# How to integrate Nango MCP with Claude Code ```json { "title": "How to integrate Nango MCP with Claude Code", "toolkit": "Nango", "toolkit_slug": "nango", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/nango/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/nango/framework/claude-code.md", "updated_at": "2026-05-12T10:19:44.657Z" } ``` ## Introduction Manage your Nango directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Nango with - [ChatGPT](https://composio.dev/toolkits/nango/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/nango/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/nango/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/nango/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/nango/framework/codex) - [Cursor](https://composio.dev/toolkits/nango/framework/cursor) - [VS Code](https://composio.dev/toolkits/nango/framework/vscode) - [OpenCode](https://composio.dev/toolkits/nango/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/nango/framework/openclaw) - [Hermes](https://composio.dev/toolkits/nango/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/nango/framework/cli) - [Google ADK](https://composio.dev/toolkits/nango/framework/google-adk) - [LangChain](https://composio.dev/toolkits/nango/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/nango/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/nango/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/nango/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/nango/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Nango to Claude Code ### Connecting Nango to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Nango MCP server, and what's possible with it? The Nango MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Nango account. It provides structured and secure access to your integrations, so your agent can perform actions like triggering syncs, managing connections, listing providers, and executing workflow actions across 250+ external APIs on your behalf. - Connection management and discovery: Effortlessly list all your existing Nango connections, view metadata, or retrieve connection information without exposing sensitive credentials. - Provider information and browsing: Ask your agent to list all available providers or fetch detailed configuration info for a specific provider, making it easy to discover and set up new integrations. - Triggering workflow actions: Direct your agent to execute custom workflow actions by specifying the connection, provider, and action identifiers—unlocking advanced automation across connected platforms. - Manual sync initiation: Have your agent trigger sync processes for any established connection, ensuring your data stays up-to-date across all integrated services. - Script configuration retrieval: Let your agent fetch Nango scripts configuration and triggers, enabling more tailored and automated integration flows. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `NANGO_ACTION_TRIGGER_POST` | Trigger Nango Action | Trigger a Nango action to execute a workflow or operation. Use this to run pre-defined actions in your Nango integrations, such as creating issues, sending messages, or fetching data from external APIs. All three of `connection_id`, `provider_config_key`, and `action_name` must simultaneously match a pre-configured integration and connection in Nango — a valid `connection_id` alone is insufficient if the other two don't correspond to an existing setup. Actions may have real upstream side effects (e.g., creating records, sending messages); confirm intent before triggering non-read-only operations. | | `NANGO_ADD_CONNECTION` | Add Connection | Tool to add a connection with existing credentials to Nango. Use when you want to bulk import existing access tokens into Nango. | | `NANGO_CONNECTION_LIST_GET` | List Connections | List all Nango connections without credentials. Use this to discover available connections, check connection status, and find connection IDs. Omitting all filters returns every connection across all integrations; use `connection_id`, `end_user_id`, or `end_user_organization_id` to narrow results. To retrieve credentials for a specific connection, use the 'Get Connection Details' action. | | `NANGO_CREATE_CONNECT_SESSION` | Create Connect Session | Tool to create a new connect session with a 30-minute lifespan for enabling connection creation via Connect UI. Use when you need to generate a session token for users to authorize integrations through Nango's Connect interface. | | `NANGO_CREATE_INTEGRATION` | Create Integration | Tool to create a new integration in Nango. Use when setting up a new provider connection configuration. Creates an integration with specified credentials (OAuth2, App-based, or Hybrid authentication). The unique_key will be used to reference this integration in subsequent API calls. Returns the created integration details including timestamps and provider information. | | `NANGO_DELETE_CONNECTION` | Delete Connection | Tool to delete a specific Nango connection. Use when you need to remove an existing connection permanently. | | `NANGO_DELETE_INTEGRATION` | Delete Integration | Tool to delete a specific integration by its unique key. Use when you need to remove an integration configuration from Nango. | | `NANGO_EDIT_CONNECTION` | Edit Connection | Tool to edit a connection's tags and metadata. Use when you need to update connection attributes like environment tags, team assignments, or end user information. | | `NANGO_GET_CONNECTION` | Get Connection with Credentials | Retrieve a specific connection with its credentials. Automatically checks if the access token has expired and refreshes it if needed. Use this action when you need to access the authentication credentials for a connection to make API calls to the provider. The credentials returned depend on the auth type (OAuth2, API Key, Basic Auth, etc.). Returns 404 if the connection does not exist, 424 if token refresh is exhausted. | | `NANGO_GET_ENVIRONMENT_VARIABLES` | Get Environment Variables | Tool to retrieve environment variables from the Nango dashboard. Use when you need to access or list environment variables configured in Nango. | | `NANGO_GET_INTEGRATION` | Get Integration | Retrieve detailed configuration for a specific Nango integration by its unique key. Returns integration details including provider, display name, creation/update timestamps, and optionally sensitive data like credentials or webhook URLs if requested via the 'include' parameter. Use this to inspect integration configuration, verify setup, or retrieve credentials for a specific integration. Returns 404 error if the integration unique key does not exist. | | `NANGO_GET_PROXY` | Proxy GET Request | Tool to make a GET request with Nango's Proxy to forward requests to external APIs while managing authentication. Use when you need to make authenticated API calls to external services through Nango's proxy infrastructure. | | `NANGO_GET_SYNC_STATUS` | Get Sync Status | Tool to get the status of specified sync(s) for a connection or all connections. Use when you need to monitor sync execution state, check completion times, or view sync frequency. | | `NANGO_CONNECTION_LIST_GET` | List Connections | Tool to list all connections without credentials. Use when you need to retrieve connection metadata across your account. | | `NANGO_LIST_INTEGRATIONS` | List Integrations | Tool to retrieve a list of all configured integrations. Use when you need to display or iterate through integrations in your account. | | `NANGO_PROVIDERS_GET_GET` | Get Provider Details | Retrieve detailed configuration for a specific Nango provider by its unique key. Returns provider authentication details (auth_mode, OAuth URLs), proxy configuration, required credentials schema, and connection configuration requirements. Use this to understand how to set up a connection with a specific provider or to get its documentation links. Provider keys can be obtained from the List Providers action. Returns 404 error if provider key does not exist. | | `NANGO_PROVIDERS_LIST_GET` | List Providers | Tool to retrieve a list of all available providers. Use when you need to display or iterate through every provider before creating connections. The provider_config_key values returned must be used verbatim when referencing providers in other actions; any mismatch will cause those actions to fail. | | `NANGO_PUT_PROXY` | Proxy PUT Request | Tool to make a PUT request with the Nango Proxy to forward requests to external APIs while managing authentication. Use when you need to update resources via external APIs through Nango's proxy. | | `NANGO_RECONNECT_SESSION_POST` | Reconnect Session | Create a new connect session to reconnect to a specific integration. Use this when a user needs to input new credentials or to manually refresh a token. Only connections created with a connect session are compatible with this endpoint. | | `NANGO_SCRIPTS_CONFIG_GET` | Get Integration Functions Configuration | Retrieve all integration functions configuration from Nango. Returns the configuration for all integrations including their sync scripts, action scripts, and event handlers. Use this to discover available integrations and their capabilities before triggering syncs or actions. | | `NANGO_SET_CONNECTION_METADATA` | Set Connection Metadata | Tool to set custom metadata for one or more Nango connections. Use when you need to attach custom data (tags, labels, context) to connections for filtering, organization, or application-specific purposes. | | `NANGO_SYNC_TRIGGER_POST` | Trigger Sync | Tool to trigger sync process(es) manually. Use after establishing a connection and defining syncs. This triggers an additional, one-off execution of the specified sync(s) for a given connection or all applicable connections. Useful when you changed metadata for a connection and want to re-import data. | | `NANGO_UPDATE_CONNECTION_METADATA` | Update Connection Metadata | Tool to edit custom metadata for one or multiple connections. Use when you need to update specific metadata properties without overwriting the entire metadata object. | | `NANGO_UPDATE_INTEGRATION` | Update Integration | Tool to update an existing integration's configuration. Use when you need to modify an integration's display name, unique key, or credentials. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Nango MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Nango account. It provides structured and secure access so Claude can perform Nango operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Nango account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["nango"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http nango-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['nango'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http nango-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Nango MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (nango-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http nango-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Nango MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your nango-composio entry in the list - This confirms that Claude Code can now access Nango tools If everything is wired up, you should see your nango-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Nango The first time you try to use Nango tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Nango - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Nango authorization flow - Return to the terminal and start using Nango through Claude Code Once authenticated, you can ask Claude Code to perform Nango operations in natural language. For example: - "List all connected CRM accounts" - "Trigger manual sync with Salesforce provider" - "Get configuration for all available scripts" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["nango"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http nango-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['nango'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http nango-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Nango with Claude Code using Composio's MCP server. Now you can interact with Nango directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Nango operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Nango operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Nango MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/nango/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/nango/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/nango/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/nango/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/nango/framework/codex) - [Cursor](https://composio.dev/toolkits/nango/framework/cursor) - [VS Code](https://composio.dev/toolkits/nango/framework/vscode) - [OpenCode](https://composio.dev/toolkits/nango/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/nango/framework/openclaw) - [Hermes](https://composio.dev/toolkits/nango/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/nango/framework/cli) - [Google ADK](https://composio.dev/toolkits/nango/framework/google-adk) - [LangChain](https://composio.dev/toolkits/nango/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/nango/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/nango/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/nango/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/nango/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Nango MCP? With a standalone Nango MCP server, the agents and LLMs can only access a fixed set of Nango tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Nango and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Nango tools. ### Can I manage the permissions and scopes for Nango while using Tool Router? Yes, absolutely. You can configure which Nango scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Nango data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)