<p align="center"> <img src="./assets/banner.png" alt="CompetLab MCP Server — Competitive Intelligence for AI Agents" width="100%" /> </p>

CompetLab MCP Server

Competitive intelligence for AI agents — see where AI sends your buyers, and what to do about it.

More B2B buyers are asking AI before they Google. CompetLab monitors competitors across 6 dimensions — including AI Visibility, which tracks which brands ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews recommend, and AI Sources, the pages Perplexity and Google AI Overviews read when they answer your buyers' questions. This MCP server gives your AI agent access to all of it: dashboards, historical data, alerts, the Strategic Briefing, and the project's Strategic Tickets board.

Supported Clients

Works with any MCP-compatible client:

• Claude Desktop / Claude Web
• Claude Code
• Cursor
• VS Code (Copilot)
• Windsurf
• Cline

Quick Start

Two ways to connect — pick the one that fits your setup:

| | Remote Server | Local Server | | ------------- | ---------------------------------------------------------- | ------------------------------------- | | Transport | Streamable HTTP | stdio | | Setup | Zero install — just add URL | npm install && npm run build | | Best for | Most users — Claude Code, Cursor, VS Code, Windsurf, Cline | Claude Desktop, Glama, or running the process yourself |

Get your API key: app.competlab.com > Organization Settings > API Keys

Option 1: Remote Server (recommended)

Server URL: https://mcp.competlab.com/mcp Auth: API key via CL-API-Key header (or api_key query parameter)

Claude Code

claude mcp add --transport http \
  --header "CL-API-Key: YOUR_COMPETLAB_API_KEY" \
  competlab https://mcp.competlab.com/mcp

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "competlab": {
      "url": "https://mcp.competlab.com/mcp",
      "headers": {
        "CL-API-Key": "YOUR_COMPETLAB_API_KEY"
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "competlab-api-key",
      "description": "CompetLab API Key (starts with cl_live_)",
      "password": true
    }
  ],
  "servers": {
    "competlab": {
      "type": "http",
      "url": "https://mcp.competlab.com/mcp",
      "headers": {
        "CL-API-Key": "${input:competlab-api-key}"
      }
    }
  }
}

Note: VS Code uses "servers" (not "mcpServers") and supports secure input prompts via ${input:id}.

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "competlab": {
      "serverUrl": "https://mcp.competlab.com/mcp",
      "headers": {
        "CL-API-Key": "YOUR_COMPETLAB_API_KEY"
      }
    }
  }
}

Note: Windsurf uses "serverUrl" (not "url").

Cline

Add to cline_mcp_settings.json (or configure via Cline UI > Installed > Advanced MCP Settings):

{
  "mcpServers": {
    "competlab": {
      "url": "https://mcp.competlab.com/mcp",
      "headers": {
        "CL-API-Key": "YOUR_COMPETLAB_API_KEY"
      },
      "disabled": false
    }
  }
}

Claude Desktop / Claude Web

Claude Desktop and Claude Web only support URL-based auth (no custom headers). Use the api_key query parameter:

Go to Settings > MCP and add the server with this URL:

https://mcp.competlab.com/mcp?api_key=YOUR_COMPETLAB_API_KEY

Option 2: Local Server (stdio)

Run the server locally via stdin/stdout. Useful for Claude Desktop, Glama, or environments that prefer stdio transport.

git clone https://github.com/competlab/competlab-mcp-server.git
cd competlab-mcp-server
npm install
npm run build

Claude Code

claude mcp add --transport stdio \
  --env COMPETLAB_API_KEY=YOUR_COMPETLAB_API_KEY \
  competlab node dist/index.js

Claude Desktop

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "competlab": {
      "command": "node",
      "args": ["dist/index.js"],
      "cwd": "/path/to/competlab-mcp-server",
      "env": {
        "COMPETLAB_API_KEY": "YOUR_COMPETLAB_API_KEY"
      }
    }
  }
}

Generic stdio

COMPETLAB_API_KEY=YOUR_COMPETLAB_API_KEY node dist/index.js

The server reads JSON-RPC from stdin and writes responses to stdout.

See examples/ for ready-to-paste config files for each client.

What is CompetLab?

Competitive intelligence for the AI era: 14 dimensions — 6 monitored continuously, plus 8 leading-edge dimensions researched for a Strategic Briefing every month, or every two weeks on Process. The six monitored dimensions:

| Dimension | What It Tracks | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | AI Visibility | Which companies ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews recommend in your category, how often each is named, and where you stand | | AI Sources | The pages Perplexity and Google AI Overviews read when they answer your buyers' questions, and whether you are on them | | Positioning | What each company says on its homepage as the page says it, what you say that nobody else does, what changed, and what pages say about you | | Pricing | What each company charges as its pricing page shows it, what typical setups cost cheapest first and where you stand, what changed, and what pages say about you | | Content | Sitemap analysis, content categorization (12 categories), URL changelog, content gaps | | Tech & Trust | Tech stacks, security headers (grade A-F), trust signals (26 signals in 5 categories), per-assistant AI access |

AI Visibility answers who AI recommends — which brands ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews name and recommend when your buyers ask, and whether you are in the core. AI Sources is its companion: the pages Perplexity and Google AI Overviews retrieve on the way to those answers, and whether they name you.

Start free trial (14 days, no credit card) | Learn more

Available Tools

48 tools. 40 are read-only; 3 are async-scan starters that create a scan record (start_tech_stack_scan, start_trust_signals_scan, start_agent_adoption_scan); 5 write to the project's Strategic Tickets board (create_ticket, update_ticket, move_ticket, delete_ticket, add_ticket_comment) and need a read_write API key.

Projects & Competitors

| Tool | Description | | ------------------ | ----------------------------------------------------------------------------- | | list_projects | List all projects with status, competitor count, and last monitored timestamp | | get_project | Get project details with per-dimension monitoring freshness | | list_competitors | List all monitored competitors (includes your own domain for comparison) | | get_competitor | Get competitor details including monitored page URLs |

AI Visibility

| Tool | Description | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | get_ai_visibility_dashboard | The market map — which companies the AI models recommend in your category, and whether you are one of them — with per-model breakdowns; optionally the models' raw answers | | get_ai_visibility_history | Paginated history of AI Visibility checks | | get_ai_visibility_check_detail | Full detail for one check, and optionally what each model actually said — filterable by competitor, model, or prompt; an answers read comes without the summary unless you ask for it (includeSummary) | | get_ai_visibility_trend | How the market the AI models draw has moved over a window — each company's reading now and at the start, and the difference; readable per AI model |

AI Sources

| Tool | Description | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | get_ai_sources_dashboard | The pages Perplexity and Google AI Overviews read when they answer the project's buying questions, per engine — which companies each named, which pages it retrieved, and the pages naming other companies and not you | | get_ai_sources_history | Paginated history of AI Sources checks | | get_ai_sources_check_detail | Full detail for one AI Sources check, and optionally every answer and retrieved page — filterable by engine or question; an answers read comes without the summary unless you ask for it (includeSummary) |

Positioning

| Tool | Description | | ---------------------------- | ----------- | | get_positioning_dashboard | What each company says on its homepage as the page says it, what you say that nobody else does, what changed, and what pages say about you | | get_positioning_history | One row per positioning check with what it found changed, in full; filter by since | | get_positioning_run_detail | One past positioning check in full, in the dashboard's shape |

Pricing Intelligence

| Tool | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | get_pricing_dashboard | What each company charges as its pricing page shows it, what typical setups cost cheapest