How to integrate Context.dev MCP with LangChain

This guide walks you through connecting Context.dev to LangChain using the Composio tool router. By the end, you'll have a working Context.dev agent that can extract pricing data from competitor pages, monitor brand mentions across target websites, scrape structured data from product pages through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Context.dev account through Composio's Context.dev MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Context.dev

Api Key

Context.dev is a web data API platform for scraping, extraction, brand intelligence, monitoring, and structured web data. Use it to turn public web pages into clean, AI-ready data without building brittle scrapers.

11 Tools

Managed auth

Connect Context.dev without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

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

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

Also integrate Context.dev with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

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

The Context.dev MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Context.dev account. It provides structured and secure access to web content, brand intelligence, website design details, monitors, documents, and usage data, so your agent can scrape webpages, extract structured data, research brands, parse files, and review monitoring activity on your behalf.

Web scraping and structured extraction: Have your agent turn a public webpage into Markdown or crawl relevant website pages to extract information that matches your chosen structure and instructions.
Brand research and discovery: Let the agent search for companies by name or domain, then retrieve brand details such as logos, colors, industry, and descriptions.
Website design analysis: Direct your agent to inspect a website's colors, typography, spacing, shadows, fonts, and common component styles.
Document and file parsing: Instruct your agent to convert uploaded documents, images, source files, or data files into Markdown that an AI assistant can use.
Monitoring and usage oversight: Have your agent review web monitors, asynchronous scraping batches, WebDB collections, credit consumption, storage, row counts, and monitor limits.

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:

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

Step-by-step Guide

Step by step10 STEPS

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

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.

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

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

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 Context.dev functionality through MCP

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 Context.dev tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

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

const url = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Context.dev 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 Context.dev tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "context_dev-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 Context.dev MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Context.dev tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

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 Context.dev 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

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 Context.dev 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: ['context_dev']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "context_dev-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 Context.dev 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 Context.dev 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 Context.dev action and event your agent gets out of the box.

Extract Structured Web Data

Crawl relevant pages from a website and return data matching a caller-provided JSON Schema and extraction instructions.

Get Brand

Retrieve enriched brand identity, logos, colors, industry, and description using exactly one domain, name, work email, ticker, direct URL, or transaction descriptor.

Get Monitor Limits

Return the connected account's plan and current monitor usage versus its monitor limit.

Get WebDB Usage

Return WebDB credit balance, period consumption, row count, storage, and per-collection usage for an optional time range.

Get Website Styleguide

Extract a website's colors, typography, spacing, shadows, font assets, and common component styles from either a domain or one direct URL.

List Batches

List and filter the connected account's asynchronous web batches from newest to oldest, returning one cursor-controlled page.

List Monitors

List and filter the connected organization's web monitors, returning one cursor-controlled page.

List WebDB Collections

List the connected account's WebDB collections and return one cursor-controlled page, including each collection's sources, extraction configuration, status, usage, and timestamps.

Parse File

Convert an uploaded document, image, source file, or data file into LLM-usable Markdown.

Scrape Webpage to Markdown

Render one public URL and return its main or CSS-selected content as Markdown.

Search Brands

Prefix-search Context.

FRAMEWORKS

How to build Context.dev MCP Agent with another framework

OpenAI Agents SDK

Use Context.dev MCP with OpenAI Agents SDK

Claude Agent SDK

Use Context.dev MCP with Claude Agent SDK

Claude Code

Use Context.dev MCP with Claude Code

Claude Cowork

Use Context.dev MCP with Claude Cowork

Codex

Use Context.dev MCP with Codex

OpenClaw

Use Context.dev MCP with OpenClaw

Hermes

Use Context.dev MCP with Hermes

CLI

Use Context.dev MCP with CLI

Google ADK

Use Context.dev MCP with Google ADK

Vercel AI SDK

Use Context.dev MCP with Vercel AI SDK

Mastra AI

Use Context.dev MCP with Mastra AI

LlamaIndex

Use Context.dev MCP with LlamaIndex

CrewAI

Use Context.dev MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Excel

Oauth2S2s Oauth2

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.

Adafruit IO

Api Key

Adafruit IO is Adafruit's cloud platform for connected device and IoT project data. It helps you store, visualize, and act on sensor feeds without running your own backend.

Agenty

Api Key

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.

ApexVerify

Api Key

ApexVerify is a contact-data validation service for emails and phone numbers. Use it to normalize, verify, and clean leads before they enter your systems.

FAQ

Frequently asked questions

With a standalone Context.dev MCP server, the agents and LLMs can only access a fixed set of Context.dev tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Context.dev 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 Context.dev tools.

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

Start with Context.dev.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Context.dev MCP with LangChain

Connect Context.dev without auth hassles

Introduction

Also integrate Context.dev with

TL;DR

What is LangChain?

What is the Context.dev MCP server, and what's possible with it?

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

Supported Tools

How to build Context.dev MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Excel

Adafruit IO

Agenty

ApexVerify

Frequently asked questions

What are the differences in Tool Router MCP and Context.dev MCP?+

Can I use Tool Router MCP with LangChain?+

Can I manage the permissions and scopes for Context.dev while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Context.dev.It takes 30 seconds.

Teams ship real agents on Composio