App MCP Server

MCP server for App Store Connect & Google Play Console — iOS/Android app management. The app mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 12 defined tools rather than through you.

What it actually does

A unified MCP (Model Context Protocol) server for App Store Connect and Google Play Console. Manage app listings, screenshots, releases, reviews and submissions — all from your AI assistant.

Its toolset

Everything the assistant can do here goes through one of these:

• Category — Tools
• Versions — apple_list_versions, apple_create_version
• Screenshots — apple_list_screenshot_sets, apple_create_screenshot_set, apple_upload_screenshot, apple_delete_screenshot
• Builds — apple_list_builds, apple_assign_build
• Submission — apple_submit_for_review, apple_cancel_submission
• Pricing — apple_get_pricing, apple_set_price, apple_list_availability
• Certificates — apple_list_certificates, apple_create_certificate, apple_revoke_certificate
• Devices — apple_list_devices, apple_register_device, apple_update_device
• Testers — google_get_testers, google_update_testers
• Images — google_list_images, google_upload_image, google_delete_image, google_delete_all_images
• Reviews — google_list_reviews, google_get_review, google_reply_to_review
• Subscriptions — google_list_subscriptions, google_get_subscription, google_archive_subscription

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 6 environment variables: APPLE_KEY_ID, APPLE_ISSUER_ID, APPLE_P8_PATH, GOOGLE_SERVICE_ACCOUNT_PATH, YOUR_KEY_ID, YOUR_ISSUER_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. App's toolset — Category, Versions, Screenshots and 9 more — is a fair guide to whether it matches your workflow. It is maintained by mikusnuz; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch App.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the app mcp server does with a few real requests.