MCP connector

Appo offers a remote MCP (Model Context Protocol) connector at https://apps.goappo.io/mcp. An AI assistant connected to it can create an app from a website, let you try it on a phone, and publish it to the App Store and Google Play. Nothing is installed locally and no token is managed by hand.

Connect

The appo command-line tool registers the connector on every supported agent it finds on the PATH (Claude Code and Codex):

npx @appolabs/appo mcp

For each agent it registers, it also adds a short section, delimited by <!-- appo-start --> and <!-- appo-end -->, to that agent's user-level instructions file (~/.claude/CLAUDE.md for Claude Code, ~/.codex/AGENTS.md for Codex). The section tells the agent that an app of this kind lives in Appo, so that a request such as "what is the status of my app" is not read as a question about the working directory. The section can be edited or removed freely.

To add the connector by hand, use the address https://apps.goappo.io/mcp in the client of your choice.

Claude Code:

claude mcp add --transport http --scope user appo https://apps.goappo.io/mcp

Codex CLI:

codex mcp add appo --url https://apps.goappo.io/mcp

Claude on the web and Claude Desktop: open Customize, then Connectors, choose Add custom connector, enter the address and select Sign in now. When the dialog offers a choice of OAuth client mode, select Register automatically.

Other clients that accept a remote MCP server by URL, such as ChatGPT, Cursor, Windsurf and VS Code, take the same address. For a client that reads a JSON configuration:

{ "mcpServers": { "appo": { "url": "https://apps.goappo.io/mcp" } } }

Client options change between releases; the client's own help output or connector dialog is authoritative for the exact flags and labels.

Sign in

The first use opens Appo's sign-in, followed by a consent screen that names the client and the single permission requested. Sign-in is by Google or by email and password. Access can be revoked from the client.

What you can do

• Create the app from the address of its website.
• Adapt the website to the app. This is done by the site's developer, or by Appo's team, typically within 24 to 48 hours.
• Try the app through one preview link that works on every phone: it is opened on the phone, or scanned as a QR code from a computer.
• Publish to the stores. Publication requires an active subscription for the app and an explicit confirmation.
• Follow store review and handle a rejection.
• Send push notifications.
• Adjust the icon, the permissions and the appearance of the app.

What it does not do

Payment and subscription management stay in the Appo dashboard, which the connector points to with a link.

Privacy, terms and support

• Privacy policy
• Terms of service
• Contact

Next

• Tool reference: every tool, its outcome and its gate.