Whistle MCP Server

Name: Whistle MCP Server
Author: 7gugu

@7gugu

About 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.

#ai #network #proxy #mcp #whistle #whistle-plugin #mcp-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "whistle-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@7gugu/whistle-mcp",
        "--client",
        "claude"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Whistle MCP Server?

Whistle MCP Server is a Whistle proxy management tool based on the Model Context Protocol (MCP) that allows AI assistants to directly operate and control local Whistle proxy servers. It simplifies network debugging, API testing, and proxy rule management by enabling users to manage rules, groups, values, monitor network requests, and replay/modify requests through natural language interaction with AI.

How to use Whistle MCP Server?

Install via npm install -g whistle-mcp-tool or through Smithery. Configure the server in your MCP client’s JSON config with the Whistle server host, port, and optional authentication credentials. By default the server uses stdio transport; pass --transport http-stream to expose Streamable HTTP and SSE endpoints.

Key features of Whistle MCP Server

Rule management: create, update, rename, delete, enable/disable rules
Group management: create, rename, delete groups, add/remove rules
Value management: create, update, rename, delete values and value groups
Proxy control: enable/disable proxy, HTTP/HTTPS interception, HTTP/2 protocol
Request interception and replay with URL filtering and custom parameters
Multi-rule mode: toggle enabling multiple rules simultaneously

Use cases of Whistle MCP Server

Debugging network traffic by managing Whistle rules via natural language
Automating proxy configuration changes during API testing sessions
Quickly replaying and modifying captured requests for regression testing
Enabling/disabling proxy features and interception modes without manual UI use
Organizing rules and values into groups for complex proxy workflows

FAQ from Whistle MCP Server

What are the runtime requirements for Whistle MCP Server?

Node.js 18.20.0 or newer is required. Older versions are not supported.

How do I configure the transport mode?

By default the server uses the stdio transport. To expose Streamable HTTP and SSE, pass --transport http-stream (also aliased as sse or streamable-http). The MCP HTTP port defaults to 8085 and the endpoint defaults to /mcp.

How do I pass authentication credentials to the Whistle proxy?

Use the --username/--password flags (or their short forms -n/-w) with the same credentials used when starting Whistle with w2 start -n <username> -w <password>. If Whistle has no login, omit these flags.

Is there a limit I should be aware of when fetching all values?

The getAllValues tool may return a large payload because it includes data fields. Prefer using getValueList (index and name only) to avoid large responses.