caido-mcp-server
70 tools for the Caido proxy: request history, replay, fuzzing and findings for an agent during authorized security testing.
- 138 ★ on the repository
- Last commit
Broad access
Why this level
- The agent sends real HTTP requests and runs fuzzing against targets, and calling it on someone else's system without permission is illegal.
- Some tools delete projects, scopes and findings in Caido.
- The session token and disabled header redaction expose credentials in the model context.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/c0tton-fluff/caido-mcp-server/main/install.sh | bashThe first README option installs a prebuilt binary. `go install` and a source build also exist.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent sends real HTTP requests and runs fuzzing against targets, and calling it on someone else's system without permission is illegal.
- Some tools delete projects, scopes and findings in Caido.
- The session token and disabled header redaction expose credentials in the model context.
This is third-party code. Review the repository files before installing.
What it does
caido-mcp-server connects the Caido proxy to Claude Code and Cursor over MCP. The agent searches history with HTTPQL, reads headers and bodies, diffs two responses and replays requests through Replay. The server exposes 70 tools and 6 read-only resources. The same code also ships as a standalone terminal CLI. Tools cover Replay sessions with a shared cookie jar, race tests through Replay Pipelines (Caido 0.59 and newer), Automate sessions, findings, scopes, Match & Replace rules and intercept. Authorization, Cookie and API key values are redacted from output by default.
Who it is for. Pentesters and bug hunters who keep a project in Caido and hand traffic review and request replay to an agent.
Good fit when
- Look for POST requests to `/api` with a specific parameter among hundreds in proxy history.
- Test for IDOR: the agent takes a captured request, swaps the user id and compares responses.
- For a vulnerability report the agent collects findings and exports a request as a curl command.
- Check a race condition with a single-packet run through Replay Pipelines.
Not a fit when
- The system is tested without its owner's permission.
- Caido is not running, or older than 0.59 while you need Replay Pipelines race tests.
- The Caido session token must not reach the agent environment.
Example request
Show POST requests to `/api` from the last hour, replay the third with a different user_id and compare the responses.MCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
CAIDO_URLrequired- Address of the local Caido, for example `http://127.0.0.1:8080`.
CAIDO_ACCESS_TOKENsecret- Caido session token. Needed when OAuth login was not performed.
CAIDO_ALLOW_SENSITIVE_HEADERS- A `true` value disables redaction of Authorization, Cookie and API key headers in output.
Limitations
The server talks to the local Caido app through its GraphQL API and uses the session access token from your Caido login, not a Caido Cloud personal token prefixed `caido_`. A token taken from the browser console lasts about 7 days; for long sessions use OAuth login (`caido-mcp-server login`), which refreshes itself. `CAIDO_ALLOW_SENSITIVE_HEADERS` sends real authorization header values into the model context, so keep it off unless needed. Some tools delete projects, scopes and findings; confirm such calls manually. Response bodies are trimmed to a few kilobytes by default, and the full text needs an explicit `bodyLimit`.
How to disable. Remove the `caido` entry from your MCP configuration. If you signed in through OAuth, delete `~/.caido-mcp/tokens/`. The session token in Caido is replaced by signing in again.
FAQ
Where do I get the CAIDO_ACCESS_TOKEN value?
Open developer tools in Caido and run `JSON.parse(localStorage.CAIDO_AUTHENTICATION).accessToken` in the console. The token lives about 7 days. For permanent use run `CAIDO_URL=http://localhost:8080 caido-mcp-server login`.
Does the agent see passwords and cookies from traffic?
Not by default: Authorization, Cookie and API key headers are replaced with `[REDACTED]`. Real values appear only with `CAIDO_ALLOW_SENSITIVE_HEADERS=true`.
How do I connect the server to Claude Code or Cursor?
Add a `caido` server to your MCP configuration with the command `caido-mcp-server` and the argument `serve`, and pass `CAIDO_URL` in `env`. Cursor and other clients take the same block.
Is there a CLI without MCP?
Yes. A separate `caido-cli` for the terminal is built alongside and uses the same token and SDK.
Which Caido versions are needed?
Race tests through Replay Pipelines need Caido 0.59 or newer. The other tools work with the local app through its GraphQL API. `caido_get_instance` reports the version and platform.
Discussion
No questions or reviews yet.
Related
MCP serversThe official Caido skill for agents: search HTTP history with HTTPQL, test requests through the Caido proxy, add replace rules and hand findings to Replay
Security scanner for MCP servers that looks for hardcoded keys, tool poisoning and injection flaws in repository code.
MCP server on mitmproxy: the agent reads HTTP traffic, rewrites responses, replays requests and builds an API spec.
CLI mediator scans agent network requests and MCP calls for secret leaks, unsafe destinations and injected instructions
A scanner that finds leaked keys, dangerous access and connected models in MCP configs of Claude Desktop, Cursor and VS Code.
MCP-Shield finds your MCP configs, connects to servers and scans tool descriptions for hidden commands, exfiltration channels and tool shadowing
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| caido-mcp-server (this card) | no | key is optional | 138 | |
| Caido Skills | yes | 287 | the official Caido skill with HTTPQL search; this server adds 70 MCP tools including Automate, findings and intercept | |
| Burp Suite MCP Server | yes | not required | 1 | works with the Burp Suite proxy; this one targets the Caido proxy and ships a CLI on the same code |
README in short
One codebase provides an MCP server and a CLI. The README covers installation, two authorization routes, the list of 70 tools and safeguards: header redaction, read and write annotations and input length limits.