httptoolkit-mcp
An MCP server that enables AI assistants to control HTTP Toolkit for intercepting, inspecting, and debugging HTTP(S) traffic from browsers, mobile devices, and Docker containers. It provides tools for server management, interceptor activation, and sending HTTP requests through natural language commands.
README
httptoolkit-mcp
A Model Context Protocol (MCP) server that provides AI assistants with full control over HTTP Toolkit — the powerful, open-source HTTP(S) debugging proxy.
Intercept, inspect, and debug HTTP traffic from browsers, Android/iOS devices, Docker containers, JVM processes, and more — all through natural language via your AI assistant.
Features
- Live Traffic Capture — Capture intercepted HTTP traffic in real-time with full request/response headers and bodies
- Browser Interception — Launch Chrome or Firefox with traffic automatically routed through the proxy
- Android Interception — Intercept device traffic via ADB or target specific apps with Frida (bypasses certificate pinning)
- iOS Interception — Intercept specific iOS apps via Frida on jailbroken devices
- Docker Interception — Attach to running Docker containers and capture all outgoing HTTP traffic
- Terminal Interception — Open intercepted terminal sessions or configure existing ones
- JVM Attach — Attach to running Java/Kotlin/Clojure processes
- Electron Apps — Launch Electron applications with interception enabled
- HTTP Client — Send HTTP requests through the proxy with full control over method, headers, and body
- Server Management — Query configuration, manage interceptors, and control the server lifecycle
- Zero-Config with Desktop App — Automatically detects auth token from the running HTTP Toolkit desktop app
Prerequisites
- HTTP Toolkit installed and running (desktop app or server)
- Node.js >= 18
Installation
Using npx (recommended)
No installation required — just configure your MCP client:
{
"mcpServers": {
"httptoolkit": {
"command": "npx",
"args": ["-y", "httptoolkit-mcp"]
}
}
}
Global install
npm install -g httptoolkit-mcp
From source
git clone https://github.com/fdciabdul/httptoolkit-mcp.git
cd httptoolkit-mcp
npm install
npm run build
Configuration
Claude Code
Add to ~/.claude/settings.json or ~/.claude.json:
{
"mcpServers": {
"httptoolkit": {
"command": "npx",
"args": ["-y", "httptoolkit-mcp"]
}
}
}
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"httptoolkit": {
"command": "npx",
"args": ["-y", "httptoolkit-mcp"]
}
}
}
Environment Variables
| Variable | Description | Default |
|---|---|---|
HTK_SERVER_URL |
HTTP Toolkit management API URL | http://127.0.0.1:45457 |
HTK_SERVER_TOKEN |
Auth token (auto-detected from desktop app) | Auto-detected |
HTK_ADMIN_URL |
Mockttp admin API URL | http://127.0.0.1:45456 |
Note: When using the HTTP Toolkit desktop app, the auth token is automatically detected from the running process — no manual configuration needed.
Example with manual environment variables:
{
"mcpServers": {
"httptoolkit": {
"command": "npx",
"args": ["-y", "httptoolkit-mcp"],
"env": {
"HTK_SERVER_URL": "http://127.0.0.1:45457",
"HTK_SERVER_TOKEN": "your-token-here"
}
}
}
}
Available Tools
Traffic Capture
| Tool | Description |
|---|---|
capture_traffic |
Capture live intercepted HTTP traffic with full request/response bodies. Subscribes to the active HTTP Toolkit session via WebSocket. Supports auto-detection or manual session ID. |
Server Management
| Tool | Description |
|---|---|
get_version |
Get the HTTP Toolkit server version |
get_config |
Get proxy configuration (certificates, DNS, system proxy) |
get_network_interfaces |
List all network interfaces |
trigger_update |
Trigger a server update check |
shutdown_server |
Shutdown the HTTP Toolkit server |
Interceptor Management
| Tool | Description |
|---|---|
list_interceptors |
List all available interceptors and their status |
get_interceptor_metadata |
Get detailed metadata for a specific interceptor |
activate_interceptor |
Generic interceptor activation with custom options |
deactivate_interceptor |
Deactivate a running interceptor |
Browser Interception
| Tool | Description |
|---|---|
intercept_chrome |
Launch a fresh Chrome window with interception |
intercept_firefox |
Launch a fresh Firefox window with interception |
Terminal Interception
| Tool | Description |
|---|---|
intercept_fresh_terminal |
Open a new terminal with interception enabled |
intercept_existing_terminal |
Get commands to enable interception in an existing terminal |
Docker Interception
| Tool | Description |
|---|---|
intercept_docker_container |
Attach to a running Docker container |
Android Interception
| Tool | Description |
|---|---|
intercept_android_adb |
Intercept an Android device/emulator via ADB |
frida_android_setup |
Set up Frida on an Android device |
frida_android_launch |
Launch Frida server on an Android device |
frida_android_intercept |
Intercept a specific Android app via Frida |
iOS Interception
| Tool | Description |
|---|---|
frida_ios_intercept |
Intercept a specific iOS app via Frida |
Application Interception
| Tool | Description |
|---|---|
intercept_jvm |
Attach to a running JVM process |
intercept_electron |
Launch an Electron app with interception |
HTTP Client
| Tool | Description |
|---|---|
send_http_request |
Send an HTTP request through the proxy |
Usage Examples
Once configured, you can ask your AI assistant things like:
- "Capture the HTTP traffic from my intercepted Chrome for 10 seconds"
- "List all available interceptors"
- "Intercept Chrome on port 8000"
- "Show me the connected Android devices"
- "Attach to the Docker container running my API"
- "Send a GET request to https://api.example.com/users"
- "Set up Frida on my Android device and intercept the target app"
- "Open an intercepted terminal session"
Capture Traffic Example
User: "Capture traffic from my browser for 5 seconds"
capture_traffic({ duration: 5, sessionId: "2474b580-482e-4a79-8488-121583d466e1" })
Result:
{
"capturedExchanges": 2,
"exchanges": [
{
"request": {
"method": "GET",
"url": "https://api.example.com/users",
"headers": { "host": "api.example.com", ... },
},
"response": {
"statusCode": 200,
"headers": { "content-type": "application/json", ... },
"body": "[{\"id\": 1, \"name\": \"John\"}]"
}
}
]
}
Architecture
┌─────────────────┐ stdio ┌──────────────────┐ REST API ┌─────────────────────┐
│ AI Assistant │◄─────────────►│ httptoolkit-mcp │◄────────────►│ httptoolkit-server │
│ (Claude, etc.) │ MCP │ (this project) │ :45457 │ (HTTP Toolkit) │
└─────────────────┘ └──────────────────┘ └─────────────────────┘
│ │
│ WebSocket ┌────────┴────────┐
│ (traffic capture) │ Mockttp Proxy │
└──────────────────────────►│ :45456 (admin) │
│ :8000 (proxy) │
└────────┬────────┘
│
┌───────────────┼───────────────┐
│ │ │
Browsers Android/iOS Docker
Devices Containers
Credits
This project is an MCP interface for HTTP Toolkit, created by Tim Perry (@pimterry).
- HTTP Toolkit — github.com/httptoolkit
- HTTP Toolkit Server — github.com/httptoolkit/httptoolkit-server
- Tim Perry — github.com/pimterry — Creator & maintainer of HTTP Toolkit
HTTP Toolkit is a beautiful, open-source tool for debugging, testing, and building with HTTP(S). If you find it useful, consider supporting the project.
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。