home / mcp / appstore connect mcp server

AppStore Connect MCP Server

Provides access to App Store Connect metrics and finance data via Claude through a dedicated MCP server.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "trialanderrorai-appstore-connect-mcp": {
      "command": "node",
      "args": [
        "/path/to/appstore-connect-mcp/dist/index.js"
      ],
      "env": {
        "APP_STORE_KEY_ID": "YOUR_KEY_ID",
        "APP_STORE_P8_PATH": "/path/to/key.p8",
        "APP_STORE_ISSUER_ID": "YOUR_ISSUER_ID"
      }
    }
  }
}

You have an MCP server that bridges App Store Connect data into Claude. It provides authenticated access to App Store Connect metrics and exposes a set of tools you can use to retrieve financial, subscription, and usage data directly from Claude, without manual exports or fragile integrations.

How to use

You interact with the App Store Connect MCP Server through your MCP client. After you configure the server, you can ask Claude to fetch metrics like monthly recurring revenue, active subscribers, or app analytics. The server exposes eight tools you can call to collect data, run reports, and check API health. Use natural language prompts that map to these tools, for example: asking for revenue metrics, subscription analytics, or a quick health check of the connection.

How to install

{
  "displayName": "App Store Connect MCP Server",
  "shortDescription": "MCP server to fetch iOS metrics from App Store Connect for Claude access.",
  "mcpServers": {
    "appstore_connect": {
      "type": "stdio",
      "name": "appstore_connect",
      "command": "node",
      "args": ["/path/to/appstore-connect-mcp/dist/index.js"],
      "env": {
        "APP_STORE_KEY_ID": "YOUR_KEY_ID",
        "APP_STORE_ISSUER_ID": "YOUR_ISSUER_ID",
        "APP_STORE_P8_PATH": "/path/to/key.p8"
      }
    }
  }
}

Additional sections

This MCP server is designed to be set up locally and run as a small, typed service that authenticates with App Store Connect using a short-lived JSON Web Token (JWT) built from a private key (.p8). The server runs in a standalone process and is configured through a Claude Desktop integration that launches the Node-based MCP implementation.

Configuration and security notes

Configuration involves running the server locally and wiring it into Claude Desktop. You will provide a private key (.p8), a key ID, and an issuer ID to authenticate with App Store Connect. Keep the .p8 file private and restrict access to the machine where Claude Desktop runs. Tokens refresh automatically, but you should monitor for any authentication errors and verify your key permissions in App Store Connect.

Troubleshooting

If you encounter connection or data issues, check the following: verify your environment variables are set correctly, ensure the build output is reachable at the path you supply, and confirm Claude Desktop is restarted after configuration changes. Use the built-in test tool to validate the connection and scan logs for authentication or rate-limiting messages.

Notes

The server currently exposes eight tools to Claude for data access and reporting. You can run tests to confirm connectivity and verify API health before relying on data in dashboards.

Available tools

list_apps

Get all apps in your account

get_app

Get detailed app information

get_sales_report

Fetch sales and subscription data

get_revenue_metrics

Calculate MRR, ARR, churn

get_subscription_metrics

Subscription analytics

get_app_analytics

User engagement metrics

test_connection

Verify API access

get_api_stats

Rate limit monitoring