Caido is a proxy for inspecting and replaying HTTP traffic. Kiro CLI can call external tools through the Model Context Protocol (MCP). Connect the two and you can ask Kiro to read your proxy history, explain requests, and help you reason about what you captured, without copying traffic into a chat window.

This guide sets up that connection on Linux in ten steps and ends with a read-only test.

How it fits together

Diagram of Kiro CLI connecting through MCP to caido-mcp-server, which calls the Caido Desktop API on localhost.
Overview — Kiro CLI talks MCP to caido-mcp-server, which talks to your local Caido instance.

Kiro CLI starts caido-mcp-server serve as an MCP server. That process uses the OAuth token you create in step 4 to call the Caido instance at CAIDO_URL. Kiro then lists whatever tools the server exposes.

Requirements

Requirement Notes
Linux Arch Linux here; other distributions work the same way
Caido Desktop Installed and running before you log in
Kiro CLI Installed and authenticated
Go Used to install the MCP server

Step 1 — Verify Go

go version

Expected output:

go version go1.27.3-X:nodwarf5 linux/amd64
Terminal running go version and printing the installed Go version.
Figure 1 — Go is installed. Illustration of the expected output.

Step 2 — Install the Caido MCP server

go install github.com/c0tton-fluff/caido-mcp-server/v4/cmd/caido-mcp-server@latest

Check that the binary is on your path:

which caido-mcp-server

Expected output (your Go bin directory may differ):

~/go/bin/caido-mcp-server
Terminal running go install for caido-mcp-server and then which caido-mcp-server, printing the binary path in the Go bin directory.
Figure 2 — Installing the server with go install, then locating the binary.

Step 3 — Check the available commands

caido-mcp-server --help
  • login authenticates with Caido.
  • serve starts the MCP server.
  • completion generates shell autocompletion scripts.
Terminal showing caido-mcp-server --help listing the login, serve and completion commands.
Figure 3 — The three commands: login, serve and completion.

Step 4 — Authenticate with Caido

Start Caido Desktop, then run:

caido-mcp-server login -u http://127.0.0.1:8080

The server starts an OAuth device flow and prints an authentication URL, a temporary user code, and an expiry time. Open the URL in your browser, enter the code, and approve the connection.

Terminal showing caido-mcp-server login starting an OAuth device flow with a placeholder URL, a placeholder user code and an expiry time.
Figure 4 — The device flow prints a URL and a one-time code (placeholders here). Never publish a real code.

When you approve, the terminal shows:

Authentication successful!

You can now use 'caido-mcp serve' to start the MCP server.

The token is stored under ~/.caido-mcp/tokens/.

Terminal showing Authentication successful and a hint to use caido-mcp serve.
Figure 5 — Authorization complete. The token is stored under ~/.caido-mcp/tokens/.

Step 5 — Check Kiro’s MCP support

kiro-cli mcp --help

The commands are add, remove, list, import, and status. You will use add to register Caido.

Terminal showing kiro-cli mcp --help listing add, remove, list, import and status.
Figure 6 — kiro-cli mcp supports add, remove, list, import and status.

Step 6 — Look at the Kiro settings directory

ls -la ~/.kiro/settings/

This shows what is already configured before you add a server.

Terminal running ls -la on the Kiro settings directory to inspect existing configuration.
Figure 7 — Look at the existing configuration before you add a server.

Step 7 — Add Caido to Kiro CLI

Register Caido as a global MCP server:

kiro-cli mcp add \
  --name caido \
  --scope global \
  --command ~/go/bin/caido-mcp-server \
  --args serve \
  --env CAIDO_URL=http://127.0.0.1:8080
Parameter Description
--name caido Name of the MCP server
--scope global Makes it available in every project
--command Path to the server executable
--args serve Starts the server
--env Sets the Caido instance URL

Expected output:

✓ Added MCP server 'caido' to global config

The configuration is stored in ~/.kiro/settings/mcp.json.

Terminal running kiro-cli mcp add with the name caido, global scope, the server command, the serve argument and the CAIDO_URL environment variable.
Figure 8 — Registering the Caido MCP server globally.

Step 8 — Verify the configuration

kiro-cli mcp list
kiro-cli mcp status --name caido

list should show caido under the default Kiro agent. In the status output, check that:

  • the server name is caido
  • the command points to your caido-mcp-server binary
  • Disabled is false
  • the environment contains CAIDO_URL=http://127.0.0.1:8080
Terminal showing kiro-cli mcp list with caido registered under the default agent.
Figure 9 — Caido appears under the default Kiro agent.
Terminal showing kiro-cli mcp status for caido with the command, disabled false and the CAIDO_URL environment variable.
Figure 10 — Name, command, Disabled: false and the CAIDO_URL variable.

Step 9 — Confirm the connection inside Kiro CLI

Start Kiro CLI and open the MCP view:

kiro-cli
/mcp

caido should show as running, with the number of tools it exposes in the Details column. That number depends on the server version, so don’t expect a specific count.

Kiro CLI /mcp view showing the caido server with status running and its tools loaded.
Figure 11 — Kiro CLI loaded the server and discovered its tools. The tool count depends on your server version.

Step 10 — Test the tools

Ask Kiro what the server offers:

List all available Caido tools and explain what each one does.
Kiro CLI prompt asking to list all available Caido tools and explain what each one does.
Figure 12 — Ask Kiro what the server can do before you rely on it.

Then run a read-only test against your proxy history:

Show me the latest 10 HTTP requests from my Caido proxy history.
Do not modify or replay anything.
Kiro CLI prompt asking for the latest 10 HTTP requests from Caido history without modifying or replaying anything.
Figure 13 — A read-only request: list history and change nothing.

If both prompts work, the integration is done.

Troubleshooting

  • caido-mcp-server: command not found. Add your Go bin directory (~/go/bin by default) to PATH, or pass the full path to --command.
  • Login fails or times out. Check that Caido Desktop is running and that the -u URL matches the address Caido listens on. Run login again to get a fresh code.
  • caido is not running in /mcp. Run kiro-cli mcp status --name caido and confirm Disabled is false and CAIDO_URL is correct. Restart Kiro CLI after changing the configuration.

Security notes

  • Never share the OAuth device code or the files in ~/.caido-mcp/tokens/.
  • Captured traffic often contains cookies, authorization headers, and personal data. Redact them before you paste anything into a report or post.
  • Read what Kiro plans to do before you let it modify or replay a request.
  • Use this only against systems you are authorized to test.