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

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