AppFactory

An MCP server that lets your coding agent take a SwiftUI iOS subscription app from idea to the App Store.

What it does: idea harvesting and validation, design, SwiftUI code from a template, Supabase backend, App Store Connect + RevenueCat setup, localization, analytics, ASO, screenshots and TestFlight. Every stage has a gate the agent must pass. You do the final App Store submission.

Quickstart

Requires a Mac, Python 3.12+ and uv.

1. Add the MCP to your agent

Like any MCP server. Research works with no keys at all:

2. Add keys for the services you use

Keys are environment variables on the MCP entry, named APPFACTORY_<KEY>. For example, App Store Connect in Claude Code:

claude mcp add appfactory -s user \
  -e APPFACTORY_ASC_KEY_ID=ABC123DEFG \
  -e APPFACTORY_ASC_ISSUER_ID=00000000-0000-0000-0000-000000000000 \
  -e APPFACTORY_ASC_KEY_FILEPATH=~/keys/AuthKey_ABC123DEFG.p8 \
  -e APPFACTORY_TEAM_ID=TEAMID1234 \
  -- uvx appfactory@latest

You don't need to know the names up front: say "Set up AppFactory" (or just start a run). The agent asks which services you want, one by one, and gives you the exact command for your agent with the keys that are still missing. Keys never go through the chat. Every variable is listed in docs/SETUP.md.

Then try this first prompt. It needs no accounts:

Find 3 underserved iOS app niches in Health & Fitness and validate the best one

Works with

Claude Code, Codex CLI, Gemini CLI and Cursor. The run playbook is served by the MCP server itself (tool playbook(), prompt run, resource appfactory://playbook), so any MCP-capable agent can follow it.

Choose what you use

Every service is optional. Tools for a disabled service do nothing and the pipeline skips those stages (appfactory services enable|disable NAME).

Details and credential steps: docs/SETUP.md.

Safety

• Approvals. Irreversible or outward actions (submission, store/backend/RevenueCat writes, GitHub pushes, uploads) do not run when an agent calls them. They wait for appfactory approve <id> in your terminal.
• Dry run by default for deploys, repo creation, uploads and issue writes.
• Secrets stay local and are scrubbed from every tool result.
• Untrusted content (App Store listings, reviews) is labelled as data, not instructions.

Full threat model and limits: SECURITY.md.

How a run works

1. Interview. Before any work the agent calls run_options(), asks you about every optional part, and saves your answers. Anything you turn off is skipped.
2. Pipeline with gates. scaffold, design, features, backend, store setup, localize, analytics, ASO, metadata, screenshots, TestFlight. A stage is done only when pipeline_mark passes its gate; blockers stop the run with a NEEDS_HUMAN.md.
3. You submit. App Store submission is always human, in the App Store Connect web UI.

Docs

• docs/SETUP.md: credentials and per-app choices
• docs/PIPELINE_PLAYBOOK.md: the why, order and gotchas of every stage
• docs/TOOLS.md: every tool (generated)
• CONTRIBUTING.md, SECURITY.md, AGENTS.md

License

MIT