Mockzilla MCP Server

Mockzilla MCP server. Mock any OpenAPI spec locally with Claude, Cursor, or Gemini CLI.

Remote serverstreamable-httpGo

What is the Mockzilla MCP server?

Most developer tooling work still happens through a UI a human drives. Mockzilla MCP server moves it into the conversation instead. Mockzilla MCP server. Mock any OpenAPI spec locally with Claude, Cursor, or Gemini CLI.

The short version

MCP server for Mockzilla - an open-source API mock server for OpenAPI specifications. Let Claude Code, Claude Desktop, Cursor, or Gemini CLI install Mockzilla, inspect OpenAPI specs, and spin up realistic local mock APIs in seconds. No account required for local use.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

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

  • get_context — list_sims
  • list_catalog_products — deploy_mock_from_catalog
  • deploy_mock_from_spec — deploy_mock_from_url
  • Cursor — Easiest: Settings -> MCP Servers -> Add new MCP server and fill in:

What it needs from you

Configuration is passed through the environment: MOCKZILLA_TOKEN, MOCKZILLA_MCP_URL. 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.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • 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. Mockzilla's toolset — get_context, list_catalog_products, deploy_mock_from_spec and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mockzilla; 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.

Available tools

ToolWhat it does
get_contextlist_sims
list_catalog_productsdeploy_mock_from_catalog
deploy_mock_from_specdeploy_mock_from_url
CursorEasiest: **Settings -> MCP Servers -> Add new MCP server** and fill in:

How to install the Mockzilla MCP server

{
  "mcpServers": {
    "mockzilla": {
      "command": "npx",
      "args": ["-y", "@mockzilla/mcp"],
      "env": {
        "MOCKZILLA_TOKEN": "your-value",
        "MOCKZILLA_MCP_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MOCKZILLA_TOKENCredential the server authenticates with.Yes
MOCKZILLA_MCP_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Mockzilla to get context.
  • Use Mockzilla to list catalog products.
  • Use Mockzilla to deploy mock from spec.

Frequently asked questions

It connects Mockzilla to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (get_context, list_catalog_products, deploy_mock_from_spec, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mockzilla directly.