Run your app's growth
from your editor.
The Verqu MCP server plugs your Verqu console into Claude Code — and any MCP client — so you can monitor reviews, revenue, releases and ASO, and act on them, in plain language without leaving the terminal.
Your growth data, one prompt away
Verqu already watches your Play listing — reviews, releases, purchases, store performance — and your apps already ship the verqu-android SDK that feeds it verified events. The MCP server is the control layer on top: an agent you're already talking to can read that data and take action through the same api.verqu.io your app uses.
Your app
The Verqu SDK reports verified purchases and events to api.verqu.io.
Verqu console
Aggregates reviews, releases, revenue and ASO across all your apps.
Verqu MCP
Exposes that surface as tools an agent can call, scoped by your key.
Claude Code
You ask in plain language; the agent queries and acts on your behalf.
Add it once, from anywhere
A hosted endpoint authenticated with a secret vq_… MCP key you generate in the console (Settings → MCP) — separate from the public SDK ingest key, and scoped to the apps you choose. Register it in Claude Code like this:
# one-time: register the Verqu MCP server with Claude Code claude mcp add verqu --transport http https://api.verqu.io/mcp \ --header "Authorization: Bearer vq_…" # then just ask, in any session: > what did my revenue do this week, and are there any angry reviews?
{
"mcpServers": {
"verqu": {
"type": "http",
"url": "https://api.verqu.io/mcp",
"headers": { "Authorization": "Bearer vq_…" }
}
}
}
Note: generate and revoke keys in the console under Settings → MCP. A key can be scoped to a single app or your whole account, so it only ever exposes the apps you allow. Write tools ask for confirmation before they act.
The tool surface
Grouped by what they touch. Read tools answer questions; write tools take action and will require the graduation/confirmation rules Verqu already enforces in the console.
Apps & setup
orient and configureEvery app this key can see, with package name, store status and the latest headline metrics.
Full detail for one app — tracks, integrations, monitored signals and health.
Mint a new app-scoped SDK ingest key for wiring up a new build or rotating an old one.
The recent activity feed across an app — releases, reviews, purchases, alerts — as one timeline.
Reviews
read the room, respondFilter Play reviews by rating, version, language or sentiment — newest, worst, or unanswered first.
One review in full, with device/version context and any reply history.
Post a developer reply to Google Play — draft it with the agent, send on confirm.
What are people complaining about this week? Themes, deltas and standout quotes.
Revenue
verified purchases & earningsEarnings over a range — gross, net, by product and subscription, with period-over-period change.
Individual server-verified purchase, renewal, cancel and refund events from the RTDN + SDK pipeline.
Active subs, churn, trial conversion and refund rate at a glance.
Releases
tracks & rolloutWhat's live on each track — internal, alpha, beta, production — with version and rollout %.
One release in detail: notes, staged rollout, crash/ANR signal since launch.
Move a build up a track or bump its rollout — gated by Verqu's graduation/confirmation rules.
ASO & growth
store performanceImpressions → store-listing visitors → installs, with the conversion funnel and trend.
How store-listing variants stack up on conversion, so you know which copy/art is winning.
Where installs come from and how each channel converts and retains.