mcp-security-mitmproxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MITM_WEB_HOST | No | Bind address for mitmweb REST/Web UI interface (R1). | 127.0.0.1 |
| MCP_MITM_WEB_PORT | No | HTTP port for web interface and REST bridge. | 8081 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mitmdump_startB | Start a headless mitmdump capture session with explicit proxy modes, optional .mitm output saving, flow filtering and scripts. |
| mitmdump_stopB | Stop an active mitmproxy/mitmdump/mitmweb session and release ports. |
| mitmdump_replayC | Replay flows through mitmdump using client (-C) or server (-S) replay from existing .mitm dump files. |
| mitmweb_startC | Start an interactive mitmweb proxy session with web UI and REST API bridge enabled. |
| mitmweb_stopB | Stop an active mitmweb session and release listen and web ports. |
| mitmweb_get_flowsC | Retrieve captured flows (HTTP/WebSocket/TCP/UDP) from a running mitmweb session. |
| mitmweb_get_flow_detailA | Fetch detailed inspection data for a single flow from mitmweb, including headers, payloads and content views, with automatic secret redaction. |
| session_listA | List all active, stopped and managed mitmproxy sessions. |
| session_statusB | Get the detailed status and runtime parameters of a session by ID. |
| mitm_execute_commandC | Execute an allowlisted command on an active mitmweb session (e.g. view.clear, flow.kill). |
| mitm_export_flowA | Export a captured flow to an external format (curl, httpie, raw, raw_request, raw_response) from an active session's dump or directly from a .mitm dump file. The exported content has secrets redacted (R4). |
| mitm_filter_flowsB | Filter flows using mitmproxy FlowFilter expressions (~u, ~m, ~c, ~b, ~h, ~d, etc.) evaluated either from a .mitm dump file or from an active session. |
| mitm_set_map_remoteB | Redirect requests matching a URL regex to another remote URL (mitmproxy map_remote). Applied live over mitmweb. |
| mitm_set_map_localA | Serve a mocked response for requests matching a URL regex from a local file or directory. The path MUST be inside allowed_mock_roots (R3). |
| mitm_modify_headersC | Set or remove an HTTP header on matching requests/responses (mitmproxy modify_headers). |
| mitm_modify_bodyB | Regex-substitute inside matching request/response payloads (mitmproxy modify_body, DOTALL). |
| mitm_list_rulesC | List the active map_remote/map_local/modify_headers/modify_body rules. |
| mitm_clear_rulesA | Clear active rules. Pass rule_type to clear one family, or omit it to clear all four. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Every tool targets a distinct mitmproxy operation: session lifecycle, flow inspection/export/filtering, and rule management are cleanly separated. Even similarly named start/stop tools are disambiguated by mitmdump vs mitmweb mode, and the rule tools map clearly to remote/local/header/body mutations.
Most tools follow a verb_noun pattern under a mitm/mitmdump/mitmweb prefix, e.g. get_flows, export_flow, clear_rules. The noun-first session_list and session_status tools deviate slightly, and get vs list is mixed across tools, but the overall pattern remains predictable.
At 18 tools, this is above the ideal 3–15 range and feels heavy, though the tools are not redundant. The count is justified by the breadth of mitmproxy functionality but still pushes the server into the 'heavy' band.
The server covers the complete proxy workflow: start/stop sessions, replay, retrieve/filter/export flows, and apply map/modify rules. Minor gaps remain, such as no direct intercept/breakpoint controls or explicit session/dump cleanup, but agents can work around these with the provided command and rule tools.