Type "chrome web store mcp" into Google and the suggestions drift toward browser automation. That's a hint. Most of what's out there drives Chrome, and very little of it knows anything about the store.
New to the idea? Start with what an MCP server is. The protocol itself is documented at modelcontextprotocol.io.
Two kinds of "Chrome" MCP
| Kind | What it does | Good for |
|---|---|---|
| Browser control | Opens tabs, clicks, reads the page | Testing, form filling |
| DevTools bridge | Reads console and network logs | Debugging your own build |
| Store data | Queries saved listing numbers | Market research |
| Your own crawler | Whatever you wired up | Custom jobs, if you'll maintain it |
A browser MCP can open one listing and read it aloud. Fine. Ask it to compare 500 listings and it'll grind through pages one by one, if the site lets it.
A store-data MCP queries a database instead. The crawling already happened, politely, before you asked.
What a good Chrome Web Store MCP returns
The test is simple. Ask for a number, then ask where it came from.
- Users as the store shows them, with "rounded bucket" marked.
- Rating and count, labelled lifetime.
- The date each number was observed.
- Unknown when there's no data, never a zero.
That last rule matters more than it sounds, because an assistant can't tell the difference between a field that was checked and found empty and a field nobody ever looked at.
If a tool returns "paid: false" when it simply never checked, your AI will repeat "this extension is free" with total confidence.
To test this on real listings, start with the Developer Tools category page.
What we're building, and what's not ready
We're biased here, so take this as a plain status note. Ext Watch's MCP server is in build for our two top plans. It reads only our own crawl.
On 3 Oct 2026 that crawl covered 61,820 extensions, about 21% of the store's sitemap IDs. Our own history started on 2 Oct 2026, so growth answers will say "not enough history yet" for a while.
| Tool | Status |
|---|---|
| Search extensions | Planned for launch |
| Get one extension | Planned for launch |
| Openings and new launches | Planned for launch |
| Monetization facts | Waits on the pricing-page crawl |
| Review text | Not collected; no compliant source yet |
How to try the idea today, for free
You don't need us to feel the difference. Try it. Export a small CSV of listings you've checked by hand, then give it to Claude as a file.
Ask the same question twice: once with the file, once without. The answer with data names dates. The one without names vibes.
For the prompt side, see asking Claude what extension to build and AI market research without made-up facts.
When a number comes back with a date, you can check it. That's the whole point of plugging the store into your assistant.
Questions people ask
Is there an MCP server for the Chrome Web Store?
Several MCP servers drive Chrome itself. Few return store listing data. Check the tool list before you install one.
Can Claude read Chrome Web Store data?
Claude can browse a page you give it, but it can't compare thousands of listings over time without a data source plugged in through MCP.
What is the difference between a browser MCP and a store-data MCP?
A browser MCP clicks and reads pages for you. A store-data MCP queries a database that someone has already collected.
Where these numbers come from
- modelcontextprotocol.ioModel Context Protocol: introductionAccessed 3 Oct 2026
- anthropic.comAnthropic: Introducing the Model Context ProtocolAccessed 3 Oct 2026
Part of our guide: What Is MCP Server? A Plain Guide for Extension Builders. More in AI and MCP.
1,182 new extensions in the last 30 days in Developer Tools. See them all.
Ask Claude about store data directly, or browse the openings yourself. Updated 3 Oct 2026 from our Chrome Web Store crawl
