> 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/limitations-and-troubleshooting.md).

# MCP limitations and troubleshooting

Diagnose connection, authentication, input, and tool-result problems.

The connected server defines the available tools, parameters, and permissions. Jet Admin cannot call an action the server does not expose.

| Symptom                          | Check                                                                   | Verify the fix                                                |
| -------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------- |
| Connection times out             | Server URL, server availability, firewall, and network access           | Reconnect and load the tool list                              |
| Authentication fails             | Required authentication method, current credentials, and granted access | Run an authorized read action                                 |
| Expected tool is missing         | Server's exposed tools and account permissions                          | Confirm the tool appears for this account                     |
| Action rejects an input          | Required parameters, types, and accepted values                         | Run a known valid input                                       |
| Calls are rate-limited           | Limits from the MCP server and underlying service                       | Follow the service's retry guidance and reduce call frequency |
| Output differs from expectations | Requested record/location, response fields, units, and dates            | Compare with the same data in the external service            |
| Write action is unavailable      | Server capabilities and account permissions                             | Confirm the server exposes an authorized write operation      |

## Before using a tool in automation

[Test the tool](/user-guide/data-sources/mcp/test-an-mcp-tool.md) with a known input. Record its expected output and whether it changes external data. Inspect tool inputs and outputs when debugging an agent or workflow.

Manage credentials according to your organization's policy and the provider's requirements. Include the action name, error, and test inputs in a support report; remove credentials from logs and screenshots.


---

# 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/limitations-and-troubleshooting.md?ask=<question>&goal=<user_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.