MCP Catalogs
Home

appstore-connect-mcp

by TrialAndErrorAI·20·Score 43

A code mode MCP server for Apple App Store Connect with 923 endpoints accessible through just 2 tools.

developer-toolsproductivityfinance
6
Forks
0
Open issues
1 mo ago
Last commit
2d ago
Indexed

Overview

This MCP server provides an innovative 'Code Mode' approach to accessing Apple's App Store Connect API, which contains 923 endpoints. Instead of creating individual tools for each endpoint (which would require ~100K+ context tokens), the server provides just two tools: 'search' for querying the OpenAPI spec and 'execute' for making API calls. This approach automatically adapts when Apple updates their API, requiring zero maintenance from the server side. The server handles authentication via Apple's JWT system using a P8 key and provides security through a Node.js sandbox that restricts potentially dangerous functions.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Automate App Store metadata management including updating app descriptions, keywords, and screenshots
you:Monitor app analytics and customer reviews programmatically
you:Manage app builds, TestFlight beta testers, and version releases
you:What makes this different from traditional MCP servers?
you:How is authentication handled?

When to choose this

Choose this for development work with App Store Connect where you need programmatic access to the API without the overhead of maintaining 923 individual tool definitions.

When NOT to choose this

Avoid if you need a simpler tool-based interface without JavaScript coding, or if you require access to endpoints not covered by Apple's official API.

Tools this server exposes

2 tools extracted from the README
  • searchsearch(code)

    Write JS to query Apple's OpenAPI spec. Discover endpoints, check parameters, read schemas.

  • executeexecute(code)

    Write JS to call the API. Auth is automatic. Chain multiple calls.

Comparable tools

apple-mcpappstore-clifastlane

Installation

Install via Claude Code:

claude mcp add appstore-connect -s user \
  -e APP_STORE_KEY_ID=YOUR_KEY_ID \
  -e APP_STORE_ISSUER_ID=YOUR_ISSUER_ID \
  -e APP_STORE_P8_PATH=/absolute/path/to/AuthKey_XXXXXXXXXX.p8 \
  -e APP_STORE_VENDOR_NUMBER=YOUR_VENDOR_NUMBER \
  -- npx -y @trialanderror-ai/appstore-connect-mcp

Configure for Claude Desktop in ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "appstore-connect": {
      "command": "npx",
      "args": ["-y", "@trialanderror-ai/appstore-connect-mcp"],
      "env": {
        "APP_STORE_KEY_ID": "YOUR_KEY_ID",
        "APP_STORE_ISSUER_ID": "YOUR_ISSUER_ID",
        "APP_STORE_P8_PATH": "/path/to/AuthKey_XXXXXXXXXX.p8"
      }
    }
  }
}

FAQ

What makes this different from traditional MCP servers?
Instead of creating a separate tool for each of the 923 App Store Connect API endpoints, this server provides just 2 tools ('search' and 'execute') that allow the LLM to write JavaScript code to interact with the API directly. This reduces context usage from ~100K+ tokens to ~1K tokens and eliminates maintenance when Apple adds new endpoints.
How is authentication handled?
The server uses Apple's JWT authentication system. You need to provide a P8 key file, Key ID, and Issuer ID through environment variables. The JWT is automatically generated and injected into API calls without exposing credentials to the sandboxed code.

Compare appstore-connect-mcp with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.