Skip to main content
The Kubit MCP server connects an AI assistant to your Kubit workspace over the Model Context Protocol. With it connected, you ask Claude, Cursor, Codex or another MCP client a question in plain language, and the assistant builds the Kubit report, runs it and returns the results with a link to the report in Kubit. The server works with Agent Observability and Product Analytics data. It reads the same workspaces, reports and permissions you have in the Kubit app.

Server URL

The Kubit MCP server URL is https://agent.kubit.ai/mcp. It uses the streamable HTTP transport, so it runs in Kubit’s cloud and needs nothing installed on your machine. Connect your AI assistant has the setup for each client.

What the MCP server can do

The Kubit MCP server exposes 11 tools. Your assistant picks the tool, so you rarely name one. MCP tools reference lists every tool with its inputs and limits.

What the MCP server can’t do

The Kubit MCP server builds Query, Funnel, Path, Retention, Inspection and Agent flow reports. Build these in the Kubit app instead:

Sign-in and permissions

The Kubit MCP server signs you in with OAuth in your browser, using your Kubit account. The assistant sees the same organizations, workspaces and data you see in the Kubit app, with the same permissions. Sign-in doesn’t ask for an organization. After you sign in, the assistant starts in your last-used workspace. To change it, ask the assistant to switch workspaces, or run /kubit-connect if you use the Kubit plugin for Claude Code or Cursor.

Connect your AI assistant

Setup for Claude Code, Cursor, Claude, Codex and other MCP clients.

MCP tools reference

Every tool, its inputs and its limits.

Prompt Kubit

How to phrase questions so the MCP server builds the right report.

Kubit skills

Slash commands for reports, traces and regressions in Claude Code and Cursor.