AppLaunchFlow MCP server

AppLaunchFlow MCP

Pro allowance and Automation

API and MCP exports require an active Pro subscription. Pro includes 5 export jobs per month, shared across all API keys, projects and MCP clients. One job includes its requested languages and device formats. Annual Pro also receives a monthly allowance. Editor exports keep their existing limits.

Add Automation for €19/month on top of Pro for unlimited API exports. Rate limits, job-size limits and AI generation credits still apply.

Use await client.getApiUsage() (requires exports:read) to check used, remaining, unlimited and resetsAt. The API returns HTTP 402 with code apiexportquotaexhausted when the monthly allowance is exhausted, and HTTP 403 with apipro_required without Pro. Replaying the same idempotency key does not spend another export. Failed and canceled jobs restore their credit; an uncertain dispatch remains reserved until its outcome is known. Polling and downloads are included.

MCP server for AppLaunchFlow — create App Store & Google Play screenshots with AI.

Official API and CI releases

The MCP and the Node SDK now share the versioned /api/v1 API. Import AppLaunchFlow from applaunchflow/api for project-scoped API key authentication, active-variant editing, asynchronous renders and checksum-verified downloads. Browser OAuth remains the normal way to connect MCP.

Use the CI and Fastlane example. Update captures and localized copy directly in the active variant, then render with projectId, languages and formats. CI keys need asset, design read/write and export scopes. HTTP API reference.

Release ordering: 0.7.0 requires the dashboard v1 API and validating bundler to be enabled before this MCP/SDK release is published or deployed.

Connect

Cursor marketplace plugin

This public repository includes a Cursor plugin manifest in .cursor-plugin/plugin.json and a root mcp.json targeting the hosted service. No API keys or local server are required. After installing, authorize AppLaunchFlow through Cursor's MCP settings using your AppLaunchFlow account. Existing plan limits apply; installing the plugin does not grant a paid AppLaunchFlow subscription.

Try "List my AppLaunchFlow projects", then "Show the screenshot styles for this project using its existing screenshots". Choose the style in the interactive picker; preparing previews does not select a design for you. The same flow supports social graphics and promo videos. Asset uploads and management are available from the asset browser.

If you already configured AppLaunchFlow manually, disable the duplicate MCP entry when installing the plugin. Support: support@applaunchflow.com.

Maintainers: validate with npm test, then submit the public repository at https://cursor.com/marketplace/publish. Cursor reviews marketplace listings separately from npm and the MCP Registry. The Cursor plugin version tracks its packaging release; the remotely hosted server can receive independent updates.

AppLaunchFlow is a hosted MCP connector with OAuth 2.1 and PKCE. No API key, local token, or scoped npm package name is required.

Codex

The shortest setup command configures the hosted connector and opens OAuth:

npx -y applaunchflow connect codex

Useful follow-up commands:

npx -y applaunchflow status
npx -y applaunchflow disconnect

The equivalent native Codex commands are:

codex mcp add applaunchflow --url https://mcp.applaunchflow.com/mcp
codex mcp login applaunchflow
codex mcp get applaunchflow
codex mcp remove applaunchflow

Claude Code

The same one-command setup is available for Claude Code. It replaces a legacy AppLaunchFlow entry when necessary, adds the hosted HTTP connector, and opens OAuth sign-in:

npx -y applaunchflow connect claude

The equivalent native Claude Code commands are:

Shortened. The full README is on GitHub.