AppNiche MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPNICHE_API_KEY | Yes | Your AppNiche API key from https://app.getappniche.com/settings/api-keys |
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_appsA | Search and filter iOS App Store apps by keyword, category, rating, reviews, downloads, revenue, and sort order. |
| get_app_detailA | Get one app profile with App Store metadata, ratings, and directional revenue and download estimates. |
| get_keyword_difficultyA | Estimate difficulty and opportunity for one iOS App Store keyword in a country and language. |
| get_app_reviewsA | Fetch enriched App Store review rows with sentiment and topic signals for one iOS app. |
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 4 tools
Each tool targets a distinct purpose: fetching app metadata, reviews, keyword difficulty, and app search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (get_app_detail, get_app_reviews, get_keyword_difficulty, search_apps).
With 4 tools, the server is slightly minimal but remains well-scoped for its niche of iOS App Store data. Each tool adds clear value without unnecessary bloat.
The set covers key app store operations: search, detail, reviews, and keyword analysis. Minor gaps like top charts or developer-level queries exist but don't impede core workflows.