MCP Server - Rybbit | Analytics for AI Assistants | Rybbit
MCP Server
Ask your analytics anything
Rybbit's hosted MCP server connects Claude, Cursor, Codex, and any MCP client to your analytics: query traffic, manage goals and funnels, even run read-only SQL, with the same permissions as your dashboard.
mcp
Dashboards answer the questions someone thought to build. The Rybbit Model Context Protocol server answers the ones you ask: connect an AI assistant and it can explore your traffic, behavior, errors, and performance data through the same API the dashboard uses, in plain language, from wherever you already work.
This isn't a read-only feed. 39 tools span analytics queries, live stats, sessions and raw events, read-only ClickHouse SQL, and management of sites, goals, funnels, user profiles, organization members, and teams. A coding agent can verify that the error you just fixed has stopped occurring in production, or check which pages matter before a refactor.
Access is as controlled as the dashboard itself: connect with OAuth or scoped, revocable API keys, and every tool call is authorized against your role, site access, and rate limits. Rybbit runs no AI model of its own. Your data goes only to the client you configure, on cloud or self-hosted.
What you can do
Works with your AI tools
Claude Code, Claude Desktop, Cursor, Codex, VS Code, opencode: any MCP client that speaks Streamable HTTP connects to the hosted endpoint in minutes.
The full analytics surface
Overview KPIs, time series, breakdowns by any dimension, live visitors, custom events, JavaScript errors, Web Vitals, retention cohorts, journeys, sessions, and raw events.
Read-only SQL
Let your assistant write ClickHouse SQL against a site-scoped events table, with a schema tool, row limits, and execution-time caps. Ad-hoc questions without a BI tool.
Manage as well as read
39 tools mirror the dashboard: create goals, save funnels, configure sites, identify users and update traits, and manage organization members and teams.
OAuth or scoped API keys
Log in with OAuth in supporting clients, or create a revocable API key per integration, optionally scoped to exactly the permissions an agent needs, like analytics read-only.
Dashboard-grade permissions
Every tool call re-runs the same access checks, roles, and rate limits as the dashboard's own API. Destructive tools are flagged so well-behaved clients confirm before running them.
How it works
Add the endpoint
Point your MCP client at https://app.rybbit.io/api/mcp (or your own domain if you self-host). Per-client walkthroughs cover Claude Code, Cursor, Codex, Claude Desktop, VS Code, and opencode.Authenticate
OAuth-capable clients open a browser login and you approve access. Everywhere else, create an API key in your account settings, scoped if you want the agent limited to specific permissions.Start with context
The assistant calls list_sites to discover your organizations, sites, and its role in each: everything the other tools need.Ask in plain language
"Summarize last month's traffic for the docs site and create a goal for signups." The assistant picks the right tools and works with live data, subject to your permissions.
Who uses this
Developers & coding agents
Check whether the error you just fixed still occurs in production, or look up which pages actually matter before a refactor, without leaving the editor.
Founders
Ask Claude Desktop how the launch went instead of building a report. Conversational analytics with zero setup beyond a connector.
Marketing teams
Compare campaigns, break down UTM performance, and draft reports by asking. No query builder, no CSV exports.
Data-curious teams
The read-only SQL tool answers one-off questions that dashboards can't, without standing up a warehouse or BI tool.
Agencies
Give a reporting agent a scoped read-only key per client and automate the weekly summary across every site you manage.
Automation builders
Agents can create goals, save funnels, and manage sites, members, and teams. The write tools mirror what the dashboard can do.