Skip to main content
Glama
mitmproxy-mcp MCP Server

mitmproxy-mcp MCP Server

by lucasoeth

mitmproxy-mcp MCP server

A MCP server project

Components

Resources

The server implements a simple note storage system with:

  • Custom note:// URI scheme for accessing individual notes

  • Each note resource has a name, description and text/plain mimetype

Prompts

The server provides a single prompt:

  • summarize-notes: Creates summaries of all stored notes

    • Optional "style" argument to control detail level (brief/detailed)

    • Generates prompt combining all current notes with style preference

Tools

The server implements one tool:

  • add-note: Adds a new note to the server

    • Takes "name" and "content" as required string arguments

    • Updates server state and notifies clients of resource changes

Related MCP server: Datetime MCP Server

Configuration

[TODO: Add configuration details specific to your implementation]

Quickstart

Install

Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Development

Building and Publishing

To prepare the package for distribution:

  1. Sync dependencies and update lockfile:

uv sync
  1. Build package distributions:

uv build

This will create source and wheel distributions in the dist/ directory.

  1. Publish to PyPI:

uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: --token or UV_PUBLISH_TOKEN

  • Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /Users/lucas/Coding/mitmproxy-mcp run mitmproxy-mcp

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

Available Tools

4 tools
analyze_protectionC

Analyze flow for bot protection mechanisms and extract challenge details

Inputs: session_id (required), flow_index (required), extract_scripts.

extract_json_fieldsC

Extract specific fields from JSON content in a flow using JSONPath expressions

Inputs: session_id (required), flow_index (required), content_type (required), json_paths (required).

get_flow_detailsC

Lists HTTP requests/responses from a mitmproxy capture session, showing method, URL, and status codes

Inputs: session_id (required), flow_indexes (required), include_content.

list_flowsC

Retrieves detailed HTTP request/response data including headers, content (or structure preview for large JSON), and metadata from specified flows

Inputs: session_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap that could cause confusion. 'get_flow_details' and 'list_flows' both retrieve HTTP flow data, with 'get_flow_details' focusing on method/URL/status and 'list_flows' providing headers/content/metadata—these boundaries are unclear and might lead to misselection. However, 'analyze_protection' and 'extract_json_fields' are clearly distinct, targeting bot protection analysis and JSON field extraction respectively.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern, using snake_case throughout. 'analyze_protection', 'extract_json_fields', and 'list_flows' follow this well, but 'get_flow_details' deviates slightly by using 'get' instead of a more descriptive verb like 'show' or 'retrieve', which is a minor inconsistency in an otherwise predictable set.

    Tool Count5/5

    With 4 tools, the count is well-scoped for a mitmproxy server focused on HTTP flow analysis. Each tool appears to serve a distinct purpose within this domain, such as listing flows, analyzing protections, and extracting data, making the set neither too sparse nor overloaded for the intended functionality.

    Completeness3/5

    The tool surface has notable gaps for a mitmproxy domain. It covers flow retrieval, protection analysis, and JSON extraction, but lacks operations for modifying or intercepting flows (e.g., add, edit, block), which are core to proxy functionality. Agents can work around this by using existing tools for analysis, but the absence of manipulation tools limits completeness.

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches