MCP Server

The CodSpeed MCP server gives AI-powered tools direct access to your performance data — benchmark runs, comparisons, and flamegraphs — so you can investigate regressions, explore profiling results, and review performance changes without leaving your editor or chat interface. The server follows the Model Context Protocol (MCP) specification and is hosted by CodSpeed at

https://mcp.codspeed.io/mcp

Getting started

Add the CodSpeed marketplace and install the plugin:

/plugin marketplace add CodSpeedHQ/codspeed
/plugin install codspeed

The plugin installs both the MCP server and agent skills automatically.

Alternatively, you can add the MCP server directly:

claude mcp add --transport http CodSpeed https://mcp.codspeed.io/mcp

Add the following to your .cursor/mcp.json file:

.cursor/mcp.json

{
  "mcpServers": {
    "CodSpeed": {
      "url": "https://mcp.codspeed.io/mcp"
    }
  }
}

Cursor will prompt you to authenticate with CodSpeed via OAuth on first use.

Add the following to your ~/.codeium/windsurf/mcp_config.json file:

mcp_config.json

{
  "mcpServers": {
    "CodSpeed": {
      "serverUrl": "https://mcp.codspeed.io/mcp"
    }
  }
}

Add the CodSpeed MCP server and authenticate:

codex mcp add CodSpeed --url https://mcp.codspeed.io/mcp
codex mcp login CodSpeed

Add the following to your .vscode/mcp.json file:

.vscode/mcp.json

{
  "servers": {
    "CodSpeed": {
      "type": "http",
      "url": "https://mcp.codspeed.io/mcp"
    }
  }
}

Open Settings → MCP.
Click Add MCP Server.
Enter the following:
- Name: CodSpeed
- URL: https://mcp.codspeed.io/mcp
Save and authenticate with CodSpeed when prompted.

Alternative: auto-detect with `add-mcp`

If your tool supports it, you can use add-mcp to automatically detect installed agents and configure them:

npx add-mcp https://mcp.codspeed.io/mcp --name CodSpeed

Example prompts

Once connected, you can ask your AI assistant questions like:

“Explain the regression on the feat/my-great-feature branch.”
“Make my foo_bar function faster.”
“What are the hottest functions in the bench_foo benchmark?”
“Analyze the flamegraph for bench_parse and refactor the hot path.”
“Compare the flamegraphs of bench_serialize between main and feat/new-encoder and explain what changed.”
“Find the bottleneck in bench_api_handler and open a PR to fix it.”

Because the MCP server runs inside coding agents, your assistant can cross-reference flamegraph hot spots with your actual source code — then suggest or apply optimizations directly.

Available tools

The CodSpeed MCP server exposes five tools:

Tool	Description
`list_repositories`	List all CodSpeed-enabled repositories that you have access to. Returns repository names, visibility, and descriptions.
`list_runs`	List recent performance runs for a repository. Returns run IDs, commit hashes, status, event type, branch, and PR information.
`get_run`	Inspect a single performance run and its benchmark results. Shows benchmark names, identifiers, and values. Accepts a run ID, branch, or defaults to the latest run.
`compare_runs`	Compare two performance runs and return a markdown performance report. Shows benchmark-level comparisons including improvements, regressions, and new or missing benchmarks.
`query_flamegraph`	Query and summarize a flame graph from a performance run. Returns hot spots (functions with highest self time), the call tree, and timing information for each function.

Authentication

The CodSpeed MCP server uses OAuth for authentication. When you first connect, your MCP client will open a browser window where you log in to CodSpeed and authorize access. The client stores the resulting token and refreshes it automatically — no API keys to manage.

The MCP server has access to the same repositories and data as your CodSpeed account.

Get Started

For Agents

Instruments

Integrations

Explore Features

Getting started

Alternative: auto-detect with `add-mcp`

Example prompts

Available tools

Authentication

Get Started

For Agents

Instruments

Integrations

Explore Features

Documentation Index

​Getting started

​Alternative: auto-detect with add-mcp

​Example prompts

​Available tools

​Authentication

Getting started

Alternative: auto-detect with `add-mcp`

Example prompts

Available tools

Authentication