> 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/how-to-use-mcp-servers-in-jetadmin.md).

# How to Use MCP Servers in JetAdmin

### Steps to connect an MCP server in JetAdmin

1. Open the Data section → go to Data.
2. Add a new resource → Click Add Resource and choose MCP.
3. Fill in connection details → A popup will appear with the following fields:
   * Resource Name: Defaults to *MCP*, but you can rename it (e.g., Weather Information *MCP*). 
   * Server URL: Example → `https://mcp.example.com/mcp`.
   * Protocol: Options include *Auto*, *Streamable HTTP*, and *SSE*.
   * Authentication (optional):
     * None
     * API Key
     * Basic Auth
     * OAuth 2.0
4. Click Add Resource.

{% @arcade/embed flowId="5hbgXqLkwNKN9LhAPkhp" url="<https://app.arcade.software/share/5hbgXqLkwNKN9LhAPkhp>" %}

Once connected, the MCP server will be available as a datasource in your app. You can now bind it to data components, workflows, or agents. For example, you might call operations like `get_current_weather_tool` to display live weather for a city, or `get_weather_forecast_tool` to show multi-day forecasts directly in your JetAdmin app.


---

# 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/how-to-use-mcp-servers-in-jetadmin.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.