Whistle MCP Server

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. That is what the whistle mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• 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

Getting it running

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 2 tools. What each one is for:

• Requirements — The Requirements tool exposed by this server
• Utility — The Utility tool exposed by this server

What it needs from you

Configuration is passed through the environment: FASTMCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Node.js 18.20.0 or newer is required (see engines in package.json). Older versions are not supported.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Whistle MCP's toolset — Requirements, Utility — is a fair guide to whether it matches your workflow. It is maintained by 7gugu; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.