> 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/integrations/mcp/limitations-and-best-practices.md).

# Limitations & Best Practices

### Limitations & Common Gotchas

While MCP servers make integration easier, there are some limitations to be aware of:

* Some MCP servers may only expose read-only actions, which restricts workflow possibilities.
* Rate limits on external APIs can prevent workflows from executing if actions are called too frequently.
* Private servers can be blocked by firewalls or network restrictions if not configured properly.
* Parameter validation is necessary: if required parameters are missing or incorrectly formatted, actions may fail.

### Best Practices

To ensure smooth and reliable use of MCP servers in JetAdmin, follow these practices:

* Always test MCP servers in a staging environment before connecting them to production apps.
* Monitor usage and error logs in JetAdmin to detect and resolve issues early.
* Rotate credentials regularly (every 60–90 days) to minimize security risks.
* Document available actions and expected parameters so team members can use them consistently.
* Start with simple workflows or component bindings to validate server behavior before building complex automations.

By following these best practices, you can safely and efficiently leverage MCP servers from Smithery across JetAdmin apps, workflows, and AI agents.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jetadmin.io/user-guide/integrations/mcp/limitations-and-best-practices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.