AppKittie — App Store intelligence for AI agents

Full API documentation: www.appkittie.com/docs

Turn Cursor, Claude Code, or any Agent Skills–compatible assistant into a research partner for the App Store: discovery, ASO, competitors, growth, revenue, and ads—backed by live data from the AppKittie API (2M+ iOS apps, estimates, growth windows, and ad signals).

Install the skills

Today’s coding agents load Agent Skills from disk: each skill is a folder with a SKILL.md (and optional files), placed where your tool looks—commonly .cursor/skills/, .claude/skills/, .agents/skills/, or .codex/skills/. You either copy those folders, subscribe to a remote rule (Cursor), or use a CLI that fetches from GitHub (Claude Code).

Claude Code — official installer; downloads this repo and registers the skills:

npx skills add appkittie/mcp

Install only specific skills:

npx skills add appkittie/mcp --skill keyword-research competitor-analysis

If you already cloned the repo: cp -r mcp/skills/* .claude/skills/

Cursor — Settings (⌘⇧J) → Rules → Add Rule → Remote Rule (GitHub) → https://github.com/appkittie/mcp, or copy skills locally:

Any other agent — clone and point skills/ at the path your client documents:

git clone https://github.com/appkittie/mcp.git
cp -r mcp/skills/* .cursor/skills/   # or .claude/skills/, .agents/skills/, .codex/skills/

Install the MCP server

Skills describe how to reason about App Store work; MCP exposes live tools (search_apps, keyword endpoints, etc.) against AppKittie. Create an API key at appkittie.com/settings/api-keys (it is only shown once when created).

Claude Code — register the hosted server (HTTP transport + bearer auth):

claude mcp add appkittie --transport http https://mcp.appkittie.com --header "Authorization: Bearer YOUR_API_KEY"

Substitute your real key for YOUR_API_KEY.

Cursor and other MCP clients — use the same URL and Authorization: Bearer … header in your app’s MCP configuration. Example JSON: Wire up the MCP server below.

What you get

Skills compose: e.g. competitor-analysis may point you to keyword-research, then metadata-optimization for execution.

Wire up the MCP server

The worker on Cloudflare forwards requests to AppKittie. Claude Code users can register via claude mcp add above; everyone else (e.g. Cursor) typically pastes config like this:

1. Create a key: appkittie.com/settings/api-keys (shown once—copy immediately).
2. Register the server:

{
  "mcpServers": {
    "appkittie": {
      "url": "https://mcp.appkittie.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

MCP tools

MCP prompts

Skill catalog

Intelligence & positioning

Growth, money, ads

Shared context

Example prompts & commands

Natural language (after skills are installed):

• “Surface the highest-earning Health & Fitness apps.”
• “US keyword set for a meditation app—prioritize by opportunity.”
• “Competitive read for app id 1234567890.”
• “Who’s buying Meta ads in productivity lately?”
• “What’s climbing fastest this week?”
• “Rewrite title + subtitle for these keywords, three options each.”
• “Capture my marketing context so follow-ups stay consistent.”
• “Rough revenue band for education—who owns the top?”

Slash-style entry points: /app-discovery, /keyword-research, /metadata-optimization, /competitor-analysis, /growth-analysis, /ad-intelligence, /revenue-analysis.

How an agent typically runs

1. Loads the relevant SKILL.md (templates, guardrails, output shape).
2. Calls AppKittie—via MCP tools or HTTP—e.g. search_apps with category + sortBy: revenue, or batch_keyword_difficulty for a seed list, then get_keyword_difficulty on shortlist items.
3. Synthesizes: tables, takeaways, and next actions instead of raw JSON dumps.

REST API quick reference

Base: https://appkittie.com/api/v1
Auth: Authorization: Bearer \x3Ckey> — same keys as the dashboard.

curl -sS "https://appkittie.com/api/v1/apps?search=fitness&limit=5" \
  -H "Authorization: Bearer YOUR_API_KEY"

Routes & billing

Payload shape

Success bodies use a top-level data. Lists add cursor pagination:

{
  "data": [{ "title": "Calm", "score": 4.8, "downloads": 85000 }],
  "pagination": { "nextCursor": 50, "totalCount": 12450 }
}

Request the next page with cursor=\x3CnextCursor>. null means end of results.

GET /api/v1/apps filters (AND-combined)

Full parameter matrix: tools/REGISTRY.md.

cURL samples

High-revenue fitness slice:

curl -sS "https://appkittie.com/api/v1/apps?search=fitness&categories=Health+%26+Fitness&minRevenue=10000&sortBy=revenue&sortOrder=desc&limit=10" \
  -H "Authorization: Bearer YOUR_API_KEY"

Batch keywords (US storefront):

curl -sS -X POST "https://appkittie.com/api/v1/keywords/difficulty" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["meditation","sleep tracker","mindfulness","breathing exercises","yoga"],"country":"US"}'

Credits & headers

• App list: 1 credit per returned row; if your balance is below limit, the API trims the page.
• App detail: 1 credit per call.
• Keyword (single): 10 credits per call.
• Keyword (batch): 10 credits per keyword that returns data; duplicates removed before charge.

Every response can include X-Credits-Used and X-Credits-Remaining. Balance also appears on the API Keys page.

Rate limits

Per key, 60s sliding window. Useful headers:

429 includes reset timing—back off or wait.

Errors

JSON body includes error; validation issues add details per field.

Fields you can expect

• List rows: Title, icon, developer, category, rating, reviews, download/revenue estimates (e.g. trailing 30d revenue), multi-window growth, release/update timestamps.
• Detail: Everything above plus description, screenshots, versions, IAP catalog, Meta creatives (assets, copy, status, dates), Apple Search Ads by country, creator deals, contact hints, socials, hiring flags, historical series for rank/reviews/revenue/downloads.
• Keywords: Popularity and difficulty (0–100), competing app count, traffic score (0–100), leaderboard snippets (title, icon, reviews, score, rank).

License

MIT