Context.dev MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Context.dev MCP or direct API to scrape web pages, extract structured data, monitor brand mentions, and gather market intelligence through natural language.

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

Try Context.dev now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Context.dev
Try asking
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.

SETUP GUIDE

Connect Context.dev MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/openai @ai-sdk/mcp
Install the Composio SDK for Python or TypeScript
2

Initialize Client and Create Tool Router Session

typescript
import { Composio } from '@composio/core';

const composio = new Composio({ apiKey: 'your-api-key' });
const session = await composio.create('your-user-id');
console.log(`Tool Router session created: ${session.mcp.url}`);
Import and initialize the Composio client, then create a Tool Router session for Context.dev
3

Connect to AI Agent

typescript
import { openai } from '@ai-sdk/openai';
import { experimental_createMCPClient as createMCPClient } from '@ai-sdk/mcp';
import { generateText } from 'ai';

const client = await createMCPClient({
  transport: {
    type: 'http',
    url: session.mcp.url,
    headers: {
      'x-api-key': 'your-composio-api-key',
    },
  },
});

const tools = await client.tools();
const { text } = await generateText({
  model: openai('gpt-4o'),
  tools,
  messages: [{
    role: 'user',
    content: 'Scrape structured product data from https://example.com/products'
  }],
  maxSteps: 5,
});

console.log(`Agent: ${text}`);
Use the MCP server with your AI agent (Anthropic Claude or Mastra)
SETUP GUIDE

Connect Context.dev API Tool with your Agent

1

Install Composio

typescript
npm install @composio/openai
Install the Composio SDK
2

Initialize Composio and Create Tool Router Session

typescript
import OpenAI from 'openai';
import { Composio } from '@composio/core';
import { OpenAIResponsesProvider } from '@composio/openai';

const composio = new Composio({
  provider: new OpenAIResponsesProvider(),
});
const openai = new OpenAI({});
const session = await composio.create('your-user-id');
Import and initialize Composio client, then create a Tool Router session
3

Execute Context.dev Tools via Tool Router with Your Agent

typescript
const tools = session.tools;
const response = await openai.responses.create({
  model: 'gpt-4.1',
  tools: tools,
  input: [{
    role: 'user',
    content: 'Extract structured pricing data from https://example.com/pricing'
  }],
});
const result = await composio.provider.handleToolCalls(
  'your-user-id',
  response.output
);
console.log(result);
Get tools from Tool Router session and execute Context.dev actions with your Agent

Why Use Composio?

AI Native Context.dev Integration

  • Supports both Context.dev MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable scraping, extraction, and monitoring tasks
  • Rich coverage for turning web pages, brand signals, and public data into agent-ready context

Managed Auth

  • Connect Context.dev with your API key once, then let Composio handle secure credential storage
  • Use auth_configs.create() and connected_accounts.link() to configure and link Context.dev access without hard-coding secrets
  • Manage per user and per environment credentials from one place

Agent Optimized Design

  • Tools are tuned for AI agents, so scraping and extraction calls are easier for models to understand
  • Comprehensive execution logs show what URL was scraped, what extraction ran, and on whose behalf
  • Works with mcp.create() style MCP workflows as well as direct Tool Router sessions

Enterprise Grade Security

  • Fine-grained RBAC helps you control which agents and users can access Context.dev
  • Scoped, least privilege access for web data workflows, brand monitoring jobs, and extraction pipelines
  • Full audit trail of agent actions to support review, debugging, and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Context.dev requires you to configure your own API key. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Context.dev connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Context.dev account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Context.dev actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Context.dev at any time.

When you connect a Context.dev account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Context.dev as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Context.dev. If Context.dev lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Context.dev at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Context.dev connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Context.dev rejects the old key. Create a new key in Context.dev and reconnect the account from the Composio dashboard or by asking your agent to reconnect Context.dev. Nothing else changes.

Composio's free plan includes 100,000 tool calls per month with no credit card, which covers most personal Context.dev use. Paid plans add higher limits and team features. Your Context.dev plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Context.dev accounts).

With Composio, you connect Context.dev once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

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