MCP integration

When enabled, Cursor and similar tools can call DevPeek on this machine to search captured traffic and change Mock plus selected settings, without clicking through the UI.

Turn it on in Settings

1. Open Settings → MCP integration. The title shows a Pro mark.
2. Turn on Enable MCP. The service listens only on the loopback address and creates an access token. The default port is 17892.
3. Copy the Cursor mcp.json snippet. It includes the sidecar path, port, and token. The installer ships the sidecar.
4. Put the snippet in Cursor’s local MCP config and connect to this service.

MCP can read captured traffic and crypto keys. Enable it only in a trusted environment, and do not share the token or the mcp.json snippet.

What it can do

• Search historical requests and WebSocket frames, and open one request or connection.
• List, add, or update Mock rules. A rule created from a capture stays disabled.
• Read or change proxy, conversion, param transform, forward rules, and weak-network settings.
• List or save WS Flow rules.

What it does not do

• It does not clear captures, manage certificates, sign in, or run scripts on the debug page.
• You cannot copy a usable mcp.json until MCP is enabled and the sidecar file is present.

Troubleshooting

• Copy is unavailable: enable MCP first and wait until an access token exists.
• Sidecar not found: use a complete installer. Installers from 1.4.2 onward include the MCP sidecar.
• Port in use: pick a free port from 1 to 65535 on the same page, and point Cursor at that port.