Proxypin Mcp Server

What is Proxypin Mcp Server?

Proxypin Mcp Server is a Model Context Protocol (MCP) server that integrates with the open‑source ProxyPin tool to expose your local HTTP capture history to MCP‑capable clients. It reads ProxyPin’s HAR files and provides tools for listing, searching, and analyzing captured requests, as well as generating API code snippets.

How to use Proxypin Mcp Server?

Install and open ProxyPin, enable “Cache Date” in History settings, and ensure some capture history exists. Run npx -y proxypin-mcp@latest (the NPX bridge tries uvx first then falls back to uv tool run). Add the following configuration to your MCP client’s config file:

{
  "mcpServers": {
    "proxypin": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "proxypin-mcp@latest"]
    }
  }
}

If your client does not support type, remove that field.

Key features of Proxypin Mcp Server

• Reads local ProxyPin capture history (HAR files)
• Lists, searches, and retrieves individual captured requests
• Analyzes API structure for a given domain
• Generates API call code (Python, JavaScript, TypeScript, cURL)
• Works with Windsurf, Cursor, Claude Desktop, and Codex
• Configurable scan limits and body size via environment variables

Use cases of Proxypin Mcp Server

• Debugging web requests by inspecting captured traffic from ProxyPin
• Searching historical HTTP requests for specific keywords or patterns
• Analyzing endpoint structures to understand an API’s design
• Generating client code snippets from captured requests for reuse
• Automating request inspection workflows within an MCP‑powered IDE

FAQ from Proxypin Mcp Server

What are the runtime requirements?

You need Node.js (for npx) and uv installed. The server also requires ProxyPin to be installed, open, and configured to cache history (enable “Cache Date”).

How does it connect to ProxyPin?

It reads HAR files from ProxyPin’s local data directory. The path can be set via the PROXYPIN_DATA_DIR environment variable or auto‑detected. No network connection to ProxyPin is needed.

What data can be retrieved?

The server exposes recent requests (with optional filters), single request details including body, search results across URL and bodies, a list of captured domains with request counts, and API structure analysis per domain.

Which MCP clients are supported?

It works with Windsurf, Cursor, Claude Desktop, and Codex. Any client that can run a stdio MCP server should be compatible.

Are there any limits on the data scanned?

By default, the server scans up to 50 HAR files (PROXYPIN_HAR_LIMIT) and keeps at most 102,400 bytes of body content per request (PROXYPIN_MAX_BODY_SIZE). These can be adjusted via environment variables.