Whistle MCP Server

Created By
7gugua year ago
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.
Overview

What is Whistle MCP Server?

Whistle MCP Server is a proxy management tool that utilizes the Model Context Protocol (MCP) to allow AI assistants to control local Whistle proxy servers, streamlining network debugging, API testing, and proxy rule configuration through natural language.

How to use Whistle MCP Server?

To use Whistle MCP Server, install it globally via npm with the command npm install -g whistle-mcp-tool, and configure it in your MCP JSON configuration file with the Whistle server's IP address and port.

Key features of Whistle MCP Server?

  • Rule Management: Create, update, delete, and manage Whistle rules.
  • Group Management: Organize rules into groups for better management.
  • Value Management: Handle values and their groups effectively.
  • Proxy Control: Enable/disable proxy settings and manage HTTP/HTTPS interception.
  • Request Interception: View and filter intercepted network requests.
  • Request Replay: Replay captured requests with custom parameters.

Use cases of Whistle MCP Server?

  1. Simplifying network debugging tasks.
  2. Automating API testing processes.
  3. Managing complex proxy configurations through AI interaction.

FAQ from Whistle MCP Server?

  • Can Whistle MCP Server manage all types of proxy rules?

Yes, it can manage various proxy rules and configurations.

  • Is there a graphical interface for Whistle MCP Server?

No, it operates through command line and AI interaction.

  • How do I configure the Whistle MCP Server?

Configuration is done through a JSON file specifying the server's IP and port.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
7gugu
Star
7
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago