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!
Connect
For step-by-step installation instructions for specific coding agents, like Claude Code, Cursor, Codex, VS Code, Pi, and OpenCode, see the coding agent setup guide. The server uses the Streamable HTTP transport at:
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.Tools
Documentation
Use the Documentation tools to search the Nango documentation and read complete pages from Mintlify’s virtual documentation filesystem. Start withdocs_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.
Providers
Use the Provider tools to inspect the public provider catalog. Setinclude_templates to true to include the provider’s available function templates in the result.
These tools require a valid Management MCP API key but no additional environment operation scope.
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.Actions
Use the Actions tool to trigger an action function synchronously for a connection. Provide the integration ID, connection ID, and action name. The JSON input is optional. The tool returns the action’s JSON result in thedata field.
Syncs
Use the Sync tools to set sync state or trigger syncs for an integration in the authenticated Nango environment. You can optionally limit either operation to one connection and select named sync variants. Triggering can run a full reset and clear existing synced records.Proxy requests
Use the Proxy tool to make authenticated HTTP requests to a provider API through an existing connection. The tool supportsGET, 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 and deploy functions in the authenticated Nango environment.deploy_function and deploy_template start distinct deployment paths. Use get_deployment_status to check whether a deployment has finished.
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.