MCP

Beta. MCP access is opt-in per user right now. If a project’s MCP key won’t generate, or the OAuth connect flow says “not enabled for your organization,” ask an Appstack admin to turn it on for your user.

Appstack’s MCP server lets Claude (or any MCP-compatible client) query your app’s attribution and analytics data directly, including installs, ad spend, revenue, and campaign performance, across every project and organization you have access to.

Prerequisites

An Appstack account, with MCP access enabled for your user (beta, so ask an admin).
At least one project in Appstack (bundles up to one iOS + one Android app) whose data you want to query.

Connect via OAuth (Claude Desktop, Claude.ai, ChatGPT desktop)

This is the self-serve, recommended path, with no key to copy or store. Claude Desktop / Claude.ai:

Go to Settings → Connectors → Add custom connector.
Paste the server URL: https://mcp.appstack.tech/mcp
Log in with your Appstack account when prompted, and approve access.

ChatGPT desktop:

Go to Settings → Plugins → Add → Add a MCP server.
Name it, set the type to Streamable HTTP, and paste the server URL: https://mcp.appstack.tech/mcp
Save, then click Authenticate and log in with your Appstack account.

Both discover everything else automatically (client registration, PKCE, token issuance), so there is nothing to configure manually. Access always reflects your current projects and organizations. If you join a new one later, it’s covered automatically, with no need to reconnect.

Connect via API key (Claude Code, scripts)

Generate a key from any project’s settings page in the Appstack dashboard (Project → Settings → MCP). The key isn’t limited to that one project. It works across every project and organization you currently have access to.

claude mcp add --transport http appstack-analytics \
  https://mcp.appstack.tech/mcp \
  --header "Authorization: Bearer <YOUR_MCP_KEY>"

Or in Claude Desktop’s config file:

{
  "mcpServers": {
    "appstack-analytics": {
      "url": "https://mcp.appstack.tech/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_KEY>"
      }
    }
  }
}

Regenerate the key any time from the same settings page. This immediately invalidates the old one.

Get better results with a skill

Claude can use these tools with no extra setup, but it has to guess the right call order and exact metric/dimension names on its own. Installing the appstack-mcp skill teaches it those conventions up front, so you get fewer wasted calls and no made-up measure names.

claude plugin marketplace add appstack-tech/appstack-skills
claude plugin install appstack@appstack-plugins

See the appstack-skills README for Codex and Cursor install instructions.

Available tools

Tool	What it does
`whoami`	Identify which app(s) the connection has access to, each with its own organization. Call this first.
`find_organization`	Search organizations by (partial) name, with each match’s apps. Most useful if your access spans multiple organizations (Appstack staff, or anyone on more than one team), since otherwise there’s no other way to look one up by name.
`list_metrics`	List the metrics and dimensions available to query.
`list_dimension_values`	List valid values for a dimension (countries, media sources, app names, and so on) before filtering on it.
`query_metrics`	Run a scoped query with measures, dimensions, filters, and a date range, and get real numbers back. All measures and dimensions in one query must come from the same view, and the date range is capped at 60 days.
`report_data_anomaly`	Report a data inconsistency spotted in a `query_metrics` result, such as a negative value, an implausible swing, or mismatched totals. It records the query and the anomalous rows so the Appstack team can reproduce and triage it, and notifies the team on Slack. It does not fix or explain the anomaly.
`list_integrations`	Every integration (ad network, MMP, subscription platform, and so on) connected to your apps/projects, with its current status.
`get_onboarding_checklist`	Completion of the five onboarding steps for a project.
`list_dashboards` / `get_dashboard`	Saved dashboards and their widgets’ configured measures/dimensions/filters.
`list_user_journeys` / `get_user_journey_filters` / `get_user_journey`	Per-user event timelines, the “Appstack ID history” for a specific user.
`create_link` / `list_links` / `get_link` / `update_link` / `delete_link`	Write. Create, read, update, and delete standard links. Ad-network links aren’t supported here, so manage those from the dashboard. These are the only tools that change your data. `report_data_anomaly` only files a report for the Appstack team, and everything else only reads.

Ask things like:

“What was our ROAS by media source last month?”
“Show me installs and revenue by country for the last 30 days.”
“What are the possible values for media_source?”
“Is our RevenueCat integration connected and active?”
“Create a standard link for this app with campaign name ‘summer-promo’.”

Troubleshooting

“MCP isn’t enabled for your organization yet.” MCP is in beta, opt-in per user. Ask an Appstack admin to turn it on for your user. A project I have access to isn’t showing up. Only projects you’re a member of are covered, and only if MCP access is enabled for your user. If you were just added to a project or organization, the next tool call already reflects it, so there’s no need to reconnect. A tool call returns an error instead of data. Call whoami first to confirm which app(s) are actually in scope for your connection, and list_metrics / list_dimension_values before guessing measure or dimension names. A made-up name fails rather than silently returning nothing.

Limits & notes

Requests are rate-limited per credential (120 req/60s by default). A 429 response includes a Retry-After header.
query_metrics date ranges are capped at 60 days inclusive. A wider range is rejected instead of being trimmed, so split longer periods into several queries.
A single query_metrics call can only use measures, dimensions, and filters from one view. Mixing views is rejected.
OAuth access tokens are short-lived (~1 hour) and refresh automatically, so never copy-paste one.
Your key or connection exposes every project and organization you currently have access to, kept up to date automatically as that access changes.
Regenerating your key immediately breaks any client still using the old one.
create_link/update_link/delete_link actually change data, so review what Claude is about to do before confirming, same as you would for any tool with write access.

Getting started

Mobile SDKs

Integrations

Products

Developer tools

Prerequisites

Connect via OAuth (Claude Desktop, Claude.ai, ChatGPT desktop)

Connect via API key (Claude Code, scripts)

Get better results with a skill

Available tools

Troubleshooting

Limits & notes

​Prerequisites

​Connect via OAuth (Claude Desktop, Claude.ai, ChatGPT desktop)

​Connect via API key (Claude Code, scripts)

​Get better results with a skill

​Available tools

​Troubleshooting

​Limits & notes

Prerequisites

Connect via OAuth (Claude Desktop, Claude.ai, ChatGPT desktop)

Connect via API key (Claude Code, scripts)

Get better results with a skill

Available tools

Troubleshooting

Limits & notes