Claude Connector

Connect Context.dev to Claude with OAuth for live web search, scraping, extraction, monitoring, brand intelligence, and more.

The official Context.dev connector gives Claude access to current web content and structured web data. Use it to search for sources, scrape or crawl sites, extract defined fields, parse documents, retrieve brand intelligence, capture screenshots, monitor changes, and run large batches.

Connect Context.dev to Claude

Open the official Context.dev listing in Claude’s Connectors Directory.

Install and connect

1. Connect Context.dev

   Open the Context.dev connector listing while signed in to Claude, then select Connect.

2. Authorize your account

   Sign in to Context.dev when prompted and approve access. Claude returns you to the connector after authorization finishes.

3. Enable the connector in a chat

   Start a new chat. Open the + menu, choose Connectors, and make sure Context.dev is enabled for the conversation.

The connector uses Context.dev’s browser-based OAuth flow. You do not need to create or paste an API key into Claude.

Use the connector

Ask Claude for the outcome you want and name Context.dev when you want to invoke the connector explicitly.

Use Context.dev to find Stripe's latest official product announcements. Summarize them and cite the source URLs.

Use Context.dev to scrape https://example.com/pricing and return every plan as JSON with name, price, and limits.

Use Context.dev to retrieve the brand profile for linear.app, including its logos, colors, fonts, and social profiles.

Use the narrowest operation that fits the task:

Task	Ask Context.dev to
You do not know the source URL	Search the web and return cited results
You know the exact page	Scrape it as Markdown or rendered HTML
The answer spans one site	Discover its sitemap or run a focused crawl
You need predictable fields	Extract data against a JSON Schema
You need recurring checks	Create a website monitor
You have a large URL collection	Submit an asynchronous batch

Creating, updating, running, or deleting monitors and batches changes persistent Context.dev account state. Request those actions explicitly and review the tool call before approving it.

Verify the setup

Use a read-only request with a known URL:

Use Context.dev to scrape https://www.context.dev and return only the page title and source URL.

A successful result confirms that the connector is enabled and your Context.dev account is authorized.

Troubleshooting

Symptom	Fix
Context.dev is missing from the chat’s connector menu	Confirm the connector is connected, then start a new chat and enable it from + → Connectors.
Claude asks you to connect repeatedly	Disconnect Context.dev, reconnect it from the directory listing, and complete the browser consent flow before returning to Claude.
The connector is unavailable in a managed workspace	Ask the workspace owner to allow Context.dev in the organization’s connector settings.
Calls fail for insufficient credits	Review usage in the Context.dev dashboard; repeated retries will not add credits.

Reference

Context.dev connector

Open the official listing in Claude’s Connectors Directory.

Use connectors in Claude

Official instructions for connecting, enabling, and managing services in Claude.

Context.dev MCP guide

Review the capabilities and OAuth model behind the connector.

Get support

Contact Context.dev if authorization or a tool call fails.