# hotpath-cloud MCP server

> Read Rust profiling reports from CI: benchmark history, diffs against the baseline and performance policies.

- Listing: https://mcp.tc/i/hotpath-cloud
- Connect: use the server's own URL `https://hotpath.rs/api/v1/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: hotpath-rs
- Homepage: <https://hotpath.rs/mcp_api>
- Repository: <https://github.com/hotpath-rs/hotpath>

## About

Connects to hotpath-cloud, which stores Rust profiling reports uploaded from CI. You can list repositories and benchmarks, browse report history, fetch single reports, and compare a report with its baseline to see regressions, improvements and broken budgets. It also serves the default policy document and validates edited policy TOML files.

The server is hosted at https://hotpath.rs/api/v1/mcp over streamable HTTP and every tool is read-only. Clients that support Client ID Metadata Documents sign in with OAuth; other clients send a personal API token from hotpath.rs/app/tokens as a Bearer header. Dynamic client registration is not supported.

## What it can do

- List repositories with the hotpath GitHub App installed
- List benchmarks of a repository
- Browse report history, newest first
- Fetch a report with its verdict, policy and optional payload
- Compare a report with its baseline for regressions and improvements
- Get the default policy and validate edited policy files
- Check which GitHub user the connection acts as

## Tools (8)

- `get_default_policy`: Get the default policy document to save as hotpath/policy.toml and edit. (read-only)
- `get_diff`: Compare a report with its baseline: regressions, improvements and broken budgets. (read-only)
- `get_report`: Fetch one report with its summary, verdict and policy, optionally the JSON payload. (read-only)
- `list_benchmarks`: List one repository's benchmarks. (read-only)
- `list_reports`: List a repository's reports, newest first, with run totals. (read-only)
- `list_repos`: List repositories with the hotpath GitHub App installed, with their benchmarks. (read-only)
- `validate_policy`: Check a policy TOML document before committing it. (read-only)
- `whoami`: Show the GitHub user and API token this connection acts as. (read-only)

## Example prompts

- "List my repositories that use hotpath and their benchmarks."
- "Compare the latest report on PR 123 of owner/name with its baseline."
- "Show the last 10 reports for the main benchmark in owner/name."
- "Validate this hotpath policy.toml before I commit it."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http hotpath-cloud https://hotpath.rs/api/v1/mcp
```

2. Start Claude Code, type `/mcp`, pick **hotpath-cloud** and choose **Authenticate**. A browser window opens for the hotpath-rs sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **hotpath-cloud** and paste this URL:

```url
https://hotpath.rs/api/v1/mcp
```

3. Click **Add**, then **Connect**, and sign in when hotpath-rs asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=hotpath-cloud&connectorUrl=https%3A%2F%2Fhotpath.rs%2Fapi%2Fv1%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://hotpath.rs/api/v1/mcp` and click **Add**.

3. Click **Connect** and sign in when hotpath-rs asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://hotpath.rs/api/v1/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to hotpath-rs to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=hotpath-cloud&config=eyJ1cmwiOiJodHRwczovL2hvdHBhdGgucnMvYXBpL3YxL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "hotpath-cloud": {
      "url": "https://hotpath.rs/api/v1/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=hotpath-cloud&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fhotpath.rs%2Fapi%2Fv1%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"hotpath-cloud","type":"http","url":"https://hotpath.rs/api/v1/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "hotpath-cloud": {
      "type": "http",
      "url": "https://hotpath.rs/api/v1/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "hotpath-cloud": {
      "serverUrl": "https://hotpath.rs/api/v1/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add hotpath-cloud --url https://hotpath.rs/api/v1/mcp
codex mcp login hotpath-cloud
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.hotpath-cloud]
url = "https://hotpath.rs/api/v1/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http hotpath-cloud https://hotpath.rs/api/v1/mcp
```

Then, inside Gemini CLI, run `/mcp auth hotpath-cloud` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "hotpath-cloud": {
      "type": "http",
      "url": "https://hotpath.rs/api/v1/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://hotpath.rs/api/v1/mcp`.

## Recent changes

- 2026-11-09 02:51 UTC: 3 tools changed. Source: automatic check. Changed: get\_diff, get\_report, list\_reports.
- 2026-11-08 20:29 UTC: Tracking started: 8 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/hotpath-cloud#history (Atom feed: https://mcp.tc/i/hotpath-cloud/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.3
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-08
- Updated: 2026-11-08

---
Source: https://mcp.tc/i/hotpath-cloud (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
