IndustryLens MCP MCP server

An official Model Context Protocol server provided by IndustryLens that enables AI agents to query live competitive intelligence data. It allows users to retrieve competitor profiles, track pricing changes, and analyze market moves directly within MCP-aware tools like Claude or Cursor, eliminating the need for manual dashboard checks.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by IndustryLens

MCP endpoint (Streamable HTTP)

https://api.industry-lens.com/mcp/public

Vendor documentation

What you can do with it

Query competitor pricing changes and strategic moves
Retrieve detailed competitor profiles and market positioning
Analyze competitive trends and market landscapes via AI agents

Tools advertised by the last live check:

get_competitive_profile
list_competitor_moves
find_competitors
list_reports
get_report
list_comparisons
get_comparison
subscribe_to_newsletter
get_competitor_moves_diff
get_pricing_changes
list_markets
get_market_landscape

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http industrylens-mcp https://api.industry-lens.com/mcp/public

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add industrylens-mcp --url https://api.industry-lens.com/mcp/public

Cursor

Merge this server into .cursor/mcp.json in your project, then enable industrylens-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "industrylens-mcp": {
      "url": "https://api.industry-lens.com/mcp/public"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "industrylens-mcp": {
      "type": "streamableHttp",
      "url": "https://api.industry-lens.com/mcp/public",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start industrylens-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "industrylens-mcp": {
      "type": "http",
      "url": "https://api.industry-lens.com/mcp/public"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http industrylens-mcp https://api.industry-lens.com/mcp/public

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "industrylens-mcp": {
      "url": "https://api.industry-lens.com/mcp/public"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "industrylens-mcp": {
      "serverUrl": "https://api.industry-lens.com/mcp/public"
    }
  }
}

See all 1,583

Do you run IndustryLens MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing