SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Nango MCP with LangChain

Connect LangChain to Nango MCP. List all connected crm accounts, trigger manual sync with salesforce provider, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Nango logoNango
Api Key

Nango is a unified API platform that connects to 250+ SaaS apps across CRM, HR, and accounting. Streamline integrations with one API and simplify data sync across your business tools.

24 Tools

Introduction

This guide walks you through connecting Nango to LangChain using the Composio tool router. By the end, you'll have a working Nango agent that can manage connections and integrations, trigger syncs and actions, proxy API requests, and check sync status through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Nango account through Composio's Nango MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Nango with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKCodexGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentPiDeepSeek HarnessGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Nango project to Composio
  • Create a Tool Router MCP session for Nango
  • Initialize an MCP client and retrieve Nango tools
  • Build a LangChain agent that can interact with Nango
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Nango functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Nango tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['nango']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Nango tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Nango tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "nango-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Nango MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Nango tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Nango related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Nango and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['nango']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "nango-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Nango related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Nango through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Nango action and event your agent gets out of the box.

Trigger Nango Action

Trigger a Nango action to execute a workflow or operation.

Add Connection

Tool to add a connection with existing credentials to Nango.

List Connections

List Nango connections without credentials to discover connections, check status, and find connection IDs.

Create Connect Session

Tool to create a new connect session with a 30-minute lifespan for enabling connection creation via Connect UI.

Create Integration

Tool to create a new integration in Nango.

Delete Connection

Tool to delete a specific Nango connection.

Delete Integration

Tool to delete a specific integration by its unique key.

Edit Connection

Edit a Nango connection's tags or end user information, such as environment tags and team assignments.

Get Connection with Credentials

Retrieve a specific connection with its credentials.

Get Environment Variables

Tool to retrieve environment variables from the Nango dashboard.

Get Integration

Retrieve detailed configuration for a specific Nango integration by its unique key.

Proxy GET Request

Tool to make a GET request with Nango's Proxy to forward requests to external APIs while managing authentication.

Get Sync Status

Tool to get the status of specified sync(s) for a connection or all connections.

List Connections

Tool to list all connections without credentials.

List Integrations

Tool to retrieve a list of all configured integrations.

Get Provider Details

Retrieve detailed configuration for a specific Nango provider by its unique key.

List Providers

Retrieve a list of available Nango providers for display or discovery before creating connections.

Proxy PUT Request

Tool to make a PUT request with the Nango Proxy to forward requests to external APIs while managing authentication.

Reconnect Session

Create a new connect session to reconnect to a specific integration.

Get Integration Functions Configuration

Retrieve all integration functions configuration from Nango.

Set Connection Metadata

Tool to set custom metadata for one or more Nango connections.

Trigger Sync

Tool to trigger sync process(es) manually.

Update Connection Metadata

Tool to edit custom metadata for one or multiple connections.

Update Integration

Tool to update an existing integration's configuration.

FRAMEWORKS

How to build Nango MCP Agent with another framework

Claude Code logo

Claude Code

Use Nango MCP with Claude Code

Cursor logo

Cursor

Use Nango MCP with Cursor

ChatGPT logo

ChatGPT

Use Nango MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Nango MCP with Claude Cowork

Antigravity logo

Antigravity

Use Nango MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Nango MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Nango MCP with Claude Agent SDK

Codex logo

Codex

Use Nango MCP with Codex

Grok Build logo

Grok Build

Use Nango MCP with Grok Build

VS Code logo

VS Code

Use Nango MCP with VS Code

OpenCode logo

OpenCode

Use Nango MCP with OpenCode

OpenClaw logo

OpenClaw

Use Nango MCP with OpenClaw

Hermes logo

Hermes

Use Nango MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Nango MCP with Atomic Agent

Pi logo

Pi

Use Nango MCP with Pi

DeepSeek Harness logo

DeepSeek Harness

Use Nango MCP with DeepSeek Harness

Google ADK logo

Google ADK

Use Nango MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Nango MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Nango MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Nango MCP with LlamaIndex

CrewAI logo

CrewAI

Use Nango MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Nango MCP with Pydantic AI

AutoGen logo

AutoGen

Use Nango MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. LangChain 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.

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.

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.

Start with Nango.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Nango tool your agent needs.Free to start.

Start building