nango-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANGO_BASE_URL | No | Base URL of the Nango instance. | https://api.nango.dev |
| NANGO_SECRET_KEY | Yes | Nango environment secret key (required for single environment). | |
| NANGO_ENVIRONMENT | No | Nango environment name for single environment setup. | default |
| NANGO_MCP_ENV_FILE | No | Absolute path to a .env file containing configuration. | |
| NANGO_MCP_READ_ONLY | No | Set to true to block mutating tools. | false |
| NANGO_MCP_ENVIRONMENTS | No | Comma-separated list of Nango environment names for multi-environment setup. | |
| NANGO_MCP_REQUEST_TIMEOUT | No | Timeout for proxy requests in seconds. | 20 |
| NANGO_MCP_METADATA_NAMESPACE | No | Namespace for metadata conventions. | nango_mcp |
| NANGO_MCP_REQUIRE_CONFIRMATION | No | Set to true to require confirmation for write/delete tools. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_connection_conventionC | Explain the optional Nango MCP connection convention helpers. |
| list_environmentsB | List configured Nango environments without returning secret material. |
| check_environmentC | Resolve one configured Nango environment without returning its secret key. |
| list_integrationsB | List integrations configured in one Nango environment. |
| get_integrationB | Get one Nango integration. Credential-like response fields are redacted. |
| search_provider_templatesB | Search Nango provider templates before creating an integration. |
| create_integrationB | Create a Nango integration using the Nango API payload shape. |
| update_integrationC | Patch a Nango integration. |
| delete_integrationC | Delete a Nango integration. |
| list_connectionsC | List Nango connections using Nango's documented query filters. |
| get_connectionB | Get a Nango connection. Credential-like response fields are redacted. |
| refresh_connection_credentialsB | Force an OAuth refresh and return only a non-secret credential summary. |
| get_connection_contextC | Return a compact, redacted context view for one connection. |
| import_connectionC | Import/create a connection using the Nango API payload shape. |
| delete_connectionC | Delete one Nango connection. |
| replace_connection_tagsA | Replace a connection's complete tag set. Fetch and merge first when changing one tag. |
| update_connection_metadataA | Merge or replace structured connection metadata. Do not store credentials here. |
| update_connection_end_userB | Safely update native Nango end-user identity and verify it by read-back. |
| create_connect_sessionC | Create a Nango Connect session token. |
| create_standard_connect_sessionC | Create a Connect session and return its post-auth finalization contract. |
| create_reconnect_sessionC | Create a Nango reconnect session for an existing connection. |
| stage_proxy_request_bodyB | Stage an immutable outbound JSON body and return only its bounded descriptor. |
| proxy_requestC | Call a provider API through the Nango Proxy without exposing provider tokens. |
| query_response_artifactC | Query a stored provider response with bounded, strict camelCase controls. |
| download_provider_fileC | Stream a provider GET response into a protected MCP binary resource. |
| build_connection_conventionC | Build a suggested connection_id, tags, and metadata object for a managed connection. |
| apply_connection_conventionC | Apply suggested tags and metadata, deriving display identity from native end_user. |
| audit_connection_conventionsC | Audit Nango connections for suggested MCP tag/metadata conventions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Most tools target a distinct resource and action, but there are clusters that could confuse an agent: create_connect_session vs create_standard_connect_session, get_connection vs get_connection_context, and the four connection-convention helpers all have overlapping boundaries. The descriptions are precise enough to disambiguate with careful reading, but the set is not immediately self-evident.
Tool names consistently use snake_case with an imperative verb prefix like list_, get_, create_, update_, delete_, and refresh_. Minor deviations like check_environment, stage_proxy_request_body, and describe_connection_convention break the dominant verb-noun pattern slightly, but the overall style is predictable and readable.
With 28 tools, the server exceeds the 25-tool threshold that starts to feel too heavy. The broad Nango domain (environments, integrations, connections, Connect sessions, proxy, and conventions) partially justifies the count, but many helper and convention tools add surface area that could likely be consolidated.
Core lifecycle coverage is strong: integrations have full CRUD, connections support listing, reading, importing, deleting, and targeted updates, and Connect session creation is covered. Gaps include no environment create/update/delete and no generic connection update endpoint, but these are minor given the server's apparent scope.