Caido
Caido is a web security testing toolkit built around an intercepting proxy. Route a browser through Caido to inspect HTTP requests and responses, modify traffic, and replay requests while testing an application.
Use HTTP History to review captured traffic, Intercept to pause and edit it, and Replay to resend individual requests. Scopes and filters help focus on the application you are testing; workflows and plugins extend the toolkit.
Install and launch
The full Monarch software bundle includes caido-desktop. If it is missing, install it with:
monarch pkg add caido-desktopOpen Caido from the application launcher. Start the local instance and follow the sign-in flow. On first use, name the instance and approve access for your Caido account. Available features depend on your Caido plan.
The examples on this page use the default local listening address, http://127.0.0.1:8080. If you change it, use the same address in your browser proxy and MCP configuration.
First steps
Create a project
Click Create a project, give it a descriptive name, and select it before collecting traffic. A separate project per application or engagement makes captured requests easier to organize.
Connect a browser
The quickest route is Caido’s preconfigured browser launcher: open the browser control in the top-right toolbar and click Launch for an installed Chrome or Chromium browser. This avoids manually configuring the proxy and importing the certificate for that browser session.
To use another browser or an existing testing profile:
Configure its HTTP proxy to use 127.0.0.1, port 8080, for both HTTP and HTTPS traffic. You can use the browser’s proxy settings or a proxy-switching extension such as FoxyProxy.
For HTTPS, import Caido’s CA certificate as described below.
Browse your test application and check that requests appear in HTTP History.
See Using a preconfigured browser and FoxyProxy setup for browser-specific instructions.
Configure HTTPS interception
When using a manually configured browser:
In Caido, open the account menu in the top-right corner and select CA Certificate.
Download the CA certificate.
Import it into your testing browser’s trusted certificate authorities. In Firefox, open Settings → Privacy & Security → Certificates → View Certificates → Authorities → Import, select the downloaded certificate, and enable Trust this CA to identify websites.
Visit an HTTPS page through the proxy and inspect the request and response in HTTP History.
For Chrome and other browser-specific details, follow Caido’s certificate import guide.
Intercept a request
Open Intercept and enable interception, then perform an action in the browser. Caido pauses matching traffic so you can inspect or edit it before forwarding it, or drop it.
Forward the paused request to let the browser continue. Turn interception off when you want to browse normally while continuing to capture traffic in HTTP History. If the browser appears to be waiting indefinitely, check for a paused request.
Replay a request
In HTTP History, right-click a request and choose Send to Replay. Open Replay, adjust a parameter, header, or body, and send the request. Compare the response with earlier attempts to understand the effect of your changes.
See Replay for the full workflow.
MCP integration
The caido-mcp-server package lets an MCP-compatible assistant work with traffic and other data in your local Caido instance. Caido must be running whenever the assistant uses the server.
Install and authenticate
Install the server from the Monarch package repository:
If Caido itself is missing, install
caido-desktopas well.Open Caido and sign in. The examples below use its default local address,
http://127.0.0.1:8080. If you changed Caido's listening address, use your address in both the login command and client configuration.In a terminal under your normal user account, run:
Follow the browser prompt and approve the connection in Caido. Run this command again if you need to authenticate another user or Caido instance.
Connect an MCP client
Add a stdio server to your MCP client's configuration. For clients that use a mcpServers JSON object, the entry is:
Use your client's configuration format if it differs. The package installs the executable at /usr/bin/caido-mcp-server. Restart the client after adding the entry, keep Caido open, and ask the assistant to list the Caido projects or HTTP requests to check the connection. Approve MCP tool calls only when you intend the requested action.
If the connection fails, check that Caido is running, the URL in CAIDO_URL matches the address used for login, and the client runs as the Linux user who authenticated. You can repeat caido-mcp-server login -u <your-caido-url> to renew access.
For client-specific examples and the available tools, see Caido's MCP server guide.
Further reading
Caido documentation — features, setup, and advanced guides.
Web testing — Burp Suite and SecLists on Monarch.