Model Context Protocol
MCP server for App Store intelligence
Streamable HTTP at
https://mcp.appeeky.com/mcp. Same tool surface as REST — from Cursor and Claude Desktop to Codex, Windsurf, and any MCP-compatible client: search, apps, keywords, intelligence, market, ASO, screenshots, Connect, RevenueCat, and My Data.Works with
Cursor
Codex
Cursor vs Claude Desktop
Same JSON shape; only the config file path changes. Paste your Appeeky API key as
Authorization: Bearer.Cursor · .cursor/mcp.json
{
"mcpServers": {
"appeeky": {
"url": "https://mcp.appeeky.com/mcp",
"headers": {
"Authorization": "Bearer apk_your_key_here"
}
}
}
}Claude Desktop · claude_desktop_config.json
{
"mcpServers": {
"appeeky": {
"url": "https://mcp.appeeky.com/mcp",
"headers": {
"Authorization": "Bearer apk_your_key_here"
}
}
}
}macOS: ~/Library/Application Support/Claude/ · Windows: %APPDATA%\Claude\
Tools & transport
Typed tools return structured data — ideal for agents. Credits match REST; failed calls do not consume credits.
- search_apps
- get_app
- get_app_intelligence
- get_keyword_ranks
- market_movers
- connect_apps
Stable tool names
search_apps, get_app_intelligence, keyword and market tools, ASC/RevenueCat when headers are provided, and My Data — same names everywhere.
{
"mcpServers": {
"appeeky": {
"url": "https://mcp.appeeky.com/mcp",
"headers": {
"Authorization": "Bearer apk_…"
}
}
}
}One bearer token
Use the same Appeeky API key as REST. Optional Agent Skills can orchestrate multi-step ASO flows on top of these tools.
Clients & tooling
IDE integrations, MCP SDKs, and optional ASO Agent Skills — one protocol for all of them.
IDEs & assistants
Cursor, Claude Desktop, OpenAI Codex — URL + headers in JSON.
SDKs
TypeScript / Python MCP clients over Streamable HTTP.
Skills
ASO Agent Skills compose playbooks; MCP supplies live data.
Server URL
Add this URL to your MCP client and send your Appeeky API key on every request.
Connection
URL · https://mcp.appeeky.com/mcp
Authorization: Bearer <your-api-key>