# How to integrate Dromo MCP with LangChain

```json
{
  "title": "How to integrate Dromo MCP with LangChain",
  "toolkit": "Dromo",
  "toolkit_slug": "dromo",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/dromo/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/dromo/framework/langchain.md",
  "updated_at": "2026-05-12T10:09:50.251Z"
}
```

## Introduction

This guide walks you through connecting Dromo to LangChain using the Composio tool router. By the end, you'll have a working Dromo agent that can list all spreadsheet uploads from this week, upload new customer data csv file, filter uploads with validation errors only through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Dromo account through Composio's Dromo MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Dromo with

- [OpenAI Agents SDK](https://composio.dev/toolkits/dromo/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/dromo/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/dromo/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/dromo/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/dromo/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/dromo/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/dromo/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/dromo/framework/cli)
- [Google ADK](https://composio.dev/toolkits/dromo/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/dromo/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/dromo/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/dromo/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/dromo/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Dromo project to Composio
- Create a Tool Router MCP session for Dromo
- Initialize an MCP client and retrieve Dromo tools
- Build a LangChain agent that can interact with Dromo
- 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 Dromo MCP server, and what's possible with it?

The Dromo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dromo account. It provides structured and secure access to your spreadsheet imports and uploads, so your agent can perform actions like listing uploads, managing import sessions, handling file uploads, and automating data onboarding on your behalf.
- Retrieve all upload sessions: Quickly ask your agent to fetch and list every spreadsheet upload in your Dromo organization for easy monitoring and management.
- Filter and paginate uploads: Effortlessly apply filters or paginate through large numbers of uploads to find the exact import session you need.
- Headless spreadsheet file uploads: Direct your agent to upload files to Dromo's headless import, automating the data onboarding process without manual intervention.
- Automate validation and transformation flows: Let your agent initiate uploads that trigger Dromo's validation and transformation pipelines, ensuring data quality and consistency.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `DROMO_CREATE_HEADLESS_IMPORT` | Create Headless Import | Tool to create a headless import in Dromo. Returns a signed upload URL for file uploads. Use this before uploading files to obtain the temporary upload URL. |
| `DROMO_CREATE_IMPORT_SCHEMA` | Create Import Schema | Tool to create a new import schema in Dromo. Define fields, validation rules, and settings for data imports. Use this when setting up a new data import workflow or template. |
| `DROMO_DELETE_IMPORT_SCHEMA` | Delete Import Schema | Tool to delete an import schema in Dromo. Use when you need to remove a schema definition that is no longer needed. This action is irreversible. |
| `DROMO_GET_IMPORT_SCHEMA` | Get Import Schema | Tool to retrieve an import schema by ID from Dromo. Returns the complete schema definition including fields, validation rules, settings, and webhook configurations. Use this to inspect schema structure, validate field requirements, or retrieve configuration details before creating imports. |
| `DROMO_LIST_IMPORT_SCHEMAS` | List Import Schemas | Tool to retrieve all import schemas configured for your Dromo organization. Use this to discover available schemas, their field definitions, validation rules, and settings before creating imports. |
| `DROMO_LIST_UPLOADS` | List Uploads | Retrieves a paginated list of all file uploads stored by Dromo for your organization. Returns upload metadata including status, row counts, errors, user information, and file details. Use this to monitor import progress, track upload history, or retrieve upload IDs for further processing. |
| `DROMO_UPDATE_IMPORT_SCHEMA` | Update Import Schema | Tool to update an existing import schema in Dromo. Modifies the schema definition including fields, validation rules, and settings. Use when you need to change field configurations, add/remove validators, or update import settings for an existing schema. |
| `DROMO_UPLOAD_FILE_TO_HEADLESS_IMPORT` | Upload File To Headless Import | Upload a file to Dromo's headless import system using a presigned S3 URL. This action performs the actual file upload step in Dromo's headless import workflow: 1. First, create a headless import via POST to /headless/imports/ to get an upload URL 2. Then, use this action to upload the file to that URL 3. Dromo automatically processes the file once the upload completes The upload URL is valid for 30 minutes. This action performs an HTTP PUT request with the file content to the provided presigned S3 URL. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Dromo MCP server is an implementation of the Model Context Protocol that connects your AI agent to Dromo. It provides structured and secure access so your agent can perform Dromo 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

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](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-langchain langchain-mcp-adapters langchain python-dotenv
```

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

### 3. Set up environment variables

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
```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
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
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();
```

### 5. Initialize Composio client

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 Dromo tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
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()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Dromo 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 Dromo tools as needed
```python
# Create Tool Router session for Dromo
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['dromo']
)

url = session.mcp.url
```

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

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "dromo-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "dromo-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 });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

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

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Dromo 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);
    });
```

### 9. Run the application

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

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

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['dromo']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "dromo-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Dromo related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

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

```typescript
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: ['dromo']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "dromo-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 Dromo 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 Dromo 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.

## How to build Dromo MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/dromo/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/dromo/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/dromo/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/dromo/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/dromo/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/dromo/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/dromo/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/dromo/framework/cli)
- [Google ADK](https://composio.dev/toolkits/dromo/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/dromo/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/dromo/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/dromo/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/dromo/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Dromo MCP?

With a standalone Dromo MCP server, the agents and LLMs can only access a fixed set of Dromo tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dromo and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with LangChain?

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 Dromo tools.

### Can I manage the permissions and scopes for Dromo while using Tool Router?

Yes, absolutely. You can configure which Dromo 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 Dromo data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)