Appstore Rejections MCP Server

Appstore Rejections MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Appstore Rejections MCP directly instead of describing what you should do. MCP server for App Store rejection reasons, solutions, and real-world cases.

What you get

Built on a database of 48 rejection reasons, 51 solutions, 554 real-world cases, and all 130 Apple Review Guideline subsections.

Setting it up

Installation goes through your MCP client rather than a global install: point it at appstore-rejections-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Appstore Rejections MCP is connected, these are the calls the assistant has available:

• search_rejections — Semantic search — paste Apple's rejection message or describe the issue
• get_rejection_reason — Full details for a specific rejection reason (Apple's message, tags, categories)
• get_solutions — Step-by-step fixes with code examples, difficulty, and success rates
• get_guideline — Look up Apple Review Guidelines by number (e.g. 2.1, 4.3, 5.1.1)
• list_common_rejections — Top rejection reasons ranked by frequency
• get_cases — Real-world cases filtered by reason, app category, or appeal status
• Cursor — Add to your Cursor config file: - macOS/Linux: ~/.cursor/mcp.json - Windows: %APPDATA%\Cursor\mcp.json

Configuration and credentials

You will need 2 environment variables: SUPABASE_URL, SUPABASE_ANON_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 18

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the appstore rejections mcp mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Appstore Rejections MCP's toolset — search_rejections, get_rejection_reason, get_solutions and 4 more — is a fair guide to whether it matches your workflow. It is maintained by robertojoseph; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.