Which integrations are available for this server?

Allows managing iOS app releases and builds on App Store Connect, including listing apps and builds, and initiating release workflows. Receives EAS Build and EAS Submit webhooks to react to build and submission events and automate release workflows. Receives GitHub Actions workflow webhooks to react to CI/CD events and trigger automated release processes. Allows managing Android app releases on Google Play Console, including uploading builds, managing tracks, and releasing to production.

How do I use mobile-release-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mobile-release-mcp List my App Store apps and the latest build for each one." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

mobile-release-mcp

by Jeronimo0228

Overview Schema Related Servers Score Discussions

TypeScript

Hybrid

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

npm version 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.

Related MCP server: app-publish-mcp

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 flow — trigger_full_release for both platforms
Stdio + HTTP transports — local MCP clients or remote /mcp deployment
Configurable toolsets — all, 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

Node.js >= 20
App Store Connect API key (for iOS tools)
Google Play service account (for Android tools)

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.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

asc-mcp
Developer Tools App Automation Project Management
zelentsov-dev
A
license
-
quality
A
maintenance
MCP server for App Store Connect API with 208 tools across 25 workers. Manage apps, builds, TestFlight, in-app purchases, subscriptions, reviews, provisioning, screenshots, analytics, and more — directly from Claude, Cursor, VS Code, or any MCP client. Multi-account support, worker filtering, JWT auth.
Last updated 2026-07-21
51
MIT
app-publish-mcp
Developer Tools App Automation E-commerce & Retail
mikusnuz
A
license
B
quality
D
maintenance
Unified MCP server for App Store Connect & Google Play Console — manage listings, screenshots, releases, reviews & submissions
Last updated 2026-03-19
91
143
23
MIT
xcode-cloud-mcp
CI/CD & DevOps Developer Tools
thatfactory
A
license
B
quality
A
maintenance
MCP server for managing Xcode Cloud workflows, builds, and test artifacts via the App Store Connect API.
Last updated 2026-06-18
15
25
1
MIT
ShipKit
Developer Tools App Automation CI/CD & DevOps
marumemomo
A
license
-
quality
D
maintenance
MCP server for shipping iOS apps, enabling screenshots of simulators, managing App Store Connect metadata, and submitting apps for review.
Last updated 2026-04-08
15
MIT

View all related MCP servers

Related MCP Connectors

Appcircle MCP
MCP server for Appcircle mobile CI/CD platform.
Supabase
MCP server for interacting with the Supabase platform
Azure DevOps (ADO)
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.

View all MCP Connectors

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jeronimo0228/mobile-release-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server