Appfactory

io.github.gbatistuta0Published by GitHub account gbatistuta0v0.2.0Updated Oct 11, 2026

Lets your coding agent ship a SwiftUI iOS subscription app from idea to TestFlight.

Overview

AI-generated overview

Lets a coding agent take a SwiftUI iOS subscription app from idea validation through build, backend, store setup and TestFlight.

What you can do
AppFactory is a local MCP server that walks a coding agent through building an iOS subscription app. It harvests App Store data to score niches and check name availability, downloads competitor screenshots for design research, scaffolds a SwiftUI app from a template, and can set up Supabase backend, App Store Connect listings, RevenueCat subscriptions, localization, ASO assets and TestFlight uploads. Each stage has a gate, and irreversible actions wait for the user to run an approval command in their own terminal.
When to use it
Use it when you want an agent to ship a subscription-based iOS app end to end, from idea validation to a TestFlight build, on a Mac. It suits solo developers who want research, scaffolding and store plumbing automated while keeping control of submissions and destructive changes.
Requirements
A Mac and uv; Xcode and other tools only for the services you enable. Optional services need their own credentials and CLIs: App Store Connect API key (APPFACTORY_ASC_KEY_ID, APPFACTORY_ASC_ISSUER_ID, APPFACTORY_ASC_KEY_FILEPATH, APPFACTORY_TEAM_ID), Supabase access token, RevenueCat secret key, provider keys for AI, plus firebase, gh, Maestro, Java 17+, node and claude-design MCP depending on what you turn on.
Before you install
It asks for store, backend and subscription credentials such as APPFACTORY_ASC_KEY_FILEPATH, Supabase access token and RevenueCat secret key, which stay on your machine and are masked in results. Store writes, backend deploys, database changes, GitHub pushes, uploads and signing require explicit approval via appfactory approve; destructive SQL always does. App Store submission is always manual. Data goes only to services you enable, with your own keys.

Installation

In SourceWeft

  1. Open Appfactory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.2.0LatestOct 11, 2026
  2. v0.1.5Sep 29, 2026
  3. v0.1.4Sep 29, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.