mitmproxy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxy_startC | Start the mitmproxy capture proxy. |
| proxy_stopA | Stop the mitmproxy capture proxy. |
| proxy_statusA | Get the current proxy status and number of captured flows. |
| flows_loadB | Load flows from a .mitm file into memory. |
| flows_saveB | Save all in-memory flows to a .mitm file. |
| flows_listC | List captured flows with optional filtering and pagination. |
| flow_getB | Get the full details of a single flow. |
| flows_clearC | Clear all in-memory flows. Optionally stop the proxy too. |
| flow_replayC | Replay a captured flow using mitmproxy's built-in replay.client. |
| request_sendC | Send a new HTTP request using mitmproxy's built-in replay.client. |
| flow_updateC | Modify a captured request/response and its metadata. |
| flow_createB | Create a new request flow and store it (without sending). |
| flow_deleteC | Delete a flow from memory. |
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 13 tools
Each tool targets a distinct operation: proxy lifecycle management, flow singular vs plural actions, and request sending. Descriptions clearly differentiate between creating a flow without sending versus sending a request.
All tool names follow a consistent prefix_verb pattern with underscores (e.g., proxy_start, flows_list, flow_update). Singular vs plural prefixes are used appropriately for single vs batch operations.
13 tools cover proxy management, flow CRUD, load/save, replay, and request sending without unnecessary overlap. The scope aligns well with the mitmproxy domain.
The set covers the full lifecycle: proxy start/stop/status, flow capture, retrieval, creation, modification, deletion, persistence, and replay/send. No obvious gaps for standard proxy operations.