> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data-sources/mcp/authentication-and-server-access.md).
# MCP authentication and server access
Check server reachability, authentication, and tool permissions.
Before connecting, confirm who operates the server, how Jet Admin can reach it, and what the connected account is allowed to do.
## Hosting and reachability
A provider-managed server is operated by another service. A self-managed server is deployed and maintained by your team. Hosting ownership is separate from network access: a self-managed server may have a public endpoint, while a provider-managed server may require authentication.
For a server in a private network, confirm that your Jet Admin environment can reach the endpoint. Check firewall and network rules if the connection times out.
## Configure authentication
The MCP connection form offers **Automatic** and **Manual** authorization. Use Automatic for the server's sign-in flow when supported. Under Manual, choose the authentication method required by the server, such as **None**, **API Key**, **Basic Auth**, or **OAuth 2.0**, and configure its credentials in the connection form.
Configure the authentication required by your server. The example form is a setup view, not a connected server.
A reachable URL does not establish permission to use every tool. The server and connected account determine the tools and data available.
## Verify access
1. Connect the server using [Connect an MCP server](/user-guide/data-sources/mcp/connect-an-mcp-server.md).
2. Inspect the exposed actions.
3. Test a read action with a known input.
4. If the app needs a write action, confirm its expected effect and test it on a disposable record.
5. Verify the result in the external service.
For failures, see [MCP limitations and troubleshooting](/user-guide/data-sources/mcp/limitations-and-troubleshooting.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jetadmin.io/user-guide/data-sources/mcp/authentication-and-server-access.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
