SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Context.dev to Claude

Connect Claude Web, Desktop and Cowork to Context.dev MCP. Extract pricing data from competitor pages, monitor brand mentions across target websites, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
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

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Context.dev account to Claude via Composio Connect, enabling it to extract pricing data from competitor pages, monitor brand mentions across target websites, scrape structured data from product pages, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Context.dev with

ChatGPTHermesAtomic Agent

Connecting Context.dev to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Context.dev account

Back in Claude, ask it to connect to Context.dev or give it any Context.dev-related task.

For example, ask Claude to:

  • "Extract pricing data from competitor pages"
  • "Monitor brand mentions across target websites"
  • "Scrape structured data from product pages"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Context.dev account is ready to use.

What is the Context.dev Claude Connector, 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 so your agent can perform Context.dev operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Context.dev?

The connector can show as connected, but Claude must use it in each Context.dev conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Context.dev again.

2. Why does Claude show an MCP server error before Context.dev connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Context.dev.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Context.dev.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Context.dev authorization link not work?

The Composio connector is one server. Your Context.dev account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Context.dev connection.
  • Composio creates a fresh Context.dev authorization link.
  • Open that link in your browser and finish the Context.dev sign-in.

4. Why do Context.dev actions fail after they worked before?

The Context.dev connection can expire or lose permission.

  • Ask Claude to inspect the Context.dev connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Context.dev account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Context.dev.
  • If the action still fails with a permission error, check that the connected account has that permission in Context.dev itself.

5. How do I switch to a different Context.dev account?

Claude can manage the Context.dev connection for you.

  • Ask Claude to disconnect or delete the current Context.dev account.
  • Ask Claude to connect Context.dev again.
  • Open the new Composio authorization link for Context.dev.
  • Sign in with the other Context.dev account in the browser.
  • After the account connects, ask Claude to retry the Context.dev task.

6. Why is my Context.dev connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Context.dev connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Context.dev tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Context.dev.
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

ChatGPT logo

ChatGPT

Use Context.dev MCP with ChatGPT

Hermes logo

Hermes

Use Context.dev MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Context.dev MCP with Atomic Agent

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. Claude Cowork 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