App Listing Agent

npx add-mcp 'https://applistingagent.com/api/mcp'

MCP Server

Markdown version of https://applistingagent.com/docs/mcp. Index of every docs page for agents: https://applistingagent.com/llms.txt

Give Codex, Claude Code, Cursor, and other MCP-compatible AI agents the tools to prepare and ship your store presence.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI agents such as ChatGPT, Claude, Codex, and Cursor use external tools and services. Our MCP server exposes a focused set of tools for metadata, screenshots, icons, localization, legal pages, and campaign-specific store pages.

Natural Language

Ask your agent to translate your app or generate screenshots

Secure

Project-scoped OAuth; store credentials never pass through chat

Focused launch tools

55 reviewed tools for creating and shipping store assets

Remote connection

App Listing Agent is hosted. Add its HTTPS endpoint to a remote-MCP client; no npm package or local process is required.

Streamable HTTP text:

https://applistingagent.com/api/mcp

Configuration

OAuth-capable clients open a browser authorization flow. Existing scoped API keys can use this generic remote-server configuration:

Remote MCP configuration json:

{
  "mcpServers": {
    "applistingagent": {
      "url": "https://applistingagent.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <ASC_API_KEY>"
      }
    }
  }
}

Use the least authority

OAuth connections select one app workspace and an authority level. Start with review-only or draft access; publishing always requires a separate human approval.

Usage

Once connected, ask your agent for store work in plain language. Read-only audits run immediately; anything that would change a live listing waits for your approval.

Example Conversation text:

User: Is Atlas Habit ready to submit to the App Store?

Agent: I'll run a read-only readiness audit and show the result inline.

[Uses run_store_readiness_audit, then show_readiness_report]

Atlas Habit has 3 blockers. The first one to fix: App Store Connect is
not connected. Drafting can continue safely; publishing will wait for
your approval. Want me to walk through the first blocker?

Available Tools

Standard accounts can use 55 tools organized around the store-launch workflow. A few common ones are below; the tool reference lists every tool with its parameters, required key scope and approval rule.

Common tools

• run_store_readiness_audit: Check a project for launch blockers without changing anything

• translate_metadata: Translate listing fields into other locales with AI

• update_metadata: Save listing fields for one locale as a local draft

• upload_app_store_metadata: Upload saved listing fields to App Store Connect (approval required)

• upload_google_play_metadata: Upload saved listing fields to Google Play Console (approval required)

• upload_metadata_to_both_stores: Upload saved listing fields to both stores (approval required)

• generate_screenshot: Create one marketing screenshot from a raw app screenshot

• generate_screenshot_set: Create a styled set of marketing screenshots as a background job

• suggest_headlines: Suggest headline text for an existing screenshot

• generate_icon: Create an app icon and save iOS and Android sizes

• list_locales: List the locale codes each store supports

• check_project_configuration: List missing store identifiers, credentials or base listing fields

Security

Every request to the MCP server is:

• Authenticated with project-scoped OAuth or a scoped API key
• Encrypted in transit (HTTPS)
• Pseudonymous security telemetry without prompts or credentials
• Rate limited by network and account

Credential security

Prefer OAuth or the one-time pairing flow. If an existing client uses an API key, keep it in that client's secret store and never commit it to a repository.