How do I use proxypin-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@proxypin-mcp Show me the last 5 HTTP requests" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

proxypin-mcp

by k186

Overview Schema Related Servers Score Discussions

JavaScript

Local

proxypin-mcp

MCP server for ProxyPin — let AI analyze your HTTP(S) traffic in real-time.

English | 中文

How it works

┌─────────────────────────────────────────────────────────────┐
│                        ProxyPin App                         │
│                                                             │
│  MITM Proxy ──▶ EventListener ──▶ WsTrafficServer :12080   │
│                                         │   ▲              │
│                                    push │   │ commands     │
│                                         │   │ (history)    │
└─────────────────────────────────────────┼───┼──────────────┘
                                          │   │
                                     WS   │   │  WS
                                          ▼   │
┌─────────────────────────────────────────────────────────────┐
│                       proxypin-mcp                          │
│                                                             │
│  Ring Buffer (real-time)    ◀── request / response msgs     │
│  sendCommand() / pendingCmds ──▶ cmd_reply (history)        │
│                                                             │
│  MCP Tools ──▶ Claude Code / AI                             │
└─────────────────────────────────────────────────────────────┘

Real-time traffic: ProxyPin pushes every request and response through WebSocket. The MCP server buffers them in a ring buffer (default 1000 entries) and exposes them via list_requests / get_request / search_requests.

History: The MCP sends commands (list_histories, get_history, search_history, get_history_detail) over the same WebSocket. ProxyPin reads the HAR files on its end and returns only the fields needed — summaries for list/search, full HAR only for get_history_detail. This keeps AI context size bounded regardless of how many times history tools are called.

Config sync: ProxyPin sends a config message to the MCP on connect and whenever settings change (e.g. history access toggled), keeping the two sides in sync without polling.

Related MCP server: ProxyPin MCP Server

Quick Start

1. Enable WebSocket Push in ProxyPin

Settings → WebSocket Push → Enable (default port: 12080)

2. Configure MCP

Add to your .mcp.json:

{
  "mcpServers": {
    "proxypin": {
      "command": "npx",
      "args": ["@k186/proxypin-mcp@latest", "--port", "12080"]
    }
  }
}

3. Use with AI

AI can now call these tools to analyze your traffic:

Real-time tools

list_requests — Browse recent captured requests
get_request — Get full request/response details (headers, body, timing)
search_requests — Filter by URL keyword, HTTP method, or status code
get_stats — Overview: connection status, status code distribution, top domains
clear_buffer — Clear the buffer before a new capture session

History tools (requires History Access enabled in ProxyPin settings)

list_histories — List all saved history sessions
get_history_requests — Browse requests in a session (summary only)
search_history — Search across all sessions by URL/method/status
get_history_detail — Get full HAR entry for a specific request

Options

Flag	Env Variable	Default	Description
`--port`, `-p`	`PROXYPIN_PORT`	`12080`	ProxyPin WebSocket push port
`--buffer-size`	`PROXYPIN_BUFFER_SIZE`	`1000`	Max requests to keep in memory
—	`PROXYPIN_WS_URL`	`ws://127.0.0.1:{port}`	Full WebSocket URL (overrides port)

Examples

// Custom port
{ "args": ["@k186/proxypin-mcp@latest", "--port", "9999"] }

// Larger buffer
{ "args": ["@k186/proxypin-mcp@latest", "--port", "12080", "--buffer-size", "5000"] }

// Via environment variables
{
  "args": ["@k186/proxypin-mcp@latest"],
  "env": { "PROXYPIN_PORT": "12080", "PROXYPIN_BUFFER_SIZE": "2000" }
}

工作原理

┌─────────────────────────────────────────────────────────────┐
│                      ProxyPin 应用                          │
│                                                             │
│  MITM 代理 ──▶ EventListener ──▶ WsTrafficServer :12080    │
│                                        │   ▲               │
│                                   推送 │   │ 命令          │
│                                        │   │（历史记录）    │
└────────────────────────────────────────┼───┼───────────────┘
                                         │   │
                                    WS   │   │  WS
                                         ▼   │
┌─────────────────────────────────────────────────────────────┐
│                       proxypin-mcp                          │
│                                                             │
│  环形缓冲区（实时）     ◀── request / response 消息         │
│  sendCommand() / pendingCmds ──▶ cmd_reply（历史）          │
│                                                             │
│  MCP 工具 ──▶ Claude Code / AI                              │
└─────────────────────────────────────────────────────────────┘

实时流量：ProxyPin 将每条请求和响应通过 WebSocket 推送过来，MCP 缓存到环形缓冲区（默认 1000 条），通过 list_requests / get_request / search_requests 暴露给 AI。

历史记录：MCP 通过同一个 WebSocket 发送命令（list_histories / get_history / search_history / get_history_detail），ProxyPin 在自己这边读取 HAR 文件，只返回所需字段——列表/搜索只返回摘要，完整 HAR 仅在 get_history_detail 时返回。无论调用多少次历史工具，AI 上下文大小都在可控范围内。

配置同步：ProxyPin 在客户端连接时以及设置变更时（如切换历史访问开关）向 MCP 推送 config 消息，两端状态保持同步，无需轮询。

快速开始

1. 在 ProxyPin 中开启 WebSocket 推送

设置 → WebSocket推送 → 启用（默认端口：12080）

2. 配置 MCP

在 .mcp.json 中添加：

{
  "mcpServers": {
    "proxypin": {
      "command": "npx",
      "args": ["@k186/proxypin-mcp@latest", "--port", "12080"]
    }
  }
}

3. 让 AI 分析流量

AI 可以调用以下工具分析你的抓包数据：

实时工具

list_requests — 浏览最近捕获的请求列表
get_request — 查看完整的请求/响应详情（请求头、响应体、耗时）
search_requests — 按 URL 关键字、HTTP 方法或状态码过滤
get_stats — 总览：连接状态、状态码分布、Top 域名
clear_buffer — 清空缓冲区，开始新的抓包会话

历史工具（需在 ProxyPin 设置中开启"历史访问"）

list_histories — 列出所有历史会话
get_history_requests — 浏览某个会话的请求（仅摘要）
search_history — 跨所有会话按 URL/方法/状态码搜索
get_history_detail — 获取某条请求的完整 HAR 数据

配置参数

参数	环境变量	默认值	说明
`--port`, `-p`	`PROXYPIN_PORT`	`12080`	ProxyPin WebSocket 推送端口
`--buffer-size`	`PROXYPIN_BUFFER_SIZE`	`1000`	内存中最大缓存请求数
—	`PROXYPIN_WS_URL`	`ws://127.0.0.1:{port}`	完整 WebSocket 地址（覆盖 port）

配置示例

// 自定义端口
{ "args": ["@k186/proxypin-mcp@latest", "--port", "9999"] }

// 增大缓冲区
{ "args": ["@k186/proxypin-mcp@latest", "--port", "12080", "--buffer-size", "5000"] }

// 通过环境变量配置
{
  "args": ["@k186/proxypin-mcp@latest"],
  "env": { "PROXYPIN_PORT": "12080", "PROXYPIN_BUFFER_SIZE": "2000" }
}

License

MIT

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

1Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k186/proxypin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server