Eve

Context.dev is a first-party connection in Eve’s integration registry. One registry command adds the hosted Context.dev MCP server to an Eve agent. Each user authorizes their own Context.dev account in the browser, so you do not copy an API key into the agent.

Open the Context.dev integration for Eve

Review the current registry definition and setup instructions on Eve.

Prerequisites

An existing Eve project
The Eve and Vercel CLIs available in that project
A Vercel account with access to the project you will link

Install and connect

Add the registry connection

Run this from the root of your Eve project:

eve add connection/context

Eve creates agent/connections/context.ts and installs the authentication dependency when needed. The generated connection points to https://mcp.context.dev/mcp.

Create the Vercel connector

Link the project, create the connector, and pull its local environment:

vercel link
vercel connect create mcp.context.dev --name context
vercel env pull

Run these commands against the same Vercel project and environment that hosts the Eve agent.

Authorize Context.dev

Start the agent through your normal Eve development flow and request a Context.dev operation. Before the first tool call, Vercel Connect opens Context.dev’s browser authorization flow. Sign in and approve access.

The connection uses per-user OAuth. Do not add a Context.dev API key, bearer token, or custom authorization header to agent/connections/context.ts.

Use the connection

Ask the agent for an outcome and name Context.dev when you want to force this connection. For example:

Use Context.dev to search for Stripe's latest official product announcements. Summarize the results and include the source URLs.

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

The connection covers these common workflows:

Need	Context.dev capability
Find or read current pages	Web search, Markdown or HTML scraping, sitemap discovery, and crawling
Return predictable fields	JSON Schema-based extraction and document parsing
Enrich a company	Brand profiles, logos, design systems, fonts, and industry classifications
Run work over time	Website monitors and asynchronous batch jobs

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 Eve loaded the connection, the user completed OAuth, and the hosted MCP tools are available.

Troubleshooting

Symptom	Fix
The `context` connection is missing	Confirm `agent/connections/context.ts` exists, then rerun `eve add connection/context`.
Authorization never starts	Rerun `vercel connect create mcp.context.dev --name context`, then `vercel env pull`.
OAuth succeeds but tools remain unavailable	Restart the Eve development process so it reloads the pulled environment.
A deployed agent cannot connect	Confirm the connector belongs to the deployed Vercel project and environment, not only a local or different project.

Reference

Eve integration listing

Current registry commands and generated connection definition.

Eve connections

Connection configuration, authentication, and tool access in Eve.

Context.dev MCP guide

Hosted server capabilities and authentication details.

Context.dev API docs

Guides and reference material for the underlying operations.

Get Started

Give it to your Agent

What can Context.dev do

Optimizations

Integrations

Open the Context.dev integration for Eve

Prerequisites

Install and connect

Use the connection

Verify the setup

Troubleshooting

Reference

Eve integration listing

Eve connections

Context.dev MCP guide

Context.dev API docs

Open the Context.dev integration for Eve

​Prerequisites

​Install and connect

​Use the connection

​Verify the setup

​Troubleshooting

​Reference

Eve integration listing

Eve connections

Context.dev MCP guide

Context.dev API docs

Prerequisites

Install and connect

Use the connection

Verify the setup

Troubleshooting

Reference