# hotpath-cloud — MCP server card for AI agents

Read-only access to Rust profiling reports from CI: benchmark history, diffs and policies

Registry name: `rs.hotpath/hotpath-cloud` · category: Other · version 1.0.3 · updated 2026-11-08

## Connect
- Remote (Claude Code): `claude mcp add --transport http hotpath-cloud https://hotpath.rs/api/v1/mcp`

## Facts
- Repository: https://github.com/hotpath-rs/hotpath (1,928 stars)
- Website: https://hotpath.rs/mcp_api

Before you connect a server: read its repository, and give it only the permissions and keys it needs.

## Links
- AgentGid page: https://agentgid.com/mcp/servers/rs-hotpath-hotpath-cloud/


## hotpath-cloud: ask your assistant why Rust code got slower

hotpath-cloud keeps the speed and memory reports that your Rust project's automatic checks upload for every pull request. Its connector lets an AI assistant read those reports, compare a change with the main branch and say what got slower or broke a limit. It only reads; it cannot change or delete anything.

### Where to use it
- Find what slowed down a pull request: Ask what caused the slowdown in pull request 742, and the assistant reads the stored comparison instead of rerunning anything.
- Check which limits a change broke: Your team sets limits such as no memory use on a hot code path; the assistant lists which ones the latest report broke and by how much.
- Follow one benchmark over time: Compare the last five runs on the main branch to see whether memory use keeps creeping up.
- Write a stricter regression rule: Have the assistant draft a rule that flags a 10 percent rise in allocations, then check that the file is valid before you commit it.
- Connect from Codex with a token: On a machine without a browser, or in Cursor, connect with a personal token kept in an environment variable.

### How to start
- Set up the hotpath GitHub integration first, so your pull requests upload reports.
- Add the server to your assistant (Claude Code shown).

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

- Approve the connection on the hotpath.rs page that opens; it can only read.

### License
The hotpath profiler is open source under the MIT license. The hosted service is free during its open beta; public repositories will stay free, paid plans for private ones come later.

### Good to know
- It only shows reports your automatic checks already uploaded; a project without the hotpath setup has nothing to read.
- Every tool call needs a sign-in, even for public reports. Cursor has to use a personal token instead of the browser sign-in.
- Reports of public repositories are public by default, so anyone signed in can read them by naming the repository.
- It needs hotpath 0.30.0 or newer in your Rust project.

Checked 2026-11-10 against: https://github.com/hotpath-rs/hotpath/blob/b8e463528f1d14bcdbb250bcbb536e6b6bb8ec13/README.md, https://github.com/hotpath-rs/hotpath/blob/b8e463528f1d14bcdbb250bcbb536e6b6bb8ec13/server.json, https://github.com/hotpath-rs/hotpath/blob/b8e463528f1d14bcdbb250bcbb536e6b6bb8ec13/LICENSE.txt, https://github.com/hotpath-rs/hotpath/blob/b8e463528f1d14bcdbb250bcbb536e6b6bb8ec13/docs/src/mcp_api.md, https://github.com/hotpath-rs/hotpath/blob/b8e463528f1d14bcdbb250bcbb536e6b6bb8ec13/docs/src/cloud_faq.md, https://hotpath.rs/mcp_api, https://hotpath.rs/cloud, https://hotpath.rs/cloud_faq, https://hotpath.rs/terms

### Mistakes to avoid
- Don't: Adding hotpath-cloud to Cursor and waiting for a browser sign-in → Do: Create a personal token at hotpath.rs/app/tokens and send it as Bearer ${env:HOTPATH_API_TOKEN} (hotpath.rs does not offer the sign-in method Cursor uses.)
- Don't: Writing the token itself into ~/.claude.json or a committed .mcp.json → Do: Use claude mcp add-json with "Bearer ${HOTPATH_API_TOKEN}" in single quotes, so only the variable name is stored (The variable is expanded when Claude Code connects, and the token stays out of files.)
- Don't: Expecting list_repos to show another project's public reports → Do: Pass that project's owner/name to list_reports or get_diff directly (list_repos lists only your own GitHub App installations.)
- Don't: Using an MCP sign-in token with the REST endpoints in a script → Do: Use a personal API token for the REST API (OAuth tokens issued to MCP clients do not work there.)

### Questions
- Can the assistant change anything through it? No. Every tool is read-only and there is no write scope; reports arrive only from your automatic checks.
- Does it see my code? No. The hotpath GitHub App has no access to your code; the service only receives the reports your workflow uploads.
- Is it the same as the hotpath profiler's own server? No. That one runs inside your Rust program and answers about the live process; this one is hosted and reads stored reports.
- How do I cut off an assistant later? Revoke it on hotpath.rs/app/tokens; its tokens are deleted at once.

---
AgentGid's catalog is curated: every entry was checked against the maker's official pages (registry, repository, license and pricing pages) on the date shown; a license value shows the quote it stands on wherever AgentGid has one. Usage numbers come from AgentGid's own scan of public repositories set up for AI coding agents. Claims by makers are reported, not tested by AgentGid.
