MCPサーバー
ExtensionDash
io.github.tonic20/extensions-dashboard
このMCPでできること
Researches browser-extension store listings, search rankings, installs, competitors and historical performance.
機能
ツール
15
ツール
add_competitor
Start tracking a competitor for an extension.
Takes the same store and external_id that search_store returns, so a
result you just saw on a SERP can be promoted without looking anything
up in between.
Promoting a listing is what earns it a store fetch: its description,
install count, rating and languages start being recorded, and its
position is kept even on days it falls out of the results entirely.
Where it ranks has been recorded all along, from the searches this
account already runs — so a competitor added today arrives with
history rather than starting from zero.
The description is not available when this returns. Call
list_competitors with the same extension_id until this competitor's
status turns from "pending" to "scraped".
At most 20 competitors per store, because
each one costs a fetch of that store on every refresh. The two stores
are counted separately: a full Chrome roster does not cost you a
Firefox slot.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id', 'store', 'external_id'], 'properties': {'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'external_id': {'type': 'string', 'description': "Chrome's 32-letter id or the AMO slug, exactly as search_store returns it."}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
add_keyword
Start tracking a search term for an extension. The term is added once
per store the extension is listed in, and a rank fetch is enqueued for
each store that was not already tracking it.
The position is not available when this returns. Call list_keywords with
the same extension_id until this term's status turns from "pending" to
"scanned", or list_scrape_runs to watch the fetch itself — a fetch that
fails shows up there, rather than as a position that never arrives.
A term is tracked per store language. Tracking "ad blocker" in en and
again in de gives two independent keywords with their own positions.
Call list_keywords for the languages an extension already tracks.
During the beta an extension tracks at most 15
keywords, counted per language: "ad blocker" in en and de is two of them.
Past that this returns a limit error and remove_keyword has to free a
slot first.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id', 'term'], 'properties': {'term': {'type': 'string', 'description': 'The search term, e.g. "json viewer". Squished and lowercased before use.'}, 'locale': {'type': 'string', 'description': 'Store language to search in: "en", "de", "pt-BR". Defaults to "en". The same term ranks differently in each, so this is a separate keyword, not a translation. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
find_listing
Turn an extension's NAME into the store id every other tool asks for.
Start here whenever you were handed a name rather than an id or a store
URL, which is what a person will normally give you. Matching is
approximate: case, punctuation, word order and a missing word are all
tolerated, so "image search anywhere" finds "Reverse Image Search
Anywhere".
This reads names already stored here. It is not a store search and
reports no ranking -- for where an extension actually places on a term,
use search_store. It starts no fetch, so it never returns "pending" and
spends none of the store-egress budget; like every call here it is
logged and counts against the rate limit.
Every match carries `cached`. true means get_store_listing can serve
that extension's page from cache right now, with no account.
false says one thing only: this locale has no fresh guest-readable
cache. For a guest that is a refusal. Signed in, the next call may
answer "pending" while it fetches, or hand back older data marked
stale while it refreshes, or report a recent fetch failure with no
listing at all -- so read the status you get rather than assuming
which of those it will be.
`cached` is a promise about ONE locale -- the one you pass here, "en" by
default -- because a Chrome listing read in German needs two fetches,
English structure plus German copy. Ask with the locale you intend to
read in, or the answer is about a different call than the one you make.
Two extensions can share a name, so matches carry `publisher` to tell
them apart when the store recorded one.
A name too long to match in full is refused rather than trimmed, because
trimming would report the words it dropped as matched.
No match means this app has never seen that name -- guessing another
spelling will not help. Use search_store if what you have is really a
search phrase; otherwise ask the person you are working for for the
extension's store URL or id, and pass that to get_store_listing.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['name'], 'properties': {'name': {'type': 'string', 'maxLength': 200, 'description': 'The extension\'s name as you were given it, e.g. "Reverse Image Search Anywhere".'}, 'limit': {'type': 'integer', 'maximum': 25, 'minimum': 1, 'description': 'Most matches to return, best first. Defaults to 10.'}, 'store': {'enum': ['chrome', 'firefox'], 'type': 'string', 'description': 'Restrict to one store. Both are searched when omitted.'}, 'locale': {'type': 'string', 'maxLength': 35, 'description': 'Which locale `cached` should answer for. Defaults to "en". Does not change which names match.'}}, 'additionalProperties': False}
get_extension
One extension in full: every store listing's latest numbers plus its
tracked keywords and their current positions.
locales lists every store language this extension tracks, with a
keyword count each, so the keywords can be worked a language at a time.
Use get_metrics_history or get_keyword_ranks for movement over time.
This is the tracked view, built from what we have recorded. For an
extension this account does not track, or for a listing in another
language, use get_store_listing instead.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id'], 'properties': {'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
get_keyword_ranks
Daily search position history for an extension's tracked keywords, one
series per term per store.
Every point carries the depth it was scanned to, because a position only
means something against the size of the pool it came from: #1 of 9 and
#1 of 50 are different results. A null position means we searched that
deep and this extension was not in the results.
A term tracked in more than one store language comes back as one series
per language — the same term is a different SERP in each.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id'], 'properties': {'days': {'type': 'integer', 'maximum': 365, 'minimum': 1, 'description': 'How far back to look. Defaults to 30.'}, 'term': {'type': 'string', 'description': 'One term. Omit for all of them.'}, 'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'locale': {'type': 'string', 'description': 'Store language, e.g. "de". Omit for every language. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
get_keyword_serp
The search page for one of an extension's tracked keywords, as this
account last recorded it — who was on it, in what order, and which way
each of them moved over the past week.
Read from recorded history, not from the store: no fetch, no waiting,
no egress spent. Use search_store instead when you need what the store
is showing right now; use this when you want movement, or the same page
the dashboard is showing.
Every row carries mine and competitor flags, so "who is above me and
which of them am I already tracking" is one call. Positions always
travel with depth_scanned, because #1 of 9 and #1 of 50 are different
results.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id', 'store', 'term'], 'properties': {'term': {'type': 'string', 'description': 'A term this extension tracks. From list_keywords.'}, 'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'locale': {'type': 'string', 'description': 'Store language. Defaults to "en".'}, 'window': {'type': 'boolean', 'description': 'Return only the leaders and our own neighbourhood rather than the whole page. Defaults to false.'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
get_metrics_history
Daily-or-sparser history of an extension's numbers: user count,
rating and ratings count, each as a map of ISO date to value.
"listings" is this extension's own store listings; "competitors" is
its roster from list_competitors. store and days filter both.
A map holds only dates actually observed; an empty map means no
measurement in range, never zero. If users_rounded_in_range is true
the store published rounded counts somewhere in the window, so small
movements there may be rounding.
Competitors are captured every few days rather than daily, and not on
a fixed schedule, so compare a rival against "listings" on dates
present in both, never by position in the map. Join a competitor
entry back to list_competitors on (store, external_id); name is a
label, not an identifier.
include_competitors adds every roster competitor's history.
competitors narrows that to specific (store, external_id) pairs and
implies include_competitors; a pair not on the roster fails the whole
call rather than silently dropping it.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id'], 'properties': {'days': {'type': 'integer', 'maximum': 365, 'minimum': 1, 'description': 'How far back to look. Defaults to 30.'}, 'store': {'enum': ['chrome', 'firefox'], 'type': 'string', 'description': 'Filters both listings and competitors. Omit for every store.'}, 'competitors': {'type': 'array', 'items': {'type': 'object', 'required': ['store', 'external_id'], 'properties': {'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'external_id': {'type': 'string'}}, 'additionalProperties': False}, 'description': 'Limit competitor history to these (store, external_id) pairs from list_competitors. Implies include_competitors; an unlisted pair fails the call.'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}, 'include_competitors': {'type': 'boolean', 'description': "Also return history for this extension's promoted competitors. Defaults to false."}}, 'additionalProperties': False}
get_store_listing
One extension's store page, straight from the store — any extension,
tracked by this account or not.
Copy comes back as readable text: AMO serves HTML, and its tags,
entities and redirector URLs are stripped so a description reads as
prose rather than as markup. Chrome's copy is already text and is
passed through unchanged.
This is the competitor-research and copy-review tool: full description,
supported languages, category, install count, rating, and version, in
whichever store language you ask for. Chrome listings return supported
languages as the store renders them ("Deutsch", "français"); Firefox
returns locale codes ("de", "fr"). That difference is real, not a bug.
Reading a listing never starts tracking it. Signed in, a read of a
Chrome listing already stored here -- tracked by any account, not
just yours -- may add a point to its copy timeline. A guest read
writes no research state, though the call itself is still logged and
rate-limited like any other.
Use get_extension instead for an extension this account tracks, when
you want its recorded numbers over time.
Cached for a day and fetched in the background: a cold call returns
status "pending", so call again with the same arguments until it reads
"ready".
Without an account this answers from cache only: a listing nobody has
fetched yet returns status "sign_in_required", and calling again will
not change that.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['store', 'external_id'], 'properties': {'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'locale': {'type': 'string', 'maxLength': 35, 'description': 'Store language: "en", "de", "ru". Defaults to "en".'}, 'max_age': {'type': 'integer', 'maximum': 2592000, 'minimum': 0, 'description': 'Accept a cached answer up to this many seconds old. Defaults to a day.'}, 'external_id': {'type': 'string', 'maxLength': 100, 'description': "Chrome's 32-letter id, or the AMO slug, numeric id, or guid."}, 'include_copy_history': {'type': 'boolean', 'description': 'Also return every recorded wording of this listing, newest first. Only listings already stored here have one -- tracked by any account, not just yours -- and only signed in; a guest read never receives copy history. Defaults to false.'}}, 'additionalProperties': False}
list_competitors
Who this extension competes with, measured across every keyword it
tracks.
Two sets. "competitors" is the roster you promoted with
add_competitor: their descriptions, install counts and ratings are
recorded, and their positions are kept even on days they fall out of
the results. "candidates" — returned only with include_observed —
is everyone else who has appeared in those searches, ranked by how
often they beat you.
Both are read from positions this account already recorded, not from
the store: no fetch, no waiting, and each row carries the evidence
behind it (how many of your terms, average position, first seen). This
is the tool for deciding who is worth promoting.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id'], 'properties': {'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}, 'include_observed': {'type': 'boolean', 'description': 'Also return unpromoted candidates. Defaults to false.'}}, 'additionalProperties': False}
list_extensions
Every extension this token's owner tracks, with each store listing's
latest numbers: user count (and whether the store rounded it), the
7-day change, rating, ratings count and category rank.
Start here when this connection has an account: every tracking tool
takes an extension_id from this list. Without one, start at
find_listing instead -- it needs no account and turns a name into the
store id get_store_listing reads.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {}, 'additionalProperties': False}
list_keywords
Every search term tracked for one extension, one row per term per store.
status is "pending" until a fetch has landed since the term was tracked,
and "scanned" once one has. A "scanned" row with a null position means
we searched depth_scanned results and this extension was not among
them — that is a real observation, not missing data.
A "pending" row can still carry a position. Removing a keyword stops the
tracking but keeps the history, so a term tracked before and added again
arrives with its previous result already in place; captured_on says how
old that is. Poll until the status reads "scanned" to know the number
answers the current tracking.
locale is the store language the term was searched in. The same term
ranks differently under hl=de than under hl=en, so two rows sharing a
term and a store are two different results.
locales lists every store language this extension tracks, with a
keyword count each — start there to work a language at a time. It
always reports every language, including when the locale argument
narrows the rows to one.
search_volume is Google Ads' average monthly searches for the term,
worldwide, in the row's store language. It is web search demand, not
searches inside the store, and is the same for both stores. null means
not fetched yet, Google has no data, or the term can't be looked up
(symbols such as + or %, over 80 characters or 10 words, or a store
language without a Google Ads mapping); search_volume_fetched_at says
which.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id'], 'properties': {'locale': {'type': 'string', 'description': 'Store language, e.g. "de". Omit for every language. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
list_scrape_runs
Recent scrape attempts against your own extensions, newest first, with
their outcome and any error. Covers both the listing fetches and the
rank fetches for the search terms they track.
Use this after add_keyword to watch the rank fetch: the run is targeted
at the search term, and a failed fetch appears here as a failure rather
than as a position that never arrives.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Defaults to 20.'}, 'status': {'enum': ['running', 'success', 'failure'], 'type': 'string'}, 'extension_id': {'type': 'integer', 'description': "Narrow to one extension's listings and tracked keywords."}}, 'additionalProperties': False}
remove_competitor
Stop tracking a competitor for an extension.
Stops the store fetches. The recorded history is kept, so adding the
same competitor again later restores its charts rather than starting
from zero — and its positions carry on being observed either way,
because they come from searches this account already runs.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id', 'store', 'external_id'], 'properties': {'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'external_id': {'type': 'string', 'description': 'From list_competitors.'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
remove_keyword
Stop tracking a search term for an extension, across every store it was
tracked in. Positions already recorded are kept; only the tracking stops.
Other extensions tracking the same term through their own store listings
are unaffected. A store listing can itself be shared by several
extensions, though — when it is, they share one tracking, and removing
the term from one removes it from all of them.
A term is tracked per store language. Tracking "ad blocker" in en and
again in de gives two independent keywords with their own positions.
Call list_keywords for the languages an extension already tracks.
Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['extension_id', 'term'], 'properties': {'term': {'type': 'string', 'description': 'As reported by list_keywords.'}, 'locale': {'type': 'string', 'description': 'Store language to search in: "en", "de", "pt-BR". Defaults to "en". The same term ranks differently in each, so this is a separate keyword, not a translation. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".'}, 'extension_id': {'type': 'integer', 'description': 'From list_extensions.'}}, 'additionalProperties': False}
search_store
Search a store the way a shopper would, and read the results.
This is how you see a real SERP: who ranks for a term, in what order,
with the titles and taglines they rank with. Results are not limited to
extensions this account tracks — any competitor is visible — and,
signed in, any result that IS one of yours carries its extension_id, so
"where am I, and who is above me" is one call.
locale is a real ranking axis, not a translation of the page. The same
term returns a different order, and partly different extensions, under
hl=de than under hl=en. Search the market you care about.
Signed in, any row you already track as a competitor carries
competitor_of, the ids of the extensions watching it, so you can read a
page and see at a glance who is already on a roster and who is new.
Results are cached for a day and fetched in the background. A cold
search returns status "pending": call again with the same arguments
until it reads "ready". Rows are deliberately thin — call
get_store_listing for a description, supported languages, or install
counts. To rank rivals rather than read one page, use list_competitors
with include_observed: it scores everyone already seen across every
term you track, from recorded history, with no fetch at all.
Without an account this answers from cache only: a term nobody has
fetched yet returns status "sign_in_required", and calling again will
not change that.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['store', 'term'], 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Defaults to 1.'}, 'term': {'type': 'string', 'maxLength': 200, 'description': 'e.g. "ad blocker". Squished and lowercased.'}, 'store': {'enum': ['chrome', 'firefox'], 'type': 'string'}, 'locale': {'type': 'string', 'maxLength': 35, 'description': 'Store language: "en", "de", "ru". Defaults to "en". Changes the results, not just the wording.'}, 'max_age': {'type': 'integer', 'maximum': 2592000, 'minimum': 0, 'description': 'Accept a cached answer up to this many seconds old. Defaults to a day; never refetches more than once every 15 minutes.'}, 'page_size': {'type': 'integer', 'maximum': 50, 'minimum': 1, 'description': 'Defaults to 20.'}}, 'additionalProperties': False}
履歴
最近のツール変更
追加
find_listing
2026年10月2日2:40
追加
get_store_listing
2026年10月2日2:40
追加
search_store
2026年10月2日2:40
追加
list_scrape_runs
2026年10月2日2:40
追加
get_keyword_serp
2026年10月2日2:40
追加
list_competitors
2026年10月2日2:40
追加
remove_competitor
2026年10月2日2:40
追加
add_competitor
2026年10月2日2:40
追加
remove_keyword
2026年10月2日2:40
追加
add_keyword
2026年10月2日2:40
追加
get_keyword_ranks
2026年10月2日2:40
追加
list_keywords
2026年10月2日2:40
追加
get_metrics_history
2026年10月2日2:40
追加
get_extension
2026年10月2日2:40
追加
list_extensions
2026年10月2日2:40
関連MCP
類似のMCPサーバー
rankparse-mcp
io.github.abhibavishi/rankparse-mcp
Provides SEO and search marketing research including backlinks, authority, competitor gaps, Google Ads keyword metrics, and Googl…
sonar
app.trysonar/sonar
Provides app-store optimization tools for keyword research, rankings, reviews, competitor analysis, alerts, and ASO scoring on iO…
Ai Briefing
io.github.pipeworx-io/ai-briefing
Routes research questions to structured sources including financial, scientific, government, market, news, and economic data, wit…
42matters
io.github.pipeworx-io/42matters
Provides mobile app store intelligence, SDK and chart analysis, AI visibility checks, structured research across many data source…
Ai Feeds
io.github.pipeworx-io/ai-feeds
Provides AI news feeds, AI visibility checks, and routed access to structured research and market data sources.
Textstats
io.github.pipeworx-io/textstats
Provides readability scoring, AI visibility audits, structured research across many data sources, and related research utilities.
Seo Serp
io.github.pipeworx-io/seo-serp
Provides Google organic SERP research and related routed structured-data and AI visibility capabilities.
Seo Ai Visibility
io.github.pipeworx-io/seo-ai-visibility
Checks brand visibility in LLM responses, generates llms.txt files, and provides broader routed research and structured-data look…