# How to integrate Nango MCP with Claude Agent SDK

```json
{
  "title": "How to integrate Nango MCP with Claude Agent SDK",
  "toolkit": "Nango",
  "toolkit_slug": "nango",
  "framework": "Claude Agent SDK",
  "framework_slug": "claude-agents-sdk",
  "url": "https://composio.dev/toolkits/nango/framework/claude-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/nango/framework/claude-agents-sdk.md",
  "updated_at": "2026-05-12T10:19:44.657Z"
}
```

## Introduction

This guide walks you through connecting Nango to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Nango agent that can list all connected crm accounts, trigger manual sync with salesforce provider, get configuration for all available scripts through natural language commands.
This guide will help you understand how to give your Claude Agent SDK 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

- [ChatGPT](https://composio.dev/toolkits/nango/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/nango/framework/open-ai-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/nango/framework/claude-code)
- [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

Here's what you'll learn:
- Get and set up your Claude/Anthropic and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Nango
- Configure an AI agent that can use Nango as a tool
- Run a live chat session where you can ask the agent to perform Nango operations

## What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.
Key features include:
- Native MCP Support: Built-in support for Model Context Protocol servers
- Permission Modes: Control tool execution permissions
- Streaming Responses: Real-time response streaming for interactive applications
- Context Manager: Clean async context management for sessions

## 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 your AI agent to Nango. It provides structured and secure access so your agent can perform Nango operations on your behalf through a secure, permission-based interface.
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:
- Composio API Key and Claude/Anthropic API Key
- Primary know-how of Claude Agents SDK
- A Nango account
- Some knowledge of Python

### 1. Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
- Go to the [Anthropic Console](https://console.anthropic.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-anthropic claude-agent-sdk python-dotenv
```

```typescript
npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID identifies the user for session management
- ANTHROPIC_API_KEY authenticates with Anthropic/Claude
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here
```

### 4. Import dependencies

No description provided.
```python
import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
```

```typescript
import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
```

### 5. Create a Composio instance and Tool Router session

No description provided.
```python
async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nango
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nango"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
```

```typescript
async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Nango
  const session = await composio.create(USER_ID, {
    toolkits: ['nango'],
  });
  const mcpUrl = session?.mcp.url;
```

### 6. Configure Claude Agent with MCP

No description provided.
```python
# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Nango tools via Composio.",
    max_turns=10
)
```

```typescript
const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Nango tools via Composio.',
  maxTurns: 10,
};
```

### 7. Create client and start chat loop

No description provided.
```python
# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
```

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
```

### 8. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
```

```typescript
try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
```

## Complete Code

```python
import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nango
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nango"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Nango tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
```

```typescript
import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['nango']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Nango tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
```

## Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Nango through Composio's Tool Router.
Key features:
- Native MCP support through Claude's agent framework
- Streaming responses for real-time interaction
- Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## 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 Code](https://composio.dev/toolkits/nango/framework/claude-code)
- [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 Agent SDK?

Yes, you can. Claude Agent SDK 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)