Mockzilla MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 193 installs a week from npm. Last commit 10 Oct 2026.
Mock OpenAPI specs locally, or log in to deploy hosted mocks on mockzilla.org from your MCP client.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, args, { stdio: "ignore", detached: true });
const managed = path.join(MOCKS_SERVICES_DIR, service);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mockzilla-mcp -- npx -y @mockzilla/mcp
{
"mcpServers": {
"mockzilla-mcp": {
"command": "npx",
"args": [
"-y",
"@mockzilla/mcp"
]
}
}
}
[mcp_servers.mockzilla-mcp]
command = "npx"
args = ["-y", "@mockzilla/mcp"]
{
"mcpServers": {
"mockzilla-mcp": {
"command": "npx",
"args": [
"-y",
"@mockzilla/mcp"
]
}
}
}
{
"servers": {
"mockzilla-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mockzilla/mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
MOCKZILLA_TOKEN (API key (mz_*) to use instead of logging in with the login tool, for machines without a browser. Leave unset to log in from your agent), MOCKZILLA_MCP_URL (Override the hosted MCP endpoint (staging or local development). Defaults to https://platform.mockzilla.org/mcp), MOCKZILLA_MANAGED_PORT (Preferred port for the local managed mock server. Defaults to 2200; falls back to a kernel-picked port if busy).
Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
Deploy repositories or local folders to private Pocketnook URLs from any MCP client.
Deploy localhost to a private, authenticated link from your AI coding agent.
Hosting for AI agents: your AI client deploys Docker apps to live HTTPS URLs over MCP.
Deploy local apps, add managed Postgres, and inspect logs from your AI coding agent.
Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.
Answers built from our own checks of this server.