Whistle MCP Server

by 7gugu

40 stars
363 downloads
Not rated
GitHub Website

About

Manage local Whistle proxy servers through AI assistants, simplifying network debugging, API testing, and rule management.

Details

Author
7gugu
GitHub stars
40
Downloads
363
Categories
Developer Tools, API, Infrastructure, Other, AI

- 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

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Whistle MCP Server
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

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.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

Manage local Whistle proxy servers through AI assistants, simplifying network debugging, API testing, and rule management.

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.

- 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

Node.js 18.20.0 or newer is required(seeenginesinpackage.json). Older versions are not supported.

To install Whistle MCP Server for Claude Desktop automatically viaSmithery:

npx -y @smithery/cli install @7gugu/whistle-mcp --client claude

You can install Whistle MCP Server globally via npm:

The build output entry isdist/index.js(the same file used by thewhistle-mcpCLI after a global install). You can also point MCP config at it withnodeand the path todist/index.js.

By default the server usesstdio(suitable for local MCP clients such as Cursor).

To exposeStreamable HTTPandSSEon the same process (for remote or HTTP-capable clients), use--transport http-stream. FastMCP then listens on--mcp-host/--mcp-portand serves:

- Streamable HTTP:http://<mcp-host>:<mcp-port><mcp-endpoint>(default path/mcp)
- SSE:http://<mcp-host>:<mcp-port>/sse

Aliases forhttp-stream:sse,streamable-http(same mode; both URLs are available).

Whistleconnection options are unchanged:--host,--port,--username/--password(or-n/-w).

Example (HTTP transport + local Whistle on 8899; MCP listens on8085by default):

whistle-mcp --transport http-stream --host 127.0.0.1 --port 8899

Use--mcp-port <port>to override the default8085.

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 thesamecredentials 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 withw2):-n/-ware equivalent to--username/--password.

whistle-mcp --host localhost --port 8899 -n myuser -w mypass

- host: Whistle server IP address; defaults tolocalhostif omitted
- port: Whistle server port; defaults to8899if omitted
- username(-n/--username): Basic auth username when Whistle was started with-n; omit if Whistle has no login
- password(-w/--password): Basic auth password when Whistle was started with-w; if username is set but password is omitted, an empty password is sent

- Claude Client:https://modelcontextprotocol.io/quickstart/user
- Raycast: Requires MCP plugin installation
- Cursor:
https://docs.cursor.com/context/model-context-protocol#configuring-mcp-servers

Whistle MCP Server provides the following tools, which can be called via the MCP protocol:

- Email:gz7gugu@qq.com
- Blog:
https://7gugu.com

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server for interacting with the Postman API, requiring an API key.

Proxyman MCP allows AI to inspect HTTP traffic, create debugging rules, and control Proxyman - all through natural language conversations.

Adds possibility to work with testing management via MCP

An enhanced Apifox MCP service providing comprehensive API management capabilities for Claude Desktop and Cursor.

This MCP Server accepts swagger/postman documents as input. It then generates API & Load test scenarios, executes the tests and generates the execution report.

A Model Context Protocol (MCP) server for creating, managing, and executing Bruno API testing collections. Supports both .bru and .yml (opencollection) formats with built-in security hardening.

Execute Bruno collections using the Bruno CLI, with support for environment files and detailed test results.

An MCP server exposing Hoverfly as a programmable API simulation tool for AI assistants.

A free public REST API for testing and prototyping, powered by JSONPlaceholder.

Postman for MCP — search 156 servers, inspect tools with schema visualizer, test live

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.