Mockd

What getmockd/mockd does

The getmockd/mockd MCP server lets MCP-compatible AI clients operate mockd, a local multi-protocol API mock server. It is intended for development and testing scenarios where an agent needs to define endpoints, provide realistic responses, maintain test data, or check whether a client behaves correctly against an API contract.

mockd supports HTTP and HTTPS, GraphQL, gRPC, WebSocket, MQTT, server-sent events, and SOAP. It runs as a local executable and can create mocks for services that are unavailable, expensive, unstable, or still under development. Stateful CRUD resources can model records and operations such as create, list, retrieve, update, and delete.

How it works

The MCP entry point is started by running mockd mcp. An MCP client launches that command as a local process, then exposes the server’s tools to an AI agent. The agent can manage mock definitions and supporting data through MCP rather than issuing individual CLI commands.

The server also supports imported API descriptions and captured request formats. Supported imports include OpenAPI, Postman, HAR, WireMock, cURL, Mockoon, and WSDL. These definitions can be used to create a digital twin of an existing API, including examples such as Stripe, Twilio, or OpenAI-compatible testing configurations described by the project.

Setup and configuration

Add the following server entry to an MCP client configuration, adapting the format to the client where necessary:

{
  "mcpServers": {
    "mockd": {
      "command": "mockd",
      "args": ["mcp"]
    }
  }
}

The mockd executable must be installed and available to the client process. The project documents installation through a shell installer, Homebrew, Docker, Go, and pre-built binaries for Linux, macOS, and Windows. The repository does not document any environment variables required by the MCP process.

Tools and capabilities

The getmockd/mockd MCP server includes 18 tools covering:

• Mock creation, modification, listing, and removal.
• Stateful resources for CRUD-style test data.
• Import and export operations for supported API formats.
• Chaos behavior and fault injection, including delays and errors.
• Request-log inspection and contract verification.
• Workspace management.
• Protocol-specific mocks for the seven supported protocol families.

The underlying mockd runtime also provides deterministic seeded responses, circuit-breaker behavior, bandwidth throttling, an administrative REST API, a web dashboard, and cloud tunnel sharing according to the project’s capability tables. These runtime features should not be assumed to be separate MCP tools unless exposed by the configured tool set.

Limitations and notes

This is a local MCP arrangement: the client starts the mockd command on the same environment where the executable is installed. The README names Claude Desktop, Cursor, and Windsurf, and states that the server works with MCP-compatible editors.

The repository describes mockd as self-hostable and licensed under Apache 2.0. Protocol support and import support belong to the mockd runtime; an agent’s ability to use a particular operation depends on the tools exposed by the running MCP version.