home / mcp / whistle mcp server
A Whistle proxy management tool based on Model Context Protocol that allows AI assistants to directly control local Whistle proxy servers, simplifying network debugging, API testing, and proxy rule configuration through natural language interaction.
Configuration
View docs{
"mcpServers": {
"7gugu-whistle-mcp": {
"command": "whistle-mcp",
"args": [
"--host=<whistle server IP address>",
"--port=<whistle server port number>"
]
}
}
}Whistle MCP Server lets you manage a local Whistle proxy via the Model Context Protocol (MCP). You can control rules, groups, values, monitor and replay requests, and toggle proxy behavior through an AI-enabled interface, making network debugging and API testing faster and more precise.
You connect an MCP client to the Whistle MCP Server to perform operations like creating rules, organizing them into groups, managing values, and controlling the proxy. Use the client’s MCP features to list, create, update, rename, enable/disable, and replay rules and requests. You can filter intercepted requests, replay them with altered parameters, and switch between single-rule and multi-rule modes as needed.
Prerequisites: ensure you have Node.js and npm installed on your system.
Option 1 Install via Smithery for Claude Desktop automatic setup.
npx -y @smithery/cli install @7gugu/whistle-mcp --client claudeOption 2 Manual installation: install the MCP tool globally with npm.
npm install -g whistle-mcp-toolAfter you have installed Whistle MCP Server, configure it in your MCP setup. The following JSON snippet defines how to start the Whistle MCP server locally. Replace host and port with your actual Whistle server address and port.
{
"mcpServers": {
"whistle-mcp": {
"command": "whistle-mcp",
"args": [
"--host=<whistle server IP address>",
"--port=<whistle server port number>"
]
}
}
}Host defaults to localhost if not specified. Port defaults to 8899 if not specified.
If you encounter connectivity issues, verify that the Whistle MCP Server process is running, and that the host/port you configured match the Whistle server’s listening address. Check for firewall blocks and verify that MCP client settings point to the correct host and port.
List all created rules and their content.
Create a new rule with the specified name.
Modify the content of a specified rule.
Rename a rule to a new name.
Delete a rule by name.
Enable a rule by name.
Disable a rule by name.
Disable all created rules at once.
Create a new rule group with the specified name.
Rename a rule group.
Delete a rule group by name.
Move a specified rule to a specific group.
Move a rule out of its group to the top level.
List all created values and value groups.
Create a new value with the specified name.
Modify the content of a specified value.
Rename a value.
Delete a value by name.
Create a new value group.
Rename a value group.
Delete a value group by name.
Move a value to a specific group.
Move a value out of its group to the top level.
Get the current status information of the Whistle server.
Enable/disable the Whistle proxy.
Enable/disable HTTPS interception.
Enable/disable HTTP/2 protocol support.
Enable/disable multi-rule mode.
Get intercepted network request information with filtering support.
Replay a specified network request with customizable parameters.