Skip to main content
Context.dev is available in the Smithery registry as context/contextdotdev. The listing connects to Context.dev’s hosted MCP server and exposes tools for search, scraping, crawling, extraction, document parsing, brand intelligence, screenshots, monitors, and batches.

Open Context.dev on Smithery

Review the current server endpoint, tools, and input schemas in the Smithery registry.

​
Prerequisites

  • Node.js 20 or newer
  • A Context.dev account for browser authorization
  • A Smithery account when using managed Smithery connections or CLI tool calls
Context.dev authentication uses OAuth. You do not need to create or paste a Context.dev API key into Smithery or an MCP client.

​
Install in an MCP client

Use this path when you want Context.dev tools inside Cursor, Claude Code, Codex, VS Code, Windsurf, or another client supported by the Smithery CLI.
1

Install the Smithery CLI

2

Add Context.dev to your client

Run one command for the client you use:
The CLI writes the MCP server into that client’s configuration. Run only the command for your client.
3

Authorize and reload

Complete the Context.dev authorization flow when the client opens it, then restart or reload the client so it discovers the new tools.
Verify the installation with a read-only request in the client:

​
Use Context.dev from the Smithery CLI

Use this path to let Smithery manage the connection and call Context.dev tools directly from a terminal.
1

Sign in to Smithery

2

Create the connection

Smithery opens the browser authorization flow. If the browser does not open, visit the setup URL printed by the CLI. The stable context ID is used by later commands.
3

List the available tools

4

Make a test call

The test call consumes the normal Context.dev credits for the authorized account.

​
Common tools

Creating, updating, running, or deleting monitors and batches changes persistent Context.dev account state. Request those operations explicitly and inspect their arguments before running them.

​
Data path

Smithery connects through https://contextdotdev--context.run.tools, which proxies the hosted Context.dev MCP server. Smithery manages the connection and OAuth tokens; Context.dev executes the tools. Review Smithery Connect security before sending sensitive data through this path.

​
Troubleshooting

​
Reference

Smithery listing

Live Context.dev tool catalog and schemas on Smithery.

Smithery Connect docs

Connection lifecycle, OAuth, credential storage, and direct tool calls.

Smithery CLI source

Current install, connection, client, and tool commands.

Context.dev MCP guide

Hosted MCP capabilities and authentication details.