ShipKit — Unified App Publishing

ShipKit is a unified MCP server that lets you publish apps to multiple app stores with a single natural language command. It handles authentication, artifact uploads, metadata translation, compliance checks, and multi-store orchestration, so you can manage all publishing tasks from one place rather than juggling separate workflows.

How to use

You will interact with ShipKit through an MCP client or AI agent to publish, update, or monitor apps across many stores. Start by connecting your configured stores, then run publishing actions such as uploading builds, updating metadata, and submitting releases. ShipKit provides a single, consistent interface for all supported stores and handles store-specific intricacies on your behalf.

How to install

Prerequisites: you need Node.js installed on your machine. You also need an MCP client or agent that can communicate with an MCP server. The ShipKit MCP server can be run locally as part of your development workflow.

Install the ShipKit MCP client tooling using the provided command for your environment. You will configure an MCP server entry to run ShipKit in your client.

claude mcp add shipkit -- npx -y @readmigo/shipkit-mcp

{
  "mcpServers": {
    "shipkit": {
      "command": "npx",
      "args": ["-y", "@readmigo/shipkit-mcp"],
      "env": {
        "SHIPKIT_API_KEY": "sk-your-api-key-here"
      }
    }
  }
}

First-Time Setup: Connect Your Stores

You must authenticate with each store you want to publish to. ShipKit securely stores credentials and refreshes tokens automatically. Below are the setup steps and credential examples for the stores that are commonly used.

# Google Play setup via the AI-assisted flow
$ claude
> Connect me to Google Play
> I'll need your service account key...

{
  "type": "service_account",
  "project_id": "your-project-id",
  "private_key_id": "key-id",
  "private_key": "-----BEGIN PRIVATE KEY-----\\n...\\n-----END PRIVATE KEY-----\\n",
  "client_email": "your-sa@your-project.iam.gserviceaccount.com",
  "client_id": "123456789",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token"
}

{
  "issuerId": "your-issuer-id",
  "keyId": "your-key-id",
  "privateKey": "-----BEGIN PRIVATE KEY-----\\n...\\n-----END PRIVATE KEY-----"
}

{
  "clientId": "your-client-id",
  "clientSecret": "your-client-secret"
}

Usage flow after setup

Once you have stores connected, you can perform end-to-end publishing. Typical flows include checking status across platforms, uploading builds, and submitting releases for review across the configured stores.

Available tools

store.list

List all configured stores and their connection status

store.connect

Configure and authenticate with an app store

app.upload

Upload APK/AAB/IPA/HAP build artifacts to stores

app.listing

View and update store listings (title, description, screenshots, etc.)

app.release

Manage release tracks, phases, and rollout percentages

app.status

Query review status and analytics across platforms

app.publish

Submit app for review or publish immediately to specified stores

compliance.check

Pre-submission compliance checks (ICP, privacy policy, icon specs, etc.)