ExtensionDash MCP MCP server

ExtensionDash provides an MCP server that allows coding agents to access real-time browser extension analytics. It enables agents to retrieve daily keyword rankings, install counts, user ratings, competitor data, and listing change history from the Chrome Web Store and Firefox Add-ons. This integration allows agents to answer performance questions, track market position, and monitor competitor activities directly through natural language interactions.

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 ExtensionDash

MCP endpoint (Streamable HTTP)

https://extensiondash.com/mcp

Vendor documentation

What you can do with it

Check daily keyword rankings for tracked extensions
Monitor monthly changes in installs and user ratings
Identify competitors outranking specific terms
Track changes to rival extension listing copy

Tools advertised by the last live check:

list_extensions
get_extension
get_metrics_history
list_keywords
get_keyword_ranks
add_keyword
remove_keyword
add_competitor
remove_competitor
list_competitors
get_keyword_serp
list_scrape_runs
search_store
get_store_listing
find_listing
search_catalog

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 extensiondash-mcp https://extensiondash.com/mcp

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 extensiondash-mcp --url https://extensiondash.com/mcp

Cursor

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

Cursor configuration

{
  "mcpServers": {
    "extensiondash-mcp": {
      "url": "https://extensiondash.com/mcp"
    }
  }
}

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": {
    "extensiondash-mcp": {
      "type": "streamableHttp",
      "url": "https://extensiondash.com/mcp",
      "disabled": false
    }
  }
}

VS Code

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

VS Code configuration

{
  "servers": {
    "extensiondash-mcp": {
      "type": "http",
      "url": "https://extensiondash.com/mcp"
    }
  }
}

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 extensiondash-mcp https://extensiondash.com/mcp

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": {
    "extensiondash-mcp": {
      "url": "https://extensiondash.com/mcp"
    }
  }
}

Windsurf

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

Windsurf configuration

{
  "mcpServers": {
    "extensiondash-mcp": {
      "serverUrl": "https://extensiondash.com/mcp"
    }
  }
}

See all 957

Do you run ExtensionDash 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