Skip to main content

Overview

The Formo MCP Server lets AI assistants, code editors, and custom integrations query your analytics data in natural language, using MCP, an open standard for connecting AI assistants to external data. For example:
  • “How many daily active users did we have last week?”
  • “What are the top acquisition sources this month?”
  • “Show me user retention by cohort”
MCP requires a Scale or Enterprise plan. Upgrade your workspace to get access.

Getting started

Supported clients: OAuth-capable MCP clients such as ChatGPT, Claude Desktop, Cursor, Claude Code, Windsurf, VS Code, or any client that supports HTTP or stdio MCP transports. Formo supports two authentication methods for MCP:
  • OAuth (Recommended) for clients that manage user sign-in. Users sign in to Formo, select a project on the consent page, and choose which permissions to approve.
  • Workspace API Keys for clients that let you configure an Authorization header manually.

OAuth

Connect OAuth-capable MCP clients to Formo.

API Key

Configure local clients, editors, and tools with an API Key.

Example questions

Product analytics
  • “What are my KPIs for the last 7 days?”
  • “Show me daily active users for the past month”
  • “Which lifecycle stage are most of my users in?”
  • “What’s the conversion rate from page view to wallet connection?”
Marketing attribution
  • “What are my top traffic sources?”
  • “Show me conversion by UTM source”
  • “Which countries are my users coming from?”
Wallet intelligence
  • “Look up the profile for this wallet address, including its net worth”
  • “What are my top wallets and chains?”

Available tools

Query API

SQL, exploration, and pre-built analytics endpoints. Permission: query:read.

Profiles API

Wallet enrichment and profile writes.

Alerts

Charts

Contracts

Segments

The delete_* tools permanently remove data. They will not run unless the call passes "confirm": true, so an assistant has to ask you first rather than delete on its own. Grant write permissions only to clients you trust.

Docs

Troubleshooting

  • 403 MCP access requires a Scale or Enterprise plan: MCP is available only on Scale and Enterprise plans.
  • Tools not appearing: Check that the URL ends with a trailing slash: https://api.formo.so/v0/mcp/. Restart or refresh your AI assistant after configuration changes.
  • OAuth issues: See MCP OAuth for OAuth setup, metadata, and troubleshooting.
  • API key issues: See MCP API Key for API key setup and troubleshooting.

Security

  • Project-scoped: each connection is limited to one project, either selected on the OAuth consent page or attached to the API key.
  • Permission-scoped: every tool call requires the matching permission (e.g. query:read to read analytics, alerts:write to change alerts); deletes additionally require "confirm": true.
  • Owner/admin only: only a workspace owner or admin can create a connection.
  • Nothing retained: the MCP server itself stores no data.
  • Manage anytime: review, change, or revoke access under SettingsConnected apps. Disconnects apply immediately; permission changes apply on reconnect. Sessions expire after 1 hour of inactivity.

FAQ

Any OAuth-capable or HTTP/stdio MCP client. See Getting started for the supported client list and setup instructions.
Anything in the Available tools table: KPIs, traffic sources, pages, events, geography, revenue, lifecycle, retention, cohorts, funnels, and wallet enrichment.
Yes, access is scoped to one project and the permissions you grant. See Security for details.
Yes. OAuth is additive. Existing Workspace API Key configurations continue to work with Authorization: Bearer YOUR_API_KEY.