MCP Server for ProxyPin - expose HTTP capture data to AI tools
{
"mcpServers": {
"proxypin-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP Server for ProxyPin - expose HTTP capture data to AI tools
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 39 days ago. 10 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Proxypin Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
ProxyPin MCP Server is based on the Model Context Protocol (MCP). It works with the open source project ProxyPin to expose your local capture history to MCP-capable clients.
npx) and uv (launcher supports both uvx and uv tool run)npx -y proxypin-mcp@latest
The NPX bridge tries uvx first, then automatically falls back to uv tool run.
Add the following configuration to your MCP client configuration file:
{
"mcpServers": {
"proxypin": {
"type": "stdio",
"command": "npx",
"args": ["-y", "proxypin-mcp@latest"]
}
}
}
[!TIP] If your client does not support
type, remove the field.
| Variable | Description | Default |
|---|---|---|
| PROXYPIN_DATA_DIR | ProxyPin history directory | auto-detect |
| PROXYPIN_HAR_LIMIT | max HAR files scanned | 50 |
| PROXYPIN_MAX_BODY_SIZE | max body bytes kept | 102400 |
List recent captured requests.
Parameters:
limit (int, optional, default 20)detail (string: summary | key | full)domain (string, optional)method (string, optional)status (int, optional)Get a single request detail by ID.
Parameters:
request_id (string, required)include_body (boolean, optional, default true)Search requests by keyword.
Parameters:
keyword (string, required)search_in (string: all | url | request_body | response_body)limit (int, optional, default 20)Analyze API structure for a domain.
Parameters:
domain (string, required)List captured domains with counts.
Parameters:
Generate API call code from a captured request.
Parameters:
request_id (string, required)language (string: python | javascript | typescript | curl)framework (string: requests | httpx | fetch | axios)list_requests: list recent HTTP requests with filters.get_request: fetch one request by ID.search_requests: keyword search across URL and body.analyze_api: group endpoint patterns for one domain.get_domains: summarize captured domains and method counts.generate_code: generate Python/JS/cURL snippets from a capture.analyze_api_prompt(domain): guide API structure analysis workflow.debug_request_prompt(request_id): guide request debugging workflow.proxypin://requests/recent: recent request summary dataset.proxypin://domains: captured domains summary dataset.This project is licensed under the MIT License.