Chrome-Stats MCP server

Connect Chrome-Stats to Claude, ChatGPT, and other AI assistants so they can search extensions and apps, read rankings and reviews, and compare listings — using your own account and plan.

Chrome-Stats implements the Model Context Protocol, the open standard AI applications use to connect to external data. Point a compatible assistant at the address below and it will discover everything else on its own.

https://chrome-stats.com/api/mcp

What an assistant can do with it

Ask questions in plain language and the assistant works out which data it needs:

"How has Honey's install count moved over the last year, and how does it compare to Rakuten?"
"Find Chrome extensions with over 100,000 users, rated 4+, updated in the last month."
"What permissions does this extension request, and what changed in the last version?"
"Which extensions reference chrome.declarativeNetRequest in their source?"

It sees the same data your plan gives you on this website, across the Chrome Web Store, Microsoft Edge Add-ons, Firefox Add-ons, Google Play, and the Apple App Store.

Everything is read-only. A connected assistant cannot change anything in your account, submit listings, or see your password or payment details.

Connecting

Claude (claude.ai and Claude Desktop)

Open Settings → Connectors → Add custom connector, paste https://chrome-stats.com/api/mcp, and approve the request on the Chrome-Stats page that appears. Connectors are attached to your Claude account, so this covers the desktop app too.

Claude Code

claude mcp add --transport http chrome-stats https://chrome-stats.com/api/mcp
claude mcp login chrome-stats

ChatGPT

Open Settings → Connectors, choose to add a custom connector, and paste https://chrome-stats.com/api/mcp. Approve the connection on the Chrome-Stats page that appears.

Chrome-Stats implements the search and fetch tools that ChatGPT requires, so it also works as a source for deep research. Answers that draw on Chrome-Stats data link back to the listing they came from.

OpenAI Responses API

Pass your Chrome-Stats API key as the authorization value:

{
  "type": "mcp",
  "server_label": "chrome_stats",
  "server_url": "https://chrome-stats.com/api/mcp",
  "authorization": "YOUR_API_KEY"
}

Anything else

Any MCP client that supports remote servers over HTTP will work. Clients that support OAuth sign you in through Chrome-Stats. Clients that do not can send an API key instead, as either an x-api-key or Authorization: Bearer header.

Signing in

Most assistants use OAuth: you approve the connection once on a Chrome-Stats page, and the assistant never sees your password or your API key. You can review and disconnect connected apps at any time from your profile.

Disconnecting takes effect immediately — the assistant loses access and has to be authorized again to reconnect.

Tools

Tool	What it does
`search_extensions`	Find items by keyword, category, user count, rating, freshness, or publisher
`get_extension`	Details for one item, optionally with ranks, reviews, risk, permissions, or history
`compare_extensions`	Two to five items side by side
`get_trends`	Daily history of installs and ratings
`get_reviews`	User reviews, indexed or fetched live from the store
`get_ranking`	Items ranked within a store namespace or category
`list_versions`	Archived versions of an extension, with download links
`search_source_code`	Search inside published extension source code (Premium)
`search`	Keyword lookup across all five stores, returning citable references
`fetch`	One listing as a single readable document, for citation and research

The last two exist because ChatGPT requires a tool named search and one named fetch, and will not use anything else unless developer mode is on. They cover the same data as the tools above them, in the shape a research assistant expects: a keyword lookup that returns references, and a fetch that returns one listing as a document. Assistants that can use the full catalog should prefer search_extensions and get_extension, which take filters and return structured fields.

Quota

Each tool call counts as one API request against your plan, the same as a REST call. Connecting and listing tools are free.

Plan	Limit
Free	100 requests / month
Pro	100 requests / month
Premium	10,000 requests / day
Enterprise	Unlimited

Agents ask more questions than people do — a single research conversation can easily make twenty or more calls. If an assistant reports that you are out of quota, upgrading to Premium or Enterprise raises the limit. Your usage is shown on your profile.

Plan limits inside an assistant

The same gates that apply on this website apply here, and the assistant will tell you when it hits one:

Results past the first page require a paid plan
Filtered searches, raw data, and source code search require Premium
Historical range depends on your plan
Some fields, such as risk detail and publisher email history, are masked on free plans

Coverage notes

Install counts and rankings are daily snapshots, not live figures. A good assistant will quote them with their date.
Source code search covers only the latest version of each extension, only .js and .json files under 500KB, excluding locale files, and only Chrome, Edge, and Firefox — mobile apps ship compiled binaries. A negative result means "not found in the indexed subset", not "absent".
The same product often has separate listings per store. Ask for the store you mean.

Troubleshooting

The assistant cannot connect. Confirm the address is exactly https://chrome-stats.com/api/mcp. If your client does not support OAuth, it needs an API key in a header instead.

It says a paid plan is required. That tool or that page depth is not on your plan. See pricing.

It stopped working after a while. Check your profile — if the connection is gone, it was disconnected and needs authorizing again. If your quota is exhausted, it resets daily on paid plans and monthly on free.

Results look out of date. Stats are daily snapshots. Use get_reviews with live fetching for the newest reviews.