OpenClaw

The official Context.dev plugin gives OpenClaw native web search and scraping, plus dedicated context_search and context_scrape tools. An optional OAuth MCP connection adds crawling, extraction, document parsing, brand intelligence, screenshots, monitors, and batches.

Install Context.dev from ClawHub

Review the current package, compatibility, and source before installing.

Choose an access level

Access	Authentication	Use it for
OpenClaw plugin	`CONTEXT_API_KEY` in the Gateway environment	Native `web_search` and `web_fetch`, plus `context_search` and `context_scrape`
Hosted MCP server	Browser-based OAuth	The complete public Context.dev tool catalog

You can use either path or enable both.

Install the plugin

Install from ClawHub

openclaw plugins install clawhub:@contextdev/openclaw-context

Configure the API key

Create a secret key in the Context.dev dashboard, then set it as CONTEXT_API_KEY in the environment that starts the OpenClaw Gateway.For a Gateway started from the same shell:

export CONTEXT_API_KEY=ctxt_secret_your_key
openclaw gateway restart

If OpenClaw runs as a background service, container, or process manager, set the variable in that service’s environment and restart it there. A shell-only export will not update an already-running Gateway.

Test native search and scraping

Send the agent a read-only request:

Use context_search to find the latest official OpenClaw release notes and return the source URLs.

For a known page, ask it to use context_scrape instead.

Connect the full MCP catalog

The plugin’s native tools cover search and single-page scraping. Add the hosted MCP server when the agent also needs extraction, parsing, brand data, monitors, screenshots, or batches.

openclaw mcp add context \
  --url https://mcp.context.dev/mcp \
  --transport streamable-http \
  --auth oauth \
  --parallel \
  --connect-timeout 30 \
  --timeout 180 \
  --no-probe

openclaw mcp login context

Complete the Context.dev authorization flow in the browser. No API key is required for this MCP connection. Verify the connection and list its tools:

openclaw mcp probe context

Use the integration

Use Context.dev to crawl the authentication section of this documentation site and summarize the setup paths with source URLs.

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

Use Context.dev to extract the current pricing tiers from this site as structured JSON.

Creating, updating, running, or deleting monitors and batches changes persistent account state. Ask for those operations explicitly and review the proposed action before it runs.

Troubleshooting

Symptom	Fix
ClawHub rejects the installation	Update OpenClaw to a version supported by the plugin’s current package metadata, then install again.
Native tools return an authentication error	Confirm `CONTEXT_API_KEY` is present in the Gateway process environment, then restart the Gateway.
MCP tools return `401` or request authorization	Run `openclaw mcp login context` and complete OAuth again.
MCP tools are missing	Run `openclaw mcp probe context` and confirm the connection is enabled and reachable.

Reference

Plugin source

README, package metadata, manifest, and release source.

OpenClaw documentation

Gateway, plugins, environment, and MCP configuration.

Context.dev MCP guide

Hosted MCP capabilities and OAuth behavior.

Context.dev dashboard

Create an API key and review usage.

Get Started

Give it to your Agent

What can Context.dev do

Optimizations

Integrations

Install Context.dev from ClawHub

Choose an access level

Install the plugin

Connect the full MCP catalog

Use the integration

Troubleshooting

Reference

Plugin source

OpenClaw documentation

Context.dev MCP guide

Context.dev dashboard

Install Context.dev from ClawHub

​Choose an access level

​Install the plugin

​Connect the full MCP catalog

​Use the integration

​Troubleshooting

​Reference

Plugin source

OpenClaw documentation

Context.dev MCP guide

Context.dev dashboard

Choose an access level

Install the plugin

Connect the full MCP catalog

Use the integration

Troubleshooting

Reference