whistle-mcp
The Whistle MCP Server enables AI assistants to manage Whistle proxy servers through natural language interactions via the Model Context Protocol. Key capabilities include:
Rule Management: Create, update, rename, delete, enable/disable rules
Group Management: Create, rename, delete groups, and manage rule associations
Value Management: Create, update, rename, delete values and value groups
Proxy Control: Toggle proxy settings including HTTP/HTTPS interception, HTTP/2 protocol, and multi-rule mode
Request Handling: View intercepted network requests, filter by URL, and replay requests with custom parameters
Status Monitoring: Get server status and current timestamp
Provides global installation via npm package manager, allowing users to easily set up the Whistle MCP Server tool through the npm ecosystem.
Supports integration with Raycast through MCP plugin installation, enabling users to control Whistle proxy servers via Raycast interface for network debugging and proxy configuration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@whistle-mcp show me all the rules I have configured"
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.
Whistle MCP Server
English | 中文
Project Introduction
Whistle MCP Server is a Whistle proxy management tool based on the Model Context Protocol (MCP), allowing AI assistants to directly operate and control local Whistle proxy servers. Through this tool, AI can help users manage rules, groups, values, monitor network requests, replay and modify requests, etc., without requiring manual operation of the Whistle interface. It greatly simplifies the process of network debugging, API testing, and proxy rule management, enabling users to complete complex network proxy configuration tasks through natural language interaction with AI.
Related MCP server: hotlogin-mcp
Features
Rule Management: Create, update, rename, delete, and enable/disable Whistle rules
Group Management: Create, rename, delete groups, and associate operations between rules and groups
Value Management: Create, update, rename, and delete values, with support for value group management
Proxy Control: Enable/disable proxy, HTTP/HTTPS interception, HTTP/2 protocol, etc.
Request Interception: View intercepted network request information, with URL filtering support
Request Replay: Support for replaying captured requests with custom request parameters
Multi-Rule Mode: Support for enabling/disabling multi-rule mode
Installation
Requirements
Node.js 18.20.0 or newer is required (see engines in package.json). Older versions are not supported.
Installing via Smithery
To install Whistle MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @7gugu/whistle-mcp --client claudeManual Installation
You can install Whistle MCP Server globally via npm:
npm install -g whistle-mcp-toolBuild from source
From the repository root:
npm install
npm run buildThe build output entry is dist/index.js (the same file used by the whistle-mcp CLI after a global install). You can also point MCP config at it with node and the path to dist/index.js.
MCP Configuration
Transport (stdio vs HTTP)
By default the server uses stdio (suitable for local MCP clients such as Cursor).
To expose Streamable HTTP and SSE on the same process (for remote or HTTP-capable clients), use --transport http-stream. FastMCP then listens on --mcp-host / --mcp-port and serves:
Streamable HTTP:
http://<mcp-host>:<mcp-port><mcp-endpoint>(default path/mcp)SSE:
http://<mcp-host>:<mcp-port>/sse
Aliases for http-stream: sse, streamable-http (same mode; both URLs are available).
Flag / env | Meaning |
|
|
| MCP HTTP port (default 8085 when using HTTP transport) |
| Bind address (default 0.0.0.0) |
| Streamable HTTP path (default |
| Stateless HTTP mode (optional) |
Whistle connection options are unchanged: --host, --port, --username / --password (or -n / -w).
Example (HTTP transport + local Whistle on 8899; MCP listens on 8085 by default):
whistle-mcp --transport http-stream --host 127.0.0.1 --port 8899Use --mcp-port <port> to override the default 8085.
After installation, you can configure Whistle MCP in your MCP JSON configuration file:
{
"mcpServers": {
"whistle-mcp": {
"command": "whistle-mcp",
"args": [
"--host=<whistle server IP address>",
"--port=<whistle server port number>"
]
}
}
}If you start Whistle with basic auth (same flags as the Whistle CLI: w2 start -n <username> -w <password>), pass the same credentials to this MCP server so HTTP requests to Whistle’s API succeed:
{
"mcpServers": {
"whistle-mcp": {
"command": "whistle-mcp",
"args": [
"--host=localhost",
"--port=8899",
"--username=<username>",
"--password=<password>"
]
}
}
}Short options (aligned with w2): -n / -w are equivalent to --username / --password.
whistle-mcp --host localhost --port 8899 -n myuser -w mypassConfiguration Details
host: Whistle server IP address; defaults to
localhostif omittedport: Whistle server port; defaults to
8899if omittedusername (
-n/--username): Basic auth username when Whistle was started with-n; omit if Whistle has no loginpassword (
-w/--password): Basic auth password when Whistle was started with-w; if username is set but password is omitted, an empty password is sent
Configuring MCP JSON in AI Clients
Claude Client: https://modelcontextprotocol.io/quickstart/user
Raycast: Requires MCP plugin installation
Cursor: https://docs.cursor.com/context/model-context-protocol#configuring-mcp-servers
MCP Tools Description
Whistle MCP Server provides the following tools, which can be called via the MCP protocol:
Rule Management
Tool Name | Description | Function |
getRules | Get all rules | List all created rules and their content |
createRule | Create new rule | Create a new rule with the specified name |
updateRule | Update rule content | Modify the content of a specified rule |
renameRule | Rename rule | Rename a rule to a new name |
deleteRule | Delete rule | Delete a rule with the specified name |
enableRule | Enable rule | Enable a rule with the specified name |
disableRule | Disable rule | Disable a rule with the specified name |
setAllRulesState | Set all rules state | Enable or disable all rules at once |
Group Management
Tool Name | Description | Function |
createGroup | Create group | Create a new rule group with the specified name |
renameGroup | Rename group | Rename a rule group to a new name |
deleteGroup | Delete group | Delete a rule group with the specified name |
addRuleToGroup | Add rule to group | Add a specified rule to a specific group |
removeRuleFromGroup | Remove rule from group | Remove a rule from its group to the top level |
Value Management
Tool Name | Description | Function |
getAllValues | Get all values | List all created values and value groups (note: data may be large, consider using getValueList first) |
getValueList | Get value list | Get value list with index and name only (without data field, to avoid large payloads) |
getValue | Get single value | Get full information of a single value by name (including data field) |
createValue | Create new value | Create a new value with the specified name |
updateValue | Update value content | Modify the content of a specified value |
renameValue | Rename value | Rename a value to a new name |
deleteValue | Delete value | Delete a value with the specified name |
createValuesGroup | Create value group | Create a new value group with the specified name |
renameValueGroup | Rename value group | Rename a value group to a new name |
deleteValueGroup | Delete value group | Delete a value group with the specified name |
addValueToGroup | Add value to group | Add a specified value to a specific group |
removeValueFromGroup | Remove value from group | Remove a value from its group to the top level |
Proxy Control
Tool Name | Description | Function |
getWhistleStatus | Get server status | Get the current status information of the Whistle server |
toggleProxy | Enable/disable proxy | Toggle the enabled state of the Whistle proxy |
toggleHttpInterception | Enable/disable HTTP interception | Toggle the enabled state of HTTP request interception |
toggleHttpsInterception | Enable/disable HTTPS interception | Toggle the enabled state of HTTPS request interception |
toggleHttp2 | Enable/disable HTTP2 | Toggle the enabled state of HTTP/2 protocol support |
toggleMultiRuleMode | Enable/disable multi-rule mode | Toggle whether to allow multiple rules to be enabled simultaneously |
Request Management
Tool Name | Description | Function |
getInterceptInfo | Get interception information | Get network request information intercepted by Whistle, with URL filtering and regex support |
replayRequest | Replay request | Resend a specified network request with customizable parameters |
Utility
Tool Name | Description | Function |
getCurrentTimestamp | Get current timestamp | Get the current local timestamp |
Contact Information
Email: gz7gugu@qq.com
Blog: https://7gugu.com
Available Tools
32 toolsaddRuleToGroupC
将规则添加到分组
Inputs: groupName (required), ruleName (required).
addValueToGroupC
将值添加到分组
Inputs: groupName (required), valueName (required).
createGroupC
创建新分组
Inputs: name (required).
createRuleC
创建新规则
Inputs: name (required).
createValueC
创建新的值
Inputs: name (required).
createValuesGroupC
创建新的值分组
Inputs: name (required).
deleteGroupC
删除分组
Inputs: groupName (required).
deleteRuleD
删除规则
Inputs: ruleName (required).
deleteValueD
删除值
Inputs: name (required).
deleteValueGroupC
删除值分组
Inputs: groupName (required).
disableRuleD
禁用规则
Inputs: ruleName (required).
enableRuleD
启用规则
Inputs: ruleName (required).
getAllValuesC
获取所有规则的值
Inputs: no named parameters.
getCurrentTimestampB
获取当前本地时间戳
Inputs: no named parameters.
getInterceptInfoC
获取URL的拦截信息(请求/响应皆以base64编码)
Inputs: count, startTime, url.
getRulesC
获取所有规则&分组
Inputs: no named parameters.
getWhistleStatusB
获取whistle服务器的当前状态
Inputs: no named parameters.
removeRuleFromGroupC
将规则移出分组
Inputs: ruleName (required).
removeValueFromGroupD
将值移出分组
Inputs: valueName (required).
renameGroupC
重命名分组
Inputs: groupName (required), newName (required).
renameRuleC
重命名规则
Inputs: newName (required), ruleName (required).
renameValueC
重命名值
Inputs: name (required), newName (required).
renameValueGroupC
重命名值分组
Inputs: groupName (required), newName (required).
replayRequestA
在whistle中重放捕获的请求(本接口请求后不会直接返回结果, 需要使用getInterceptInfo接口获取结果)
Inputs: url (required), body, headers, method, +1 more.
setAllRulesStateB
控制所有规则的启用状态(启用/禁用)
Inputs: disabled (required).
toggleHttp2C
启用或禁用HTTP/2
Inputs: enabled (required).
toggleHttpInterceptionC
启用或禁用HTTP拦截
Inputs: enabled (required).
toggleHttpsInterceptionC
启用或禁用HTTPS拦截
Inputs: enabled (required).
toggleMultiRuleModeC
启用或禁用多规则模式
Inputs: enabled (required).
toggleProxyC
启用或禁用whistle代理
Inputs: enabled (required).
updateRuleC
更新规则内容
Inputs: ruleName (required), ruleValue (required).
updateValueC
更新值内容
Inputs: name (required), value (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Most tools have distinct purposes targeting specific resources (rules, values, groups) and actions (create, delete, rename, enable/disable), but some overlap exists: 'getAllValues' and 'getRules' both retrieve data, and 'toggle' tools for various interception settings could be confused. Descriptions help clarify, but minor ambiguity remains.
Tool names follow a highly consistent verb_noun pattern throughout, using camelCase uniformly (e.g., createRule, deleteGroup, toggleProxy). There are no deviations in naming conventions, making the set predictable and readable.
With 32 tools, the count is borderline high for a whistle proxy management server. While it covers many operations, it feels heavy and could potentially be streamlined, as some tools (e.g., multiple toggle functions) might be consolidated without losing functionality.
The tool set provides complete CRUD/lifecycle coverage for managing rules, values, and groups, including create, read, update, delete, enable/disable, and renaming. It also covers server status, interception controls, and request replay, leaving no obvious gaps for the whistle proxy domain.
Maintenance
Related MCP Connectors
AI-native mock API server with MCP. Create REST/SOAP mocks from Claude, Cursor, or Windsurf.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Walter Remote MCP Server — AI humanization and detection tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseAqualityFmaintenanceAn 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.2318 npm1MIT
- AlicenseCqualityDmaintenanceMCP server for HotLogin Local API that enables AI agents to manage browser environments, groups, and proxies, and perform browser automation tasks like page interaction and cookie management through a standardized interface.2347 npmMIT
- FlicenseCqualityDmaintenanceMCP server for reading local WeChat data, enabling AI assistants to query chat history, contacts, sessions, and more via MCP tools.209-
- AlicenseBqualityDmaintenanceEnables AI to manage whistle mock rules, values, and inspect network sessions, facilitating API mocking and debugging through natural language.178 npm1MIT