Get the FREE Ultimate OpenClaw Setup Guide →

caido

MCP server from lambdasawa/caido-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio lambdasawa-caido-mcp-server caido-mcp-server serve \
  --env CAIDO_URL="http://localhost:8080"

How to use

This MCP server provides access to Caido proxy history via the MCP interface. It lets you list captured HTTP requests with optional HTTPQL filters, fetch detailed information for specific requests (with selectable sections like metadata, headers, and bodies), and batch-fetch multiple requests in a single call. You can also paginate large response bodies and rely on OAuth authentication with automatic token refresh when accessing Caido resources. Once configured, you can prompt supported tools (e.g., Claude Code) to analyze, compare, or trace requests across sessions to identify data exposure issues, access control gaps, or provenance of tokens and IDs across requests.

How to install

Prerequisites:

  • Go toolchain installed (go version 1.18+ recommended)
  • Git installed
  • Access to Caido instance if using real data

Installation steps:

  1. Install the binary from the Go module:
go install github.com/lambdasawa/caido-mcp-server@latest
  1. Verify the binary is on your PATH:
caido-mcp-server --version
  1. (Optional) Build from source manually:
git clone https://github.com/lambdasawa/caido-mcp-server.git
cd caido-mcp-server
go build -o caido-mcp-server .
  1. Ensure Caido is reachable and you can authenticate as described in the usage section below.

Additional notes

Tips and notes:

  • The MCP server expects Caido URL via the CAIDO_URL environment variable during authentication and interactions.
  • After authenticating, your token is saved to ~/.caido-mcp/token.json; ensure this path is writable.
  • When running the server, keep CAIDO_URL reachable from the host where you run the MCP server to avoid authentication issues.
  • If you encounter permissions or network issues, run with elevated privileges or adjust firewall/proxy settings accordingly.
  • The server supports typical MCP tooling patterns: you can configure .mcp.json to point to the running caido MCP server and then use tools that understand the MCP protocol.
  • If you need to customize the host, port, or TLS settings, consider extending the environment with additional CA/HTTP settings as needed by Caido.

Related MCP Servers

Sponsor this space

Reach thousands of developers