Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.formo.so/llms.txt

Use this file to discover all available pages before exploring further.

Overview

The Formo MCP Server enables AI tools, OAuth-capable clients, editor integrations, and custom workflows to query your analytics data directly. Ask questions about your users, events, and metrics in natural language. The Model Context Protocol (MCP) is an open standard that allows AI assistants to connect to external data sources and tools. With Formo’s MCP server, you can ask:
  • “How many daily active users did we have last week?”
  • “What are the top acquisition sources this month?”
  • “Show me user retention by cohort”
  • “Which pages have the highest bounce rate?”
The Formo MCP server requires a Scale or Enterprise plan. This applies to both OAuth and Workspace API key connections. Free and Growth workspaces cannot connect to MCP and will receive a 403 error (MCP access requires a Scale or Enterprise plan). Upgrade your workspace to enable MCP access.

Getting started

Supported clients: OAuth-capable MCP clients, Claude Desktop, Cursor, Claude Code, Windsurf, VS Code, Codex, and any client that supports HTTP or stdio MCP transports. Formo supports two authentication methods for MCP:
  • OAuth for clients that manage user sign-in. Users sign in to Formo, select a project on the consent page, and approve read-only MCP access.
  • Workspace API keys for clients that let you configure an Authorization header manually.
The MCP server URL is always https://api.formo.so/v0/mcp/. Keep the trailing slash and do not use the API root URL.

OAuth setup

Connect OAuth-capable MCP clients to Formo.

API key setup

Configure local clients, editors, and CLI bridges with a Workspace API Key.

Example queries

Once connected, try these prompts with your AI assistant: Traffic & Events
  • “What are my KPIs for the last 7 days?”
  • “What are my top traffic sources?”
  • “Which pages have the highest engagement?”
  • “Show me traffic by country”
  • “What are the most common events?”
Custom Queries
  • “How many users signed up this week?”
  • “Show me daily active users for the past month”
  • “What’s the conversion rate from page view to wallet connection?”
Web3 Analytics
  • “Look up the profile for this wallet address, including its net worth”
  • “What are my top wallets and chains?”

Available tools

The Formo MCP server exposes a curated set of tools, grouped below. Core
ToolDescription
explore_dataNatural language data exploration with Formo-specific context
execute_queryRun SQL queries against your analytics data
text_to_sqlConvert natural language to SQL
list_endpointsList available API endpoints
list_datasourcesList available data sources
Analytics endpoints
ToolDescription
kpisGet key performance indicators
distinct_valuesGet unique values for filtering
top_eventsView most common events
event_timeseriesEvent counts over time
lifecycleNew, returning, resurrected, and dormant users
retentionUser retention by cohort
frequencyHow often users return
top_pagesAnalyze page performance
top_sourcesAttribution and traffic sources
top_locationsGeographic distribution
top_walletsMost active wallets
top_chainsActivity by blockchain
revenue_overviewRevenue analytics
revenue_timeseriesRevenue over time
revenue_by_metricRevenue broken down by a dimension
volume_by_metricTransaction volume broken down by a dimension
cohort_analysisCohort-based behavioral analysis
funnelMulti-step conversion funnels
flowUser journey and path analysis
search_profileLook up enrichment for a single wallet address (net worth, tokens, labels)
Docs
ToolDescription
search_formo_docsSearch the Formo documentation
query_docs_filesystem_formo_docsQuery the Formo docs filesystem
The exact set of tools depends on your project’s configured endpoints. Use list_endpoints to discover what’s available for your project.
lifecycle, retention, and frequency are first-class MCP tools. For user-level lists or cohort exports, use text_to_sql + execute_query to query the users datasource directly.

FAQ

The Formo MCP Server works with OAuth-capable MCP clients, Claude Desktop, Cursor, Claude Code, Windsurf, VS Code, Codex, and any AI client that supports HTTP or stdio MCP transports. See the OAuth and API key setup pages above for configuration instructions.
You can query KPIs, traffic sources, top pages, top events, geographic distribution, revenue, lifecycle, retention, frequency, cohorts, funnels, and wallet enrichment. Most of these are available as first-class tools (see Available tools).
Yes. The MCP Server provides read-only access scoped to one Formo project. OAuth users select the project during consent, and API keys are project-specific. No data is stored by the MCP server itself.
Yes. OAuth is additive. Existing Workspace API Key configurations continue to work with Authorization: Bearer YOUR_API_KEY.

Troubleshooting

403 MCP access requires a Scale or Enterprise plan: MCP is available only on Scale and Enterprise plans. Upgrade your workspace to connect MCP. 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

The Formo MCP server provides read-only access to analytics data. OAuth access is scoped to the project selected on the Formo consent page. API key access is scoped to the project attached to the key. MCP sessions expire after 1 hour of inactivity.