What it does
The server exposes tools for working with James Bloom's MockServer from an MCP-compatible AI assistant. An assistant can create HTTP mock expectations with request matching and configurable responses, verify how many matching requests were received, retrieve recorded requests, clear specific or all expectations, perform a full reset, and check connection status.
The publisher describes it as a way to start building and testing a frontend or integration before the backend is ready. A shared team MockServer can be used by changing the host setting.
Running it requires an existing MockServer instance, which the server connects to through the MOCKSERVER_HOST and MOCKSERVER_PORT variables (defaults are localhost and 1080). It is installed with npx and added to the configuration file of an MCP client such as Claude Desktop, Kiro or Cursor.
Limitations and requirements
Requires a running MockServer instance and a Node.js runtime. The MOCKSERVER_HOST and MOCKSERVER_PORT settings must point to that instance.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.Akkshay10/MCPClientMock
MCP server for James Bloom MockServer - create expectations, verify requests, and manage mock state
v1.0.2As shown on registry.modelcontextprotocol.io when we last read it