Shipkit

io.github.readmigoPublished by GitHub account readmigov0.1.1Updated Oct 24, 2026

Unified app publishing MCP Server for Google Play, App Store, and 10+ Chinese stores

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant publish and manage mobile app releases across Google Play, the App Store, and 10+ Chinese app stores from one local MCP server.

What you can do
Shipkit is a local MCP server for unified app publishing. According to its registry description, it covers Google Play, the App Store, and more than ten Chinese app stores through a single interface. The manifest does not list individual tools, so the exact operations are not documented here; it keeps job state in a local SQLite database.
When to use it
Consider it when you ship the same mobile app to several stores, especially when Chinese stores are part of the release matrix, and you want an assistant to drive publishing steps instead of switching between store consoles.
Requirements
Runs as a local stdio process on a desktop machine, installed from the npm package @readmigo/shipkit-mcp, so Node.js is needed. Requires a ShipKit API key supplied as the SHIPKIT_API_KEY environment variable. Optionally set SHIPKIT_DB_PATH to choose the SQLite job database location; the default is ~/.shipkit/jobs.db. Network access is needed to reach the store services.
Before you install
The server asks for a ShipKit API key (SHIPKIT_API_KEY), which is a credential and should be stored and scoped carefully. Publishing actions can push, update, or release app listings on live stores, so review what the assistant is about to submit before confirming. Job data is written to a local SQLite file whose path is set by SHIPKIT_DB_PATH.

Installation

In SourceWeft

  1. Open Shipkit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.