MCP server overview
The Asomium MCP server — 35 tools that drive the full release workflow from inside any MCP-aware AI client.
The Asomium MCP server is a companion binary that exposes every action you can take in the Mac app as an MCP tool. That lets you drive the full release workflow from inside any MCP-aware client — Claude Code, Claude Desktop, Cursor, Windsurf — without context-switching to a GUI.
Currently 35 tools spanning discovery, metadata editing, translation, keyword tracking, snapshots, app info, reviews, build & ship, release control, screenshots, monetization, analytics, visualization, and account. See Tool reference for the full live list (auto-generated from the running server).
Why MCP and not a CLI
A CLI works fine for scripted tasks (“run this on every commit”), but the release workflow is dialogical: you pull a piece of metadata, look at it, decide what to translate, push back, check the result. An LLM driving an MCP server is the natural shape for that flow — and you already have an LLM open in another window anyway.
The dashboard tool (asomium_dashboard) is the clearest payoff: one
call fans out 4–6 ASC reads in parallel and returns a structured
payload your AI client can render as a single interactive dashboard
artifact (in Claude.ai / Desktop) or paraphrase in markdown (in
Claude Code).
Architecture
┌────────────────┐ stdio ┌──────────────────┐
│ Claude / IDE │ ◄─────────────► │ asomium-mcp │
└────────────────┘ │ (companion bin) │
└────────┬─────────┘
│ reads handoff JSON
▼
┌────────────────────┐
│ Application │
│ Support / │
│ ReleaseKit/ │
│ (workspace id + │
│ build configs + │
│ keyword tracking)│
└────────┬───────────┘
│
▼
┌────────────────────┐
│ App Store Connect │
│ + iTunes Search │
│ + Anthropic API │
└────────────────────┘The MCP binary is stateless across runs — it reads the workspace identifier from a tiny handoff JSON the Mac app writes, then pulls ASC credentials from the per-workspace Keychain entry. Both the GUI and MCP processes share the same Keychain access via plain POSIX file permissions (they run as the same user) — no entitlement gymnastics required.
The MCP server keeps a small amount of its own on-disk state
under ~/Library/Application Support/ReleaseKit/com.mariopek.releasekit/:
mcp-build-configs.json— per-app Xcode project / scheme / platformkeyword-tracking.json— tracked keywords + rank-snapshot historysnapshots/<bundleId>/*.json— saved metadata snapshots for diffingusage-counter.json— current-month translate-call counter
Does it cost extra
The MCP server is included with every tier — BYO ($7.99/mo), Pro Monthly ($14.99/mo), and Pro Annual ($119.99/yr). Translation calls made through MCP count against the same token bucket as in-app translations:
- BYO users — translations hit your own Anthropic key
- Pro users — translations consume tokens from your monthly allotment; out-of-tokens you can buy a top-up pack (50/100/200) as a consumable IAP inside the Mac app
Every other tool (push_metadata, build_and_ship, submit_for_review, list_builds, screenshots, ASO, dashboard, render_chart) is free — they hit Apple’s APIs or local state and don’t touch an LLM.
What clients work
| Client | Status | Notes |
|---|---|---|
| Claude Code | ✅ | Full support, artifacts not available (chart tool returns SVG you can save + open) |
| Claude Desktop | ✅ | Full support, React/SVG artifacts render inline |
| Claude.ai (web) | ✅ | Via the MCP connector — chart payloads become recharts artifacts |
| Cursor | ✅ | Full support, no artifact rendering |
| Windsurf | ✅ | Full support, no artifact rendering |
See Install the Mac app for the one-time setup and Auth & local state for the credentials story.