ProxyPin MCP Server
Exposes ProxyPin's local network capture history to MCP-capable clients for searching, analyzing, and detailing captured HTTP traffic. It enables users to perform API structure analysis and generate client-side code directly from captured requests.
README
ProxyPin MCP Server
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.
Features
- Read local ProxyPin history (HAR)
- List/search/detail tools for captured requests
- API structure analysis and code generation
- Works with mainstream MCP clients (Windsurf / Cursor / Claude Desktop / Codex)
Prerequisites
- Install and open ProxyPin
- In ProxyPin History settings, enable “Cache Date” (required)
- Ensure some capture history exists
- Node.js (for
npx) anduv(foruvx)
Installation
Run with npx
npx -y @elonjask/proxypin-mcp@latest
Usage
Add the following configuration to your MCP client configuration file:
{
"mcpServers": {
"proxypin": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@elonjask/proxypin-mcp@latest"]
}
}
}
[!TIP] If your client does not support
type, remove the field.
Environment Variables
| 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 |
Available Tools
list_requests
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_request
Get a single request detail by ID.
Parameters:
request_id(string, required)include_body(boolean, optional, default true)
search_requests
Search requests by keyword.
Parameters:
keyword(string, required)search_in(string:all|url|request_body|response_body)limit(int, optional, default 20)
analyze_api
Analyze API structure for a domain.
Parameters:
domain(string, required)
get_domains
List captured domains with counts.
Parameters:
- none
generate_code
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)
License
This project is licensed under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.