MCP Server
Connect ChatGPT, Claude, Grok, Gemini, JetBrains IDEs, Cursor, Antigravity, and other AI tools to your FastStats projects.
The FastStats MCP server lets AI tools that support the Model Context Protocol work with your projects. They can query your analytics, triage errors, read session replays, and build dashboards.
It’s a hosted server, so there’s nothing to install or run. Add this URL to your client:
https://api.faststats.dev/v0/mcp The server uses the Streamable HTTP transport. A client that only supports stdio can connect through a bridge.
Connect your client
Most clients sign in with OAuth, so you only need to add the URL. To connect without a browser, use an API key instead.
Menu names and plan limits in these apps change often. If a step doesn’t match what you see, check the app’s own MCP documentation.
AI assistants
- Open ChatGPT Plugins on the web
- Select the Add button, then Add custom MCP server
- Enter
FastStatsas the name, add a description, and enterhttps://api.faststats.dev/v0/mcpas the public endpoint - Choose OAuth for authentication, review the warning, and select I understand and want to continue
- Select Create as a plugin, then sign in to FastStats
- Install the plugin, then type
@in a chat to use it
What you can do depends on your plan. Pro accounts are limited to tools that read data, while Business, Enterprise, and Edu workspaces get full MCP support. In Business workspaces, only admins and owners can create custom plugins. See OpenAI’s guide for your plan’s current limits.
Coding agents
Add the server:
claude mcp add --transport http faststats https://api.faststats.dev/v0/mcp Then start Claude Code, run /mcp, select faststats, and sign in.
To use the server in every project, add --scope user. To share it with your team through a .mcp.json file, add --scope project.
IDEs
IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs have three places to add a server, depending on which agent you use.
AI Assistant
-
Open Settings > Tools > AI Assistant > Model Context Protocol (MCP)
-
Select Add, choose the HTTP option, and enter:
{ "mcpServers": { "faststats": { "url": "https://api.faststats.dev/v0/mcp" } } } -
Choose a Server level, select OK, then Apply
-
Check the Status column to see whether the server connected
JetBrains doesn’t document OAuth or custom headers for AI Assistant. If the server doesn’t connect, use the bridge instead.
Junie
Open Settings > Tools > Junie > MCP Settings, select Add, and add the same faststats entry to the mcp.json file that opens. This saves it to ~/.junie/mcp/mcp.json. To use it in only one project, put it in .junie/mcp/mcp.json instead.
In Junie CLI, run /mcp, select faststats, and choose Authorize to sign in. The status changes to Active.
Air in your IDE
Open Settings > AI > Air > MCP Servers and select Edit MCPs. JetBrains only documents header authentication here, so add the server with an API key. Then refresh the Your servers list, select faststats, and select OK. The server is available from your next session.
Other clients
Point your client at https://api.faststats.dev/v0/mcp as a remote HTTP server.
If it supports OAuth, it finds the sign-in page and registers itself, so you don’t need a client ID or secret. If it doesn’t, use an API key.
If your client only supports local stdio servers, or can’t sign in, use the third-party mcp-remote bridge. It needs Node.js and opens your browser to sign in:
{
"mcpServers": {
"faststats": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.faststats.dev/v0/mcp"]
}
}
} Sign in and approve access
When you connect with OAuth, your browser opens a FastStats page. Sign in if you need to, then choose what the client can reach:
- Workspaces: your personal projects, one or more organizations, or both. The client only sees the workspaces you pick, and it has your role in each of them.
- Access: Read and write lets the client make changes. Read only lets it see your data but change nothing, and it won’t see any tools that make changes.
Select Approve to finish. The client stays connected, so you won’t need to sign in each time.
To change your choices, disconnect and sign in again from your client. Your new choices need a new approval.
With Read and write access, changes apply as soon as a tool runs. Choose Read only if you only need answers, and only approve clients you trust.
Connect with an API key
API keys suit CI jobs and other setups where nobody can sign in through a browser. The key’s permissions and project access limit what every tool can do.
- Create a key in the API keys tab of your user or organization settings
- Choose its projects and permissions. The Read-only preset is a good start for anything that doesn’t need to make changes
- Send the key as a bearer token with each request
claude mcp add --transport http faststats https://api.faststats.dev/v0/mcp \
--header "Authorization: Bearer $FASTSTATS_API_KEY" Don’t commit API keys. The Claude Code and Antigravity CLI commands save the key in your local configuration, and the JetBrains, Antigravity, and Zed examples store it in plain text, so keep those files out of version control.
Check the connection
Ask your client:
List my FastStats projects.
You should see the projects you gave it access to, each with a link to the app. If you have only one project, you don’t need to name it in later questions.
What you can do
Here are a few things to try:
- “Which pages got the most traffic last week, and where did the visitors come from?”
- “What are the worst new errors since the last release? Find the cause in this codebase.”
- “Find session replays where someone hit the checkout error, and tell me what they did first.”
- “Build a dashboard for our signup funnel.”
- “Write a notebook summarizing how this month went.”
Tools
| Area | Tools can |
|---|---|
| Projects | List, describe, and create projects, and get their setup details |
| Data | Run SQL, read dashboards and insights, render charts, and detect anomalies |
| Library | Create and edit dashboards, charts, funnels, Sankeys, and retentions |
| Errors | Find, inspect, comment on, and update issues, and see trends and errors per release |
| Session replays | Search, read, and collect replays, and read replay insights |
| People | Look up users and their sessions, and manage segments |
| Notebooks | Read, create, and update notebooks |
| Feature flags | List and set flags |
| Event markers | Record deploys and other events so charts and anomaly detection can show them |
Tools check your role or the API key’s permissions. If a project doesn’t track something, or you don’t have access to it, those tools report that it isn’t available.
Prompts
The server also offers ready-made workflows. Clients that support prompts usually show them as commands. In Claude Code, they look like /mcp__faststats__triage_errors.
| Prompt | What it does |
|---|---|
setup_tracking | Connects this codebase to FastStats: creates or picks a project and installs the SDK |
triage_errors | Sorts new and regressed errors by impact and finds their causes in this codebase |
fix_error | Investigates one error issue, finds the root cause, and fixes it |
record_deploy | Adds a deploy marker for what you just shipped |
weekly_report | Writes a notebook summarizing a period, with live charts |
investigate_anomaly | Finds out why a metric moved: what changed, when, and for which users |
build_dashboard | Designs a dashboard for a goal, checks it with a dry run, then creates it |
Resources
Clients that support resources can attach project context to a conversation, using URIs like faststats://<project>/overview. In Claude Code, @-mention them. They include the project overview, SQL tables, topic guides, notebooks, dashboard data, and error issues.
Troubleshooting
The client says it needs authentication or returns 401
Finish signing in from your client, such as /mcp in Claude Code. If you use an API key, check that it hasn’t expired or been revoked, and that you send it as Authorization: Bearer <key>.
The client can’t finish signing in
Connect with an API key or the mcp-remote bridge instead.
A tool needs the mcp:write scope
You approved Read only access. Disconnect, sign in again from your client, and choose Read and write.
A project is missing
The connection doesn’t include that project’s workspace, or the API key doesn’t include that project. Sign in again and pick the workspace, or update the key’s projects.
A tool says something isn’t available
Your role or the API key doesn’t have the permission it needs, or the project doesn’t track that data.
A result was cut off
Results are limited to 100,000 characters. Ask for less, such as fewer columns, a shorter period, or a specific item.