Overview
The Dock MCP extension exposes 34 tools that let an AI assistant read, and in a few cases edit, the data Dock manages on your Mac:
- App Store Connect listings, keywords, screenshots, app previews, the Asset Library and the product page’s creative assets
- Google Play listings
- Keyword history, ranking evolution and fresh metrics for any keyword
- Competitor research on any app in the public stores
- Reviews on both stores
- Sales, finance, and who to invoice for each month of App Store proceeds
- Cross-platform twin app comparisons
- Your app’s website: its technical audit, keyword research, Google positions, citations in AI answers, and link building targets
The extension is a thin bridge: every tool call is forwarded to the Dock app running on your machine, over the loopback interface. The extension sends nothing to remote servers itself, and credentials (App Store Connect API keys, Google OAuth tokens) never leave Dock.
Claude ──stdio──▶ DockMCP (inside Dock.app) ──HTTP──▶ Dock.app (127.0.0.1:8765)You must keep Dock running with the MCP server enabled (Settings → MCP) for the tools to work.
Requirements
- macOS 15 or later, on Apple Silicon or Intel
- Dock — ASO Tracker 4.1 or later, from the Mac App Store or from dock-app.com. Both versions carry the same bridge. An older Dock offers only the tools it knew at the time
- An MCP-compatible client. Tested with:
- Claude Desktop (recommended)
- Claude Code
- Codex
- Other clients that implement MCP over stdio
Installation
Option 1 — From Dock (recommended)
- Open Dock → Settings → MCP and turn on Enable MCP Server.
- Click Install Claude Desktop extension. Dock hands Claude Desktop the extension that ships inside it, so it always matches your version of Dock.
- Confirm the install in Claude Desktop. If it asks for the port, enter the one shown in Dock’s settings (
8765unless you changed it). - Done — Claude can now call any of the 34 tools.
If you prefer to install it by hand, Show in Finder next to the same button reveals the dock-aso.mcpb file: drag it into Claude Desktop → Settings → Extensions.
Option 2 — Claude Code and other clients
The bridge is the DockMCP executable inside the app, so there is nothing separate to install.
Claude Code. Dock → Settings → MCP → Other MCP clients shows the exact command, with the path to your copy of Dock and your port already filled in. It looks like this:
claude mcp add dock --env DOCK_PORT=8765 -- /Applications/Dock.app/Contents/MacOS/DockMCPAny other client. Point it at the same executable and set DOCK_PORT to the port shown in Dock. As a JSON configuration:
{
"mcpServers": {
"dock": {
"command": "/Applications/Dock.app/Contents/MacOS/DockMCP",
"env": { "DOCK_PORT": "8765" }
}
}
}Restart the client after changing its configuration.
Configuration
The extension accepts one optional setting:
| Key | Default | Description |
|---|---|---|
dock_port | 8765 | The port the Dock app listens on for MCP requests. Change this only if you’ve set a different port in Dock (Settings → MCP). |
In Claude Desktop, edit the value in Settings → Extensions → Dock — ASO Tracker → Configure.
Available tools
Every read tool is annotated readOnlyHint: true. Five tools change something, and they come in two kinds:
- destructive — the two
update_*_aso_contenttools edit your store listings. They are annotateddestructiveHint: true, which Claude Desktop renders as a confirmation prompt before each call. - local write — three Web Presence tools only add to lists inside Dock. Nothing is overwritten, so they are annotated
destructiveHint: falseand your client may not ask before calling them.
Subscription: the nine Web Presence tools and the two Invoicing tools need an active Dock subscription. The other 23 work without one, and get_app_intelligence adds download and revenue estimates and review sentiment when you have one.
Apps can be named the way you would say them — “Magica” — or by bundle id or package name. If a name matches more than one app, the tool says so and lists the candidates.
Apple App Store
| Tool | Hint | What it does |
|---|---|---|
get_apps_and_languages | read-only | List Apple apps configured in Dock with their languages and platforms. |
get_app_aso_content | read-only | Read title, subtitle, keywords, description, promotional text, what’s new. |
update_app_aso_content | destructive | Save edits as a local draft inside Dock (publish from the app). |
get_app_keywords_analysis | read-only | Detailed keyword analysis (popularity, difficulty, ranking, opportunity index). |
get_app_screenshots | read-only | Fetch App Store screenshots, iPhone Duo included, with each one’s size and screen, so the assistant can look at them. |
get_app_previews | read-only | App previews: processing status, size, a link to the video and its poster frame as an image. |
get_asset_library | read-only | The app’s Asset Library on App Store Connect, with each asset’s state and where it is used. Archived assets are left out unless asked for. |
get_product_page_creatives | read-only | The product page header and search results creative assets for one language. |
Keywords and history
| Tool | Hint | What it does |
|---|---|---|
get_app_evolution | read-only | How title, subtitle, keywords and keyword rankings changed across published versions. |
get_app_keyword_history | read-only | Ranking position over time for the keywords Dock tracks, one keyword or all of them. |
search_keyword | read-only | Fresh metrics for any keyword in any country, with no tracked app needed. |
App Intelligence (competitor research)
| Tool | Hint | What it does |
|---|---|---|
search_apps | read-only | Search the public App Store or Google Play catalogue for any app. |
get_app_intelligence | read-only | A report on any app by its store id: metadata and reviews, plus download and revenue estimates and review sentiment with a subscription. |
Google Play
| Tool | Hint | What it does |
|---|---|---|
get_google_apps_and_languages | read-only | List Google Play apps configured in Dock with their languages. |
get_google_app_aso_content | read-only | Read listing content plus Dock’s ASO score breakdown. |
update_google_app_aso_content | destructive | Save edits as a local draft inside Dock (publish from the app). |
Reviews
| Tool | Hint | What it does |
|---|---|---|
get_app_reviews | read-only | Apple App Store reviews with summary statistics, optionally filtered by rating. |
get_google_app_reviews | read-only | Google Play reviews with summary statistics, optionally filtered by rating. |
Sales, finance and invoicing
| Tool | Hint | What it does |
|---|---|---|
get_sales_summary | read-only | Sales summary across all apps for a month or year. |
get_finance_summary | read-only | Monthly financial report (proceeds, partner share, commission). |
get_finance_year | read-only | Yearly financial summary, fiscal or calendar year. |
get_invoicing_period | read-only | Who to invoice among Apple’s paying companies for one month of App Store proceeds, for how much, and what each share is made of. Subscription. |
get_invoicing_outstanding | read-only | The months whose money has arrived and whose invoices have not gone out yet. Subscription. |
Cross-platform
| Tool | Hint | What it does |
|---|---|---|
get_twin_apps | read-only | List linked Apple ↔ Google twin apps. |
get_twin_comparison | read-only | Side-by-side comparison of an Apple app and its Google twin. |
Web Presence (subscription)
These tools work for every app Dock tracks a website for, including a Mac app sold from its own site.
| Tool | Hint | What it does |
|---|---|---|
get_web_presence_apps | read-only | The apps Dock tracks a website for: domain, last scan and score, keywords followed on Google, open link building targets, and the state of the DataForSEO account. |
get_site_audit | read-only | The latest technical audit of the app’s website: score per area, every failing check with its fix, tips and facts. |
get_keyword_research | read-only | The phrases being considered for the site, with search volume, advertiser competition, seasonality and twelve months of history. |
get_google_results | read-only | Where the app stands on Google for the keywords it follows, and who else holds those pages. |
get_link_building_targets | read-only | Pages worth asking for a link: articles that name the app without linking it, and lists that leave it out. |
get_ai_answers | read-only | Where the site is quoted in answers AI assistants have already given, and which of its pages earn those citations. |
add_research_keywords | local write | Add phrases to the keyword research list. Free; reports what pricing them would cost. |
follow_keywords | local write | Start tracking keywords on Google. Free to follow; reports what reading them costs. |
update_link_building_target | local write | Record what happened with a link building target: its state, the address to write to, and what was promised. |
Example prompts
Once the extension is installed, you can ask Claude things like:
Discovery
“List all my apps in Dock with the languages they support.”
Keyword analysis
“Look at the keyword analysis for my app Magica in
en-USon iOS and tell me which keywords have the highest opportunity score.”
ASO rewrite (read → propose → write)
“Read the current App Store description for Magica in
de-DE, then suggest a rewritten version that emphasizes the new AI features. Once I approve, save it as a draft in Dock.”
Screenshot review
“Pull the iPhone 6.9″ screenshots for Magica in
en-USand review them: text readability, design consistency, conversion-focused messaging.”
Asset Library
“Which assets in the Asset Library for Magica are not used anywhere yet?”
Competitor research
“Search the US App Store for mileage tracker apps, then give me a report on the top three: what their listings promise and what their reviews complain about.”
Cross-platform consistency
“Compare the App Store and Google Play listings for Magica in
itand flag any inconsistencies in title, subtitle/short description, and keyword overlap.”
Reviews triage
“Get the 1- and 2-star Google Play reviews for Magica and group them by complaint type.”
Sales and invoicing
“Give me a sales summary for December 2025 across all my apps and highlight the top three by proceeds.”
“Which months still have to be invoiced to Apple, and for how much?”
Website
“Read the site audit for Magica and tell me which three fixes would raise the score most.”
“Find the articles that mention Magica without linking it, look up who wrote each one, and draft a short note to the first three. Don’t send anything.”
Tip: prefix any rewrite with “after I approve”. The
update_*tools already trigger Claude Desktop’s confirmation, but spelling it out keeps the assistant cautious.
How edits are applied
No tool publishes to a store, spends money, or sends email.
The two listing tools (update_app_aso_content, update_google_app_aso_content) never publish directly to the stores. They write to Dock’s local draft system:
- Apple drafts are stored in Dock and need your manual publish to App Store Connect from the app.
- Google Play drafts keep a field-level record of what changed and need an explicit publish.
This means you can have Claude prepare a complete localization update across many languages, review the changes inside Dock, and publish once when you’re satisfied.
The Asset Library and creative asset tools are read-only on purpose: placing or uploading an asset changes App Store Connect directly, with no draft in between, so that stays in Dock’s interface.
The three Web Presence writes only add to lists: a phrase to research, a keyword to follow, a note about a page you wrote to. Search data is bought with your own DataForSEO account from inside Dock, where the price is on screen; the tools report what the next step would cost and leave the decision to you. Following a keyword is free in itself, but a followed keyword is read on a schedule, within the monthly limit you set in Dock’s Settings › Web Data.
Troubleshooting
“Cannot reach the Dock app on localhost”
The Dock app is not running, or the MCP server is disabled. Open Dock → Settings → MCP and turn on Enable MCP Server. The server uses port 8765 by default; if you changed it, the extension’s dock_port must match.
“This feature requires a newer version of Dock”
The tool needs a version of Dock newer than the one installed. Update Dock from the Mac App Store, or with Check for Updates… in the version from dock-app.com.
“… needs an active Dock subscription”
The Web Presence and Invoicing tools are part of the subscription. Everything they show is also in Dock’s own screens; the answer will not change until the subscription is active, so retrying does not help.
“Found N apps matching X” (ambiguous match)
You asked for an app by name and Dock found more than one. Ask again with a more specific name, or with the exact bundle id or package name.
Tool calls work but Claude can’t see images from get_app_screenshots or get_app_previews
Make sure your client supports MCP image content. Claude Desktop does. Some clients fall back to text-only output and skip the images.
The extension appears installed but no tools show up
If you configured the client by hand, check that it points to the DockMCP executable inside the installed Dock.app (typically /Applications/Dock.app/Contents/MacOS/DockMCP). The extension installed from Dock’s settings finds the app on its own.
Fewer tools than listed here
The tools come from the copy of Dock you have installed. Update Dock to 4.1 or later to get all 34.
Apple Silicon vs Intel
The bundled DockMCP binary is universal; both architectures are supported.
Privacy
The extension does not transmit any data to remote servers. All MCP traffic stays on your Mac: Dock’s local server listens on the loopback interface only, so it cannot be reached from your network, and it refuses requests coming from a web page. App Store Connect, Google Play and Search Console data are fetched by the Dock app, not by the extension, using credentials kept in your Mac’s keychain.
Anything a tool returns is sent back to your AI assistant as part of the MCP response, so the model sees the same data you see in Dock. That includes one kind of data that is not yours: a link building target carries the address, title and public contact email of a page belonging to somebody else. Treat AI access to your business data accordingly.
The extension’s diagnostic log stays on your Mac. It records the address of each local request, which names what was asked for (an app, a language, a keyword), but never credentials or the content of an edit.
The full privacy policy, including a section on the extension, is at https://dock-app.com/privacy-policy/.
Support
Questions or issues with the extension: info@dock-app.com or https://dock-app.com/support/.
The extension ships inside Dock and is updated with it, so there is nothing to download separately.