Skip to main content
The Management MCP server lets MCP-compatible clients manage Nango through tools. It is an agent-friendly alternative to the public API.

​
Connect with OAuth

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. OAuth is the default way to connect. Your MCP client opens Nango in a browser so you can sign in and approve access. You do not need to create or store a credential in the client.
  1. Add the Management MCP server to a client that supports Client ID Metadata Documents (CIMD):
  2. Start the client’s OAuth flow.
  3. Sign in to Nango in the browser and approve the authorization request.
  4. Return to the client. It stores and refreshes the OAuth credentials for you.
The server uses the Streamable HTTP transport.

​
Select an environment

OAuth authorizes the MCP client for your Nango account. Most tools require an environment argument containing the name of the environment in which to run the operation. Call environments_list first to get the environments you can access. The server checks your Nango user permissions in the selected environment for every tool call. All environment-scoped tools require permission to read that environment’s settings, plus any permission listed below.

​
Tools

​
Environments

Use the Environments tool to list the Nango environments available to your user. It does not take an environment argument.

​
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 no additional environment operation permission. 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. Set include_templates to true to include the provider’s available function templates in the result. These tools require no additional environment operation permission.

​
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 caller has the credential-reading permission.

​
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 the data field.
Expect the MCP request to time out within 90 seconds. This does not cancel the action function, which may continue running for up to 15 minutes. After a timeout, the tool cannot return the result or an action ID, and retrying starts another execution. When the action supports it, use input parameters that limit the amount of data processed to keep execution within the MCP timeout.

​
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.

​
Functions

Use the Functions tools to inspect and deploy template functions in the authenticated Nango environment. 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.

​
Use an API key instead

An Environment API key is an option for non-interactive clients and clients that do not support CIMD. It authenticates the client to one Nango environment, so environments_list is not exposed and other tool calls do not take an environment argument. Create an Environment API key in Environment Settings > API Keys, then configure the MCP client to send it as a Bearer token: The permissions in the tables above are the required API key scopes. The environment:mcp scope is not required. API key authentication also exposes these tools: proxy_request 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 JSON or UTF-8 text body up to 5 MB (5,000,000 bytes). Unsafe JSON integers and high-precision decimals are returned as strings. Binary responses, other character encodings, and larger responses return a tool error. Use the matching Proxy HTTP API endpoint for those responses. 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.