Manage Your Apps with Appeeky's MCP

Your App Store Optimization workflow just got a lot smarter. Appeeky's MCP server makes your personal app data available to — tracked apps, competitors, keywords, metadata versions, and reports — directly to AI assistants like Claude, Cursor, and ChatGPT. No dashboard switching, no copy-pasting app IDs, no manual updates. Just ask.

---

What Is MCP and Why Does It Matter for ASO?

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools in real time. Instead of the AI reasoning from static knowledge, it can fetch live data, write changes, and chain multiple operations together in a single conversation.

For ASO, this is a meaningful shift. Today, improving your App Store metadata involves:

1. Opening the dashboard
2. Looking up keyword rankings
3. Cross-referencing competitor metadata
4. Drafting new copy
5. Saving it somewhere
6. Repeating for every locale

With MCP, you describe what you want in plain language. The assistant figures out the steps, calls the right tools, and hands you the result.

---

What You Can Do With My Apps Tools

Appeeky exposes five resource types through MCP, all tied to your appeeky.com account:

All of these cost zero credits. They don't count against your monthly limit — they're tools for managing your own data, not consuming intelligence credits.

---

Getting Started

1. Get Your API Key

Sign in to appeeky.com, go to Settings → API Key, and generate your key. The key must have apps:read and apps:write scopes enabled (unrestricted keys have both by default).

2. Add Appeeky to Your MCP Client

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "appeeky": {
      "url": "https://mcp.appeeky.com/mcp",
      "headers": {
        "Authorization": "Bearer apk_your_key_here"
      }
    }
  }
}

Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "appeeky": {
      "url": "https://mcp.appeeky.com/mcp",
      "headers": {
        "Authorization": "Bearer apk_your_key_here"
      }
    }
  }
}

That's it. Restart your client and the tools are available.

---

Real Workflows

"What apps am I tracking?"

You: List my tracked apps.

Claude: You have 3 apps:
- Voice Tape Record (ID: 6443843426) — Utilities, live on App Store
- Appeeky (ID: 1234567890) — Productivity, live
- My New App (ID: 9876543210) — not yet live

Researching a competitor and adding it in one go

You: Search for the top ASO tool apps and add the #1 result
     as a competitor for Voice Tape Record.

Claude: [calls search_apps] Top result: Sensor Tower (ID: 1547223625)
        [calls add_competitor] Added Sensor Tower as a competitor
        for Voice Tape Record.

Drafting and saving new metadata

You: Write an optimized English title, subtitle, and keyword field
     for Voice Tape Record targeting "voice journal" and "audio diary".
     Save it as a new version called "v2.1 – Journal Focus".

Claude: [calls create_app_version with generated copy]
        Saved version "v2.1 – Journal Focus":
        Title: "Voice Tape – Audio Journal"
        Subtitle: "Record, Transcribe & Reflect"
        Keywords: "voice journal,audio diary,speech to text,recorder,
                   daily log,memo,dictation,note,habit,reflection"

Reviewing your keyword coverage

You: Show me all tracked keywords for Voice Tape Record,
     then add "voice memos app" and "audio notebook" for the US store.

Claude: [calls list_tracked_keywords] Current keywords: aso tool, recorder
        [calls add_tracked_keyword x2] Added:
        - "voice memos app" (us, en)
        - "audio notebook" (us, en)

Pulling a saved report before a release

You: Get my latest ASO audit report for Voice Tape Record
     and summarize the top 3 issues.

Claude: [calls list_reports with appId filter]
        [calls get_report]
        Top issues from your last audit (March 15):
        1. Keyword field is 78/100 chars — 22 characters unused
        2. Title missing primary keyword "voice recorder"
        3. Screenshot 1 has no text overlay — missed messaging opportunity

---

Security Model

Your data is only accessible to you. Every request is authenticated by your API key, and the key is scoped to your account. The MCP server resolves your identity from the key and filters all queries to your user_id — there is no way to read or modify another user's data.

If you want to limit what an AI assistant can do, set specific scopes on your key:

• apps:read — grants read-only access (list, get)
• apps:write — grants write access (add, update, delete)

An unrestricted key has both. You can update scopes anytime from appeeky.com → Settings → API Key.

---

Combining My Apps Tools with Intelligence Tools

The real power comes from combining personal data management with Appeeky's intelligence endpoints in the same conversation. For example:

You: For each of my tracked apps, fetch the top 10 keyword suggestions
     and add any that aren't already in my tracked keyword list.

The assistant can:

1. Call list_my_apps to get your app IDs
2. Call get_keyword_suggestions for each app
3. Call list_tracked_keywords to see what's already tracked
4. Call add_tracked_keyword for each new keyword

A workflow that would take 20 minutes manually runs in seconds.

---

What's Next

The My Apps MCP tools are the foundation for a deeper AI-assisted ASO workflow. Upcoming capabilities include:

• Keyword rank history — ask "how has my rank for 'voice journal' changed this month?"
• Competitor metadata diff — detect when a competitor updates their title or keywords
• Release scheduling — mark a metadata version for release on a specific date
• Localization management — manage metadata versions per locale in one conversation

---

Get Started

1. Sign up or sign in at appeeky.com
2. Go to Settings → API Key and generate your key
3. Add the MCP server config to Cursor or Claude Desktop
4. Ask your first question

The full tool reference is available in the MCP Server docs and the REST endpoints are documented in My Apps.