Connect your assistant. Keep your permissions.

1. Create a team-scoped token

Open the MCP step in onboarding or account settings. Start with WRITE for research and drafts, or READ for inspection. Copy the token once and store it securely; never paste it into a public chat or repository.

2. Use your workspace endpoint

Copy the endpoint shown in onboarding. If no endpoint is configured, contact support; do not guess a production URL. Remote clients use the URL with an Authorization: Bearer header. For Cursor, add this server configuration with your own values.

Cursor remote MCP configuration - replace the placeholders

{
  "mcpServers": {
    "asoplan": {
      "url": "<YOUR_WORKSPACE_MCP_URL>",
      "headers": {
        "Authorization": "Bearer <YOUR_TEAM_TOKEN>"
      }
    }
  }
}

3. Choose a compatible client

Claude Code supports HTTP MCP setup. Desktop clients may require an MCP bridge; use the generated onboarding instructions. ChatGPT remote connector access depends on plan, workspace and authentication support. Confirm compatibility rather than putting a token in an unsupported field.

4. Request a bounded draft

Ask: Research this app for the US storefront, use my uploaded real screenshots, and propose an English listing. Show the quote and evidence before starting. Do not publish.

Prepare an ASO draft for my app in en-US. Use my real screenshots. Show the budget and evidence. Do not publish.

5. Review, then authorize separately

Check claims, locale, screenshots and the listing diff. Publishing needs scoped PUBLISH authorization, approved QA, current ownership and explicit dryRun=false and confirm=true. A failed or blocked step is not a completed store update.