appstore-rejections-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | No | Your custom Supabase instance URL | |
| SUPABASE_ANON_KEY | No | Your Supabase anonymous key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_rejectionsA | 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. |
| get_rejection_reasonA | 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_solutionsA | 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. |
| get_guidelineA | 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. |
| list_common_rejectionsA | List the most common App Store rejection reasons, sorted by frequency. Useful for understanding what reviewers look for most. |
| get_casesA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear primary purpose, and the descriptions are specific enough to avoid major selection errors. Some overlap exists because search_rejections also returns solutions, which could make get_solutions seem redundant, and list_common_rejections overlaps slightly with search_rejections.
Tool names consistently follow a verb_noun snake_case pattern using get, search, and list as actions. This is predictable and makes the toolset easy for an agent to navigate.
Six tools is well-scoped for a specialized App Store rejection knowledge base. There are no redundant tools, and the count feels appropriate for the domain's read-only reference purpose.
The toolset covers the full reference workflow: searching rejection reasons, retrieving detailed reasons, accessing solutions, looking up guidelines, listing common rejections, and exploring real cases. No significant dead ends or missing core operations are apparent for a read-only reference server.