Overview
What is App Store Rejections Mcp?
App Store Rejections Mcp is an MCP (Model Context Protocol) server that gives AI assistants access to a curated database of Apple App Store rejection reasons, solutions, and real-world cases. It contains 48 rejection reasons, 51 solutions, 554 real-world cases, and all 130 Apple Review Guideline subsections.
How to use App Store Rejections Mcp?
Install via one command for Claude Code (claude mcp add --transport stdio appstore-rejections -- npx -y appstore-rejections-mcp) or add to Cursor / Claude Desktop config files with the same npx command. Once connected, the AI assistant can call built-in tools such as search_rejections, get_rejection_reason, get_solutions, get_guideline, list_common_rejections, and get_cases by describing rejection issues or asking for guidance.
Key features of App Store Rejections Mcp
- Semantic search of rejection messages and issues
- Full details for each rejection reason with Apple’s message templates
- Step‑by‑step solutions with code examples and difficulty ratings
- Lookup of any Apple Review Guideline by number
- Top rejection reasons ranked by frequency
- Real‑world cases filtered by reason, app category, or appeal status
Use cases of App Store Rejections Mcp
- Identify why an app was rejected and what the guideline means
- Get step‑by‑step fixes for common rejection reasons
- Review an iOS codebase for potential rejections before submission
- Browse real‑world cases of appeals and their outcomes
FAQ from App Store Rejections Mcp
What does this server do that a simple web search cannot?
It provides a curated, structured database with verified solutions, success rates, and real‑world cases, all accessible directly through your AI assistant via semantic search.
What are the runtime requirements?
Node.js version 18 or higher is required. No additional dependencies are needed for the default setup.
Where is the data stored?
The data is hosted remotely (semantic search uses pgvector embeddings). Optionally, you can point to your own Supabase instance by setting SUPABASE_URL and SUPABASE_ANON_KEY environment variables.
What transport method does the server use?
It uses stdio transport. The server is launched locally via npx -y appstore-rejections-mcp.
Is authentication required?
No API keys or authentication are required for the default configuration. Custom Supabase instances can be configured with environment variables if desired.
