Hoverfly MCP Server

A Spring Boot-based Model Context Protocol (MCP) server that exposes Hoverfly as a programmable tool for AI assistants like Cursor, Claude Desktop, GitHub Copilot, or any other assistant. The hoverfly mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 13 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• get_hoverfly_status — Checks if Hoverfly is running
• start_hoverfly_web_server — Starts Hoverfly in simulate mode as a web server. By default, it will auto-load the most recent simulation from /opt/hoverfly-mcp/simulation-data if
• stop_hoverfly_server — Stops Hoverfly and clears mocks
• fetch_hoverfly_version — Returns Hoverfly version
• list_hoverfly_mocks — Lists all active mock APIs (request-response pairs)
• add_hoverfly_mock — Adds a mock API using a JSON RequestResponsePair definition
• clear_hoverfly_mocks — Removes all existing mock APIs
• show_hoverfly_endpoints_info — Returns key Hoverfly endpoints and example usage
• get_hoverfly_documentation — Returns Hoverfly documentation for a specific topic
• suggest_hoverfly_matchers — Suggests matcher options for a given request-response pair JSON
• get_hoverfly_debug_logs — Fetches recent Hoverfly logs for debugging (limit is optional)
• download_hoverfly_simulation — Downloads current simulation to /opt/hoverfly-mcp/simulation-data (persistent simulation directory)

Configuration

• Java 17 - Maven 3.6+

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of monitoring and observability 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. Hoverfly's toolset — get_hoverfly_status, start_hoverfly_web_server, stop_hoverfly_server and 10 more — is a fair guide to whether it matches your workflow. It is maintained by kapishmalik; 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.

Caveats

• 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.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hoverfly.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the hoverfly mcp server does with a few real requests.