Competlab MCP Server

CompetLab MCP Server — competitive intelligence for B2B SaaS. The competlab mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

More B2B buyers are asking AI before they Google. CompetLab monitors competitors across 5 dimensions — including AI Visibility, which tracks how ChatGPT, Claude, and Gemini mention and rank brands. This MCP server gives your AI agent access to all of it: dashboards, historical data, alerts, and strategic briefings. No other CI platform does this.

Competitive intelligence for the AI era. One platform, 5 dimensions, monitored automatically:

Its toolset

Everything the assistant can do here goes through one of these:

• check_sitemap — Live sitemap analysis — URL discovery, categorization by section, content gaps and depth
• check_ai_crawlers — Live AI-crawler access check via robots.txt + meta tags — GPTBot, ClaudeBot, Google-Extended, PerplexityBot, and others
• start_tech_stack_scan — Start async tech-stack detection (117 rules: tech / growth / engagement). Returns scanId
• get_tech_stack_scan — Poll a tech-stack scan by scanId — returns detected technologies with confidence scores when complete
• start_trust_signals_scan — Start async trust-signals analysis (34 signals across enterprise readiness, validation, social proof, authority, risk). Returns scanId
• get_trust_signals_scan — Poll a trust-signals scan by scanId — returns per-signal verdicts and tier verdict when complete
• start_agent_adoption_scan — Start async Agent-Adoption Check (25 checks: discoverability, access, readability, agent endpoints). Returns scanId
• get_agent_adoption_scan — Poll an Agent-Adoption Check by scanId — returns complete results when finished
• fetch_url — Fetch any URL with JS rendering and bot-protection handling. Returns body, headers, cleanStats. Optional cleanHtml strips noise for LLM token-cost
• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Cline — Add to cline_mcp_settings.json (or configure via Cline UI > Installed > Advanced MCP Settings):

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 2 environment variables: COMPETLAB_API_KEY, YOUR_COMPETLAB_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Competlab's toolset — check_sitemap, check_ai_crawlers, start_tech_stack_scan and 11 more — is a fair guide to whether it matches your workflow. It is maintained by competlab; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Competlab.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the competlab mcp server does with a few real requests.