Command Palette

Search for a command to run...

UnylyUnyly
Весь каталог

Mobile Release

БесплатноНе проверен

MCP server for managing mobile app releases on App Store Connect and Google Play. It exposes 101 tools for iOS and Android release lifecycle and reacts to EAS/G

GitHubEmbed

Описание

MCP server for managing mobile app releases on App Store Connect and Google Play. It exposes 101 tools for iOS and Android release lifecycle and reacts to EAS/GitHub webhooks automatically.

README

mobile-release-mcp — Ship iOS & Android from your AI agent

101 MCP tools · App Store Connect · Google Play · EAS & GitHub webhooks


npm version CI License: MIT Node.js MCP


npx -y mobile-release-mcp · Quick start · Tools · Credentials · Changelog


Install

# Run directly (recommended for MCP clients)
npx -y mobile-release-mcp

# Or install globally
npm install -g mobile-release-mcp
mobile-release-mcp

No deployment required for local use with Cursor or Claude Desktop.

Quick start

1. Get credentials

You need App Store Connect and/or Google Play API credentials. EAS webhooks do not replace these — see docs/CREDENTIALS.md.

2. Connect to Cursor or Claude Desktop

{
  "mcpServers": {
    "mobile-release": {
      "command": "npx",
      "args": ["-y", "mobile-release-mcp"],
      "env": {
        "APPLE_KEY_ID": "ABC1234DEF",
        "APPLE_ISSUER_ID": "00000000-0000-0000-0000-000000000000",
        "APPLE_PRIVATE_KEY_PATH": "/path/to/AuthKey.p8",
        "MCP_TOOLSET": "release"
      }
    }
  }
}

3. Ask your agent

"List my App Store apps and the latest build for each one."

Alternative: run from source

git clone https://github.com/Jeronimo0228/mobile-release-mcp.git
cd mobile-release-mcp
npm install
cp .env.example .env
# Edit .env with your credentials
npm run build
npm start

For local development from source, point MCP clients to node /path/to/dist/index.js instead of npx.

Why use this

Benefit What you get
Agent-native releases Agents call typed tools instead of fragile shell scripts around fastlane or manual store UI clicks
Cross-platform One MCP server for App Store Connect and Google Play
Webhook-driven CI EAS/GitHub events trigger agent workflows via list_pending_webhooks
Production-ready defaults Retries on rate limits, pagination, persistent webhooks, startup validation
Safe by default Destructive tools require confirm: true; toolsets limit agent surface area

Features

  • 101 MCP tools — iOS, Android, and shared release operations
  • Webhook listener — EAS (Build + Submit) and GitHub Actions (workflow_run)
  • Signature verification — HMAC-SHA1 (EAS), HMAC-SHA256 (GitHub); secrets required in production
  • Persistent webhooks — events saved to disk (WEBHOOK_STORAGE_PATH), survive restarts
  • Unified release flowtrigger_full_release for both platforms
  • Stdio + HTTP transports — local MCP clients or remote /mcp deployment
  • Configurable toolsetsall, release, or readonly via MCP_TOOLSET
  • Structured errors — consistent JSON errors with retry hints for agents

Documentation

Doc Contents
docs/CREDENTIALS.md Store credentials vs webhook secrets, EAS project mapping
docs/TOOLSETS.md Limiting tools for agents (MCP_TOOLSET)
docs/TOOLS.md Full tool catalog with categories
docs/ARCHITECTURE.md Transports, reliability, project layout
docs/SECURITY.md Supply chain, HTTP auth, deployment hardening
SECURITY.md Vulnerability reporting

Configuration

Copy .env.example to .env when running from source, or set env vars in your MCP client config.

Minimum for iOS:

APPLE_KEY_ID=ABC1234DEF
APPLE_ISSUER_ID=00000000-0000-0000-0000-000000000000
APPLE_PRIVATE_KEY_PATH=/path/to/AuthKey.p8
MCP_TOOLSET=release

All environment variables

Variable Default Description
APPLE_KEY_ID App Store Connect API key ID
APPLE_ISSUER_ID App Store Connect issuer ID
APPLE_PRIVATE_KEY_PATH Path to .p8 key file
APPLE_PRIVATE_KEY_BASE64 Alternative: base64-encoded key
GOOGLE_SERVICE_ACCOUNT_KEY_PATH Path to service account JSON
GOOGLE_SERVICE_ACCOUNT_JSON Alternative: inline JSON
MCP_TRANSPORT stdio stdio or http
MCP_HTTP_API_KEY Required in HTTP mode (≥32 chars). Bearer token for /mcp
MCP_ALLOWED_ORIGINS Comma-separated CORS origins (empty = disabled)
MCP_PORT 3000 HTTP server port (when http)
MCP_TOOLSET all all, release, or readonly
WEBHOOK_PORT 3000 Webhook port in stdio mode
WEBHOOK_STORAGE_PATH .data/webhooks.json Persistent webhook storage
WEBHOOK_REQUIRE_SECRETS true Reject webhooks without secrets
EAS_WEBHOOK_SECRET EAS HMAC secret
GITHUB_WEBHOOK_SECRET GitHub HMAC secret
EAS_PROJECT_MAPPINGS JSON map EAS project → store IDs
LOG_LEVEL info debug, info, warn, error

Requirements

Important: EAS webhooks notify you about builds — they do not provide store API credentials. See docs/CREDENTIALS.md.

HTTP deployment (remote MCP)

MCP_TRANSPORT=http
MCP_PORT=3000
EAS_WEBHOOK_SECRET=your-secret
GITHUB_WEBHOOK_SECRET=your-secret

Endpoints on a single server:

Endpoint Method Purpose
/mcp GET, POST, DELETE MCP Streamable HTTP transport
/webhook/eas POST EAS build/submit webhooks
/webhook/github POST GitHub Actions webhooks
/health GET Health check

Connect MCP clients to http://your-host:3000/mcp.

Deploy with npx mobile-release-mcp as the start command and env vars from your host's secret manager (Railway, Fly.io, etc.).

Webhook setup

EAS

eas webhook:create --event BUILD --url https://your-server.com/webhook/eas --secret your-eas-secret
eas webhook:create --event SUBMIT --url https://your-server.com/webhook/eas --secret your-eas-secret

GitHub Actions

Settings → Webhooks → Payload URL: https://your-server.com/webhook/github, events: Workflow runs.

EAS project mapping

Map Expo project names to store identifiers:

EAS_PROJECT_MAPPINGS=[{"projectName":"my-app","iosAppId":"1234567890","androidPackageName":"com.example.app"}]

Webhook flow

EAS/GitHub → POST /webhook/* → verify signature → persist to disk
  → Agent: list_pending_webhooks (includes mappedTargets)
  → Agent: trigger_full_release (confirm: true)
  → Agent: mark_webhook_processed

Examples

Release on both platforms

{
  "platforms": ["ios", "android"],
  "confirm": true,
  "ios": {
    "appId": "1234567890",
    "buildId": "abc-build-id",
    "versionString": "2.1.0",
    "releaseNotes": [{ "locale": "en-US", "whatsNew": "Bug fixes" }]
  },
  "android": {
    "packageName": "com.example.app",
    "versionCodes": ["42"],
    "track": "production",
    "status": "completed"
  }
}

React to EAS build webhook

1. list_pending_webhooks → check mappedTargets.appleAppId
2. apple_list_builds → verify build is VALID
3. trigger_full_release with confirm: true
4. mark_webhook_processed

See docs/TOOLS.md for the complete tool reference.

Development

npm run dev        # Run with tsx
npm run typecheck  # TypeScript check
npm run build      # Production build
npm test           # Run tests

Publishing instructions: docs/PUBLISHING.md

Project structure

src/
├── index.ts              Entry point
├── server.ts             MCP server factory
├── http/app.ts           HTTP transport (MCP + webhooks)
├── providers/apple/      App Store Connect API
├── providers/google/     Google Play Developer API
├── tools/                MCP tool registrations
├── webhook/              Webhook routes, storage, parsers
└── utils/                Config, retry, errors, tool registry
docs/                     Detailed documentation
tests/                    Unit tests

License

MIT — see LICENSE.

from github.com/Jeronimo0228/mobile-release-mcp

Установить Mobile Release в Claude Desktop, Claude Code, Cursor

Рекомендуется · одна команда, все IDE
unyly install mobile-release-mcp

Ставит в Claude Desktop, Claude Code, Cursor и VS Code — сам разбирается с npx, uvx и сборкой из исходников.

Впервые? Поставь CLI: curl -fsSL https://unyly.org/install | sh

Или настроить вручную

Выполни в терминале:

claude mcp add mobile-release-mcp -- npx -y mobile-release-mcp

Пошаговые гайды: как установить Mobile Release

FAQ

Mobile Release MCP бесплатный?

Да, Mobile Release MCP бесплатный — установка в пару кликов через Unyly без оплаты.

Нужен ли API-ключ для Mobile Release?

Нет, Mobile Release работает без API-ключей и переменных окружения.

Mobile Release — hosted или self-hosted?

Self-hosted: сервер запускается локально на твоей машине командой из раздела установки.

Как установить Mobile Release в Claude Desktop, Claude Code или Cursor?

Открой Mobile Release на unyly.org, выбери вкладку своего клиента (Claude Desktop, Claude Code, Cursor) и нажми Install — конфиг сгенерируется автоматически, без правки JSON.

Похожие MCP

Compare Mobile Release with

Не уверен что выбрать?

Найди свой стек за 60 секунд

Автор?

Embed-бейдж для README

Похожее

Все в категории development