Storewake exposes your workspace data through a hosted MCP endpoint. A compatible agent can investigate rankings, compare competitors and suggest what to test next.
Connect your workspace
- Create a Storewake workspace, add your app and select its country. Public App Store tracking does not require Apple credentials.
- 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.
- 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.
- Ask the agent to run
list_apps, thenstatus. 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.
19 tools, one workspace
Apps and workspace
Find your tracked apps, add an app, inspect its overview and check integration availability.
list_apps, add_app, app_overview, status
Keyword research and tracking
Read ranking history by storefront, research terms and request new snapshots within your plan limits.
tracked_keywords, add_keywords, refresh_keywords, keyword_popularity, analyze_keywords, suggest_keywords, search_apps
Competitors
Review tracked competitors, add a competitor and inspect keyword overlap.
competitors, add_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. 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.