get_cases
Get real-world App Store rejection cases from developers who experienced them. Filter by rejection reason, app category, or appeal status. Cases include the developer's message, Apple's response, and resolution.
LABSCO SUMMARY
It turns a rejection notice into a guideline reference and a set of fixes that have already shipped.
The chain runs from search_rejections to get_rejection_reason for Apple's own message template and the guideline it points at, then to get_solutions for fixes that arrive with a difficulty level and a success rate. get_cases supplies the other half of the picture: what the developer wrote, what Apple wrote back, and whether the appeal held. get_guideline works in the opposite direction, from a section number such as '5.1.1' back to the reasons that cite it.
What it is
A lookup service over App Store rejection reasons, the App Store Review Guidelines they cite, and cases reported by developers who hit them.
What you get
- Natural-language matching from a pasted rejection message to ranked rejection reasons through search_rejections.
- The full record for a reason through get_rejection_reason: Apple's message template, affected categories, guideline reference and tags.
- Step-by-step fixes from get_solutions, carrying implementation details, code examples, difficulty level and success rates.
- Guideline lookup by section or subsection number through get_guideline — '2.1', '4.3', '5.1.1' — returning the text and the rejection reasons related to it.
- Frequency-ranked rejection reasons from list_common_rejections, ordered by how often reviewers raise them.
- Developer-reported cases through get_cases, filterable by rejection reason, app category or appeal status, each with the developer's message, Apple's response and the resolution.
Requirements
No account and no key. The rejection message from Apple is worth having on hand, since search_rejections matches against its text.
Setup effort
One command — npx -y appstore-rejections-mcp
USE CASES
01
Decoding the rejection notice that just landed
Apple's wording goes in as it arrived and comes back matched to ranked reasons, and the full record then supplies the guideline reference and affected categories behind it.
02
Choosing the fix that has worked for other people
Fixes arrive with implementation details, code examples, a difficulty level and a success rate, which is what lets a resubmission be spent on the option most likely to clear.
03
Reading the guideline Apple actually cited
A section number goes in and the guideline text comes back with the rejection reasons attached to it, which shows what else that clause is used to reject.
04
Deciding whether an appeal is worth the wait
Cases can be filtered by appeal status, so the question becomes what happened to developers who argued the same point rather than a guess about how it will go.
05
Reviewing a build against what reviewers flag most
The frequency-ranked list is a pre-submission checklist drawn from what actually gets rejected, rather than from the order the guidelines happen to be written in.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_guideline
Look up a specific Apple App Store Review Guideline by section or subsection number. Examples: '2.1', '4.3', '5.1.1'. Returns the guideline text and any related rejection reasons.
get_rejection_reason
Get full details about a specific App Store rejection reason including Apple's message template, affected categories, guideline reference, and tags. Use search_rejections first to find the ID.
get_solutions
Get all solutions for a specific App Store rejection reason. Returns step-by-step fixes with implementation details, code examples, difficulty level, and success rates.
list_common_rejections
List the most common App Store rejection reasons, sorted by frequency. Useful for understanding what reviewers look for most.
search_rejections
Search for App Store rejection reasons using natural language. Paste Apple's rejection message or describe the issue. Returns matching rejection reasons ranked by relevance with solutions.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. All six read a maintainer-hosted database of 48 rejection reasons, 51 solutions and 554 cases; none touch Apple or your app.
Requires
- npx on PATH
- Node.js >= 18
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y appstore-rejections-mcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport stdio appstore-rejections -- npx -y appstore-rejections-mcpCursor, Claude Desktop
JSON
{
"mcpServers": {
"appstore-rejections": {
"command": "npx",
"args": [
"-y",
"appstore-rejections-mcp"
]
}
}
}
