Storewake

npx add-mcp 'https://api.storewake.com/mcp'

Your AI agent helped you build your iOS app. Give it the context to help you grow it.

Storewake exposes your workspace data through a hosted MCP endpoint. A compatible agent can investigate rankings, compare competitors and suggest what to test next.

One paid-to-organic investigation, with the evidence

Real MCP workflow · Respira

Connect Apple Ads queries, organic rankings and subscription context in one investigation.

This edited replay uses the founder's own iOS app. The assistant reads actual Apple Ads search terms, compares them with Storewake's observed organic positions and adds RevenueCat customer aggregates without changing a campaign or listing.

• Country and reporting dates stay visible.
• Missing rank remains missing, never rank zero.
• Apple Ads tools are read-only.

Up to three apps per workspace. Use LAUNCH at checkout for 20% off while you keep the subscription.

Your browser does not support embedded video.

50 seconds · Real aggregated data · Edited MCP replay

The Apple Ads search-term window and the RevenueCat customer window are separate sources. Storewake keeps those boundaries visible instead of assigning a subscription to a query it cannot prove produced it.

Connect your workspace

1. Create a Storewake workspace, add your app and select its country. Public App Store tracking does not require Apple credentials.
2. Use a workspace on Grow for MCP access. In Settings → API & MCP, create a credential with Connect an AI assistant selected. Owner or admin access is required.
3. In a client that supports remote Streamable HTTP MCP with a custom authorization header, add the endpoint below and supply your MCP token as a Bearer token.
4. Ask the agent to run list_apps, then status. Select the returned app ID and the storefront you want to investigate.

Endpoint: https://api.storewake.com/mcp
Transport: Streamable HTTP
Authorization: Bearer <YOUR_STOREWAKE_MCP_TOKEN>

Save the token in your client’s credential configuration. An ordinary Storewake API key cannot authenticate to the MCP endpoint. Client interfaces vary; a connector that only supports OAuth or cannot send custom headers is not compatible with this token setup.

Add the context you need

Connect App Store Connect for available store metadata, Apple Ads for supported popularity and campaign data, and RevenueCat for subscription and revenue snapshots. These are separate, optional connections managed in Settings → Integrations. Missing connections mean the corresponding data is unavailable.

22 tools, one workspace

Apps and workspace

Find your tracked apps, add an app, inspect its overview, stop tracking a storefront and check integration availability.

list_apps, add_app, app_overview, remove_storefront, status

Keyword research and tracking

Read ranking history by storefront, research terms, add or remove tracked keywords and request new snapshots within your plan limits.

tracked_keywords, add_keywords, remove_keywords, refresh_keywords, keyword_popularity, analyze_keywords, suggest_keywords, search_apps

Competitors

Review tracked competitors, add or remove a competitor and inspect keyword overlap.

competitors, add_competitor, remove_competitor, competitor_keywords

Connected business context

Read available App Store Connect metadata, RevenueCat snapshots and Apple Ads campaign data with the relevant connections.

asc_metadata, revenue, new_customers, campaign_performance, search_terms

Start with a question you can verify

Find my app with list_apps. For its US storefront, read the
tracked keyword history and compare the latest two snapshots.
Show the dates, previous rank and current rank for each mover.
Separate missing ranks from measured drops. Suggest one next
investigation, and tell me what evidence is still missing.
Do not add keywords or request refreshes without asking me.

A useful answer names its source, app, country and observation dates. Follow up with competitor research or connected revenue context only when it helps answer the question.

What your agent can change

The tools include actions that add apps, keywords and competitors or request fresh data, and actions that remove keywords, competitors or a whole storefront. Removal deletes the stored rank history and cannot be undone, so these tools are marked destructive for your client to confirm; removing a storefront also requires an explicit confirmation argument. Research and refreshes consume workspace allowances. Reading existing history first avoids unnecessary collection.

The current catalogue does not publish App Store listing edits or change Apple Ads bids. Your agent can propose experiments; you review and carry out those changes in the relevant service. A suggested explanation is a hypothesis until supported by evidence.

If the connection does not work

• Authentication fails: check the endpoint, Bearer header and that the credential is an MCP token for the intended workspace. Replace expired or revoked credentials.
• Access or quota error: check the workspace’s Grow status and usage in Settings. Repeating the same call does not resolve a plan limit.
• Integration data is unavailable: check the relevant provider connection before interpreting an empty response.
• No historical comparison: a newly tracked keyword needs multiple snapshots. One observation cannot establish a trend.