Use the right tool for the actual release task.
AiSCent connects App Store work to compatible coding agents. Start without credentials, then move to a supported, authenticated Apple-account workflow when you need actual state and evidence.
1. Explore without an Apple account
Free App Store Check asks you about your release stage and offers guidance. It does not inspect App Store Connect. Interactive sample sends real JSON-RPC requests to AiSCent's public sample endpoint, but every response is synthetic, fixed, read-only data. Neither path proves your app is ready.
2. Connect a supported agent
See client-specific connection guidance for ChatGPT, Codex, Claude Code, Cursor and other MCP-capable clients. The authenticated hosted MCP address is https://aiscentmcp.com/mcp. A 401 response without authentication is intentional OAuth protection, not evidence that the service is broken. Do not paste your Apple API key into a public prompt.
3. Choose an app and verify the state
Ask your connected agent: “List the apps I can access, select my intended version, check readiness and show the exact blockers with their sources. Do not change anything.” Availability depends on the connected edition, approved scopes, credentials and supported tools. A status summary is not a comprehensive screenshot, IAP, privacy or submission verification unless it actually checked each item.
4. Review changes before any write
For workflows that support writing, inspect the proposed scope, exact app/version, locales and assets. Explicitly approve an applicable operation. Retain the provider readback. Never interpret a generated plan, test fixture, or HTTP success alone as a completed Apple submission.
Which AiSCent edition can do what?
- Hosted MCP: authenticated, read-only inspection and planning. Hosted tools do not directly submit, publish, delete or change App Store Connect records.
- Mac App Store edition: App Store Connect release management and existing static screenshot asset management within Apple's Store policy. It cannot run other apps, use simctl or Xcode automation, execute a local MCP helper, or capture another running app.
- Separate developer/direct-download and internal fleet tools: may provide additional capture and local workflows, but must not be confused with capabilities verified in the released Mac App Store edition.
- Free WWDC MCP: independent, read-only Apple SDK, WWDC and policy research, not Apple account state or release submission.
How to interpret readiness
Require the report to name its source, app, version/build, timestamp, completed checks, skipped checks and blockers. Missing permissions or unknown data should show as unverified, not green. Apple alone controls App Review outcomes.
Having trouble?
Review the preparation checklist, specific failure guides, or contact support. Pro purchase, signing and restoration have not yet been independently accepted end to end in production.