Skip to main content
The Management MCP server is in Beta. We will continue to add functionality, with the goal of supporting the full public API. This means we may introduce breaking changes along the way. We would love to hear your feedback and requests!
The Management MCP server lets MCP-compatible clients manage Nango through tools. It is an agent-friendly alternative to the public API.

​
Connect

The server uses the Streamable HTTP transport at:
Configure your MCP client to send a Nango API key as a Bearer token: Manage API keys in Environment Settings > API Keys in the Nango UI. The API key determines which Nango environment the client can access. To limit what the MCP client can do, you can scope down the API key to only the tools it needs. The required scope for each tool is listed below.
The environment:mcp scope is not required for Management MCP tools. That scope is used by the separate action-function MCP server, which exposes enabled action functions as tools.
Keep the API key server-side and only configure it in MCP clients you trust. Do not expose it in client-side code, logs, or URLs.

​
Tools

​
Documentation

Use the Documentation tools to search the Nango documentation and read complete pages from Mintlify’s virtual documentation filesystem. Start with docs_search for broad or conceptual queries, then use docs_query_filesystem to read a relevant .mdx path or perform an exact text search. These tools require a valid Management MCP API key but no additional environment operation scope. If Mintlify rate-limits a request, the tool error points to the public Nango documentation MCP at https://nango.dev/docs/mcp so you can connect to it directly.

​
Connect sessions

Use the Connect Session tools to start an authorization flow for an end user.

​
Integrations

Use the Integrations tools to inspect and manage integrations in the authenticated Nango environment.

​
Connections

Use the Connections tools to inspect connections in the authenticated Nango environment. Connection list results never include credentials. Getting a connection only includes credentials when the API key has the credential-reading scope.

​
Proxy requests

Use the Proxy tool to make authenticated HTTP requests to a provider API through an existing connection. The tool supports GET, POST, PUT, PATCH, and DELETE, along with query parameters, headers, request bodies, base URL overrides, and up to 5 retries. It returns the provider response status, headers, and body. The tool accepts JSON and UTF-8 text responses up to 5 MB (5,000,000 bytes). Unsafe JSON integers and high-precision decimals are returned as strings so their values are not rounded. Binary responses, other character encodings, and responses over 5 MB return a tool error. Use the matching Proxy HTTP API endpoint for those responses.

​
Functions

Use the Functions tools to inspect functions deployed to an integration in the authenticated Nango environment.

​
Logs

Use the Logs tools to find activity in the authenticated Nango environment and inspect the messages for a specific operation. See Observability for more information about Nango logs.