Built for agents. Governed by people.

Take an app from draft to store.

A discoverable, project-scoped operating layer for App Store Connect and Google Play—with explicit approval before anything goes live.

01

Onboard

Connect live, unpublished, or pre-store apps and produce a readiness audit.

02

Create

Draft metadata, screenshots, icons, legal copy, and campaign-specific store pages.

03

Ship

Preview changes, request human approval, then publish through scoped store credentials.

Connect with Claude

Prepare your listing with Claude.

Review launch readiness, draft and translate listing text, and view or organize existing screenshots and icons. Review the exact text before saving. Live store updates require a connected store and your approval in App Listing Agent. The Claude connector does not generate or edit images with AI.

  1. Create an App Listing Agent account or sign in, and select an existing app project. An app without a store record can still have a local draft.
  2. In Claude, open Settings → Connectors and add a custom connector named App Listing Agent.
  3. Enter this remote MCP server URL:https://applistingagent.com/api/mcp/claude
  4. Connect and complete the App Listing Agent sign-in. Choose the app and access level you want Claude to use. Keep passwords and store credentials in the secure sign-in flow.
  5. Start a new Claude conversation with the connector enabled. Ask: “Show my app’s launch readiness. Do not publish anything.”

To localize a listing, ask for a preview of the app name and subtitle in your chosen language, then approve the fields you want saved. Translation and other AI text checks may use your plan allowance. To review artwork without generating anything, ask: “Show my app’s saved screenshots.”

If the app or permissions are incorrect, reconnect and choose the intended project. You can revoke OAuth agent access in App Listing Agent Settings; this revokes all OAuth agent connections for your account. Contact support if a connection needs help.

For ChatGPT and other agents, follow the existing MCP setup guide. The Claude connection has its own URL and available tools.

Public contract

Clear capabilities for each connection.

The public capability manifest describes the full integration. The tools available to a connection depend on its setup, selected project and permissions. Claude supports listing text and existing artwork.

Full integration tools55
Credential handlingSecure handoff only
PublishingHuman approval
Project boundaryEnforced
External contentUntrusted data

Your agent gets a job. Not the keys to everything.

Start with a one-time pairing code or scoped OAuth. Grant only the project and abilities the agent needs. Store content is treated as untrusted data, and every live-store change waits for your approval.

Read the agent setup guide