Skip to main content
Use the Context.dev MCP connector in Scalekit AgentKit to give your agents web and company data. Connect a user’s Context.dev account through OAuth, then call tools through Scalekit’s SDKs or a virtual MCP server. Scalekit manages the connected account’s tokens and refreshes them for later calls. An agent can research a company with Context.dev, update its CRM record, and share a summary in Slack. Each additional app needs its own Scalekit connection and authorization.

Open Context.dev on Scalekit

Review the connector’s tools and input schemas, or open its playground.

Prerequisites

  • A Context.dev account with credits for tool calls
  • A Scalekit account with an environment URL, client ID, and client secret
  • A TypeScript or Python project for the SDK examples below
This guide connects each application user to their own Context.dev account. During authorization, the user chooses the Context.dev organization whose credits the calls use. You do not need to paste a Context.dev API key into your code.

Install and connect

1

Create a Context.dev connection

In the Scalekit dashboard, open AgentKit → Connections → Add connection and choose Context.dev MCP.The connector supports OAuth with dynamic client registration. When Scalekit pre-fills the OAuth client and endpoint fields, keep those values; you do not need to register a separate OAuth app. If the fields remain empty, check Scalekit’s connection setup guide before continuing.Select the scopes your agent needs:
  • api.read for search, scraping without browser actions, brand lookups, and reading existing batches or monitors.
  • api.write for operations such as file parsing, submitting batches, changing monitors, or browser actions that click on a page.
Save the connection and copy its exact name, such as contextdevmcp-abc123. Use this connection name in your code, rather than assuming it matches the connector’s catalog identifier.
2

Install the Scalekit SDK

Copy your Scalekit credentials from Developers → Settings → API Credentials and set them in your server environment, along with the connection name:
These credentials authenticate your application to Scalekit. Keep the client secret on your server.
3

Connect a user and make a first call

Replace user_123 with a stable internal user ID from your application. Save the example as scalekit.mts or scalekit.py, run it, and open the printed link to authorize Context.dev. Choose the organization the agent should use, then return to the terminal and press Enter.
Reuse the same connection name and user ID for later tool calls. You can skip generating another authorization link while the connected account is active. For an application flow, follow Scalekit’s user authorization guide, including its user verification settings.
4

Add the tools to your framework

Follow Scalekit’s framework examples to register the tools with your agent. Keep the same connection name and user ID when executing calls.For an MCP client, create a virtual MCP server with the connections and tools your agent needs, then mint a session token for the user. Pass that server URL and token to the client.

Verify the setup

The SDK example calls contextdevmcp_brand_search with query: "stripe". Inspect result.data for matching brands and keep the execution ID to find the call under AgentKit → Logs. Logs record the tool, connection, user identifier, status, and timing; they do not store successful response bodies. Once the tools are available in your agent, ask:
Confirm that the agent calls contextdevmcp_brand_search and returns tool output. An answer without a tool call does not verify the connection. Inspect the returned data for errors even if the Scalekit request itself succeeds.

Available tools

The Scalekit connector reference lists the current tools and their input schemas. Common tools: For scraping, supply both url and formats, for example {"url":"https://www.context.dev","formats":{"markdown":true}}. Use the connector’s schema when building tool inputs.

Troubleshooting

Reference

Scalekit framework examples

Add connected tools to your agent framework.

Scalekit authorization

Manage connection links, user verification, and account status.

Scalekit security

Review credential handling and what tool logs retain.

Context.dev MCP guide

Hosted server capabilities, OAuth scopes, and usage.