Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to the Context.dev MCP server

Vendor MCP
Open markdown

The Context.dev MCP connector routes your AI agent's tool calls to Context.dev's own MCP server through Scalekit. Each user signs in to Context.dev once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 40 tools.

Tools
40
What they doRead · write · destructive
28 · 5 · 728 read5 write7 destructive
Users sign in with
OAuth app
Your own Context.dev MCP server app

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv

  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>

  3. Create the Context.dev MCP connection

    In AgentKit > Connections, create a Context.dev MCP connection and copy its redirect URI. The name you give it is the connection_name your code passes. See Configure connections.

  4. Register an OAuth app

    Context.dev MCP server connections use your own OAuth app. Register one with Context.dev MCP server and add the redirect URI you copied.

    Then enter the app's Client ID and Client Secret on the Context.dev MCP connection.

  5. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    

    const scalekit = new ScalekitClient(
      process.env.SCALEKIT_ENVIRONMENT_URL,
      process.env.SCALEKIT_CLIENT_ID,
      process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    

    const connector = 'contextdevmcp'
    const identifier = 'user_123'
    

    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Context.dev MCP:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    

    // Make your first call
    const result = await actions.executeTool({
      connector,
      identifier,
      toolName: 'contextdevmcp_get_monitor_limits',
      toolInput: {},
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user signs in once. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • contextdevmcp_brand_retrieve_unifiedRetrieve machine-readable company and brand intelligence—logos, colors, descriptions, socials, links, industry, location, and more—from one domain, company name, work email, stock ticker, ISIN, transaction descriptor, or direct URL.Read-only

    Get brand intelligence

    Retrieve machine-readable company and brand intelligence—logos, colors, descriptions, socials, links, industry, location, and more—from one domain, company name, work email, stock ticker, ISIN, transaction descriptor, or direct URL. Use get-brand for a visual card from a domain; use this tool for raw structured data or non-domain lookups.

    Inputs

    bodystringrequired
    Brand lookup request. Provide exactly one lookup type: domain, company name, email, stock ticker, direct URL, or transaction descriptor.
  • contextdevmcp_get_batchRetrieve one batch's status, progress, timing, credit accounting, errors, and download links when complete.Read-only

    Get batch status

    Retrieve one batch's status, progress, timing, credit accounting, errors, and download links when complete. Poll this after submit-batch; use get-batch-results only after the batch has completed.

    Inputs

    batch_idstringrequired
    Batch ID.
  • contextdevmcp_get_batch_resultsPage through the successful and failed URL results of a completed batch as JSON.Read-only

    Get batch results

    Page through the successful and failed URL results of a completed batch as JSON. Use the returned cursor to continue when more results exist. For progress before completion, use get-batch instead.

    Inputs

    batch_idstringrequired
    Batch ID.
    cursorstring
    next_cursor from the previous page.
    limitinteger
    Records per page. Defaults to 25. A page can close early so its payload stays under ~8 MB; rely on next_cursor rather than counting records.
  • contextdevmcp_get_brandRetrieve live brand intelligence for a domain and render a visual Context card with its logo, colors, slogan, description, social profiles, industry, location, and key links.Read-only

    Show a brand profile

    Retrieve live brand intelligence for a domain and render a visual Context card with its logo, colors, slogan, description, social profiles, industry, location, and key links. Use this when a user wants to see or inspect a company's brand. Use brand-retrieve-unified instead for raw structured data or lookup by name, email, ticker, ISIN, transaction descriptor, or direct URL.

    Inputs

    domainstringrequired
    Domain to look up, e.g. 'stripe.com'. Bare domain, no https://.
    maxSpeedboolean
    Optimize for speed, skipping slower enrichment steps.
  • contextdevmcp_get_changeRetrieve one detected change with full text diffs, added or removed URLs, semantic evidence, confidence, importance, and the current snapshot when available.Read-only

    Get a detected change

    Retrieve one detected change with full text diffs, added or removed URLs, semantic evidence, confidence, importance, and the current snapshot when available. Use after either change-listing tool when the complete evidence is needed.

    Inputs

    change_idstringrequired
    Unique change ID returned by a monitor changes endpoint, for example `chg_123`.
  • contextdevmcp_get_logRetrieve one API request from the authenticated Context account by the request_id in a list-logs data entry, including its redacted retained input, response, timing, credits, status, and user agent.Read-only

    Get an API request log

    Retrieve one API request from the authenticated Context account by the request_id in a list-logs data entry, including its redacted retained input, response, timing, credits, status, and user agent. Zero-data-retention requests contain metadata but no retained input or response.

    Inputs

    request_idstringrequired
    The request ID of the logged API call.
  • contextdevmcp_get_monitorRetrieve one monitor's configuration, status, schedule, target, change-detection rules, webhook settings, and current baseline by ID.Read-only

    Get monitor configuration

    Retrieve one monitor's configuration, status, schedule, target, change-detection rules, webhook settings, and current baseline by ID. This reads the monitor definition; use list-monitor-runs for execution history or list-monitor-changes for detected changes.

    Inputs

    monitor_idstringrequired
    Unique monitor ID returned by create-monitor or list-monitors, for example `mon_123`.
All 33 in Search