MockServer

Overview

MockServer is a self-hosted tool for mocking and proxying HTTP, HTTPS and gRPC services, with request verification for deterministic testing. It suits teams that need to simulate more than basic HTTP APIs, including messaging brokers and identity providers. Its breadth is a strong fit for complex test environments, though its deployment and security choices call for deliberate setup.

Key features

MockServer combines mock responses, proxying and request verification, making it useful both for isolated tests and for checking how services behave against real traffic. Teams can generate mocks and validate traffic from OpenAPI or Swagger contracts, or import recorded sessions from browser HAR files and Postman collections. That gives existing API definitions and examples a direct role in test setup.

Protocol support covers HTTP/1.1, HTTP/2, HTTPS and SOCKS, plus experimental HTTP/3 on a separate UDP port. Beyond HTTP, it can mock gRPC services, AsyncAPI brokers such as Kafka, MQTT and AMQP, and OAuth2/OIDC providers. Chaos testing can inject latency, errors, dropped connections and malformed responses into mocked or proxied HTTP, gRPC and TCP traffic—a meaningful advantage when tests need to exercise failure handling, not just successful responses.

Deployment options include Docker, an executable JAR, Helm/Kubernetes, Testcontainers, Homebrew and a JVM-less binary bundle. Official clients cover Java, JavaScript, Python, Ruby, Go, .NET, Rust and PHP, alongside a CLI and REST API. A web dashboard surfaces live logs, expectations and recorded traffic; Prometheus metrics and OpenTelemetry tracing add visibility in shared environments. Each instance also exposes an MCP server at /mockserver/mcp for assistants including Claude Code, Cursor, Windsurf, Cline and OpenCode.

Control-plane requests can use mutual TLS, JWT or both, with OIDC scopes or groups mapped to roles. Template protections are enabled by default: Velocity class loading is disabled, and JavaScript templates cannot resolve Java classes unless explicitly allowed. But /mockserver/status and /mockserver/ready remain reachable without authentication or authorization. Deployments should account for those probes when deciding what can be exposed.

Pricing

MockServer is free and open source: the Free and open-source plan costs nothing and is self-hosted, with no SaaS account. That makes it suitable for teams willing to run and manage their own instance. There is no paid tier described, so organizations seeking a hosted service should consider another option.

Platforms

MockServer is listed for API, Linux, macOS, self-hosted, web and Windows use. Its deployment choices span local development and container or Kubernetes environments, while language clients let teams work from several common stacks. This flexibility is useful for mixed environments, but self-hosting means the team remains responsible for operating the service.

Who it's for

MockServer is best for developers and QA teams building contract tests, integration tests or service virtualization environments that need protocol breadth, traffic replay or controlled failure injection. It is also a strong candidate where mock behavior must be managed across languages or observed through shared dashboards and telemetry. For a small project that only needs a few hosted HTTP mocks, its self-hosted deployment model may be more operational work than necessary.

Pros and cons

• Pros: Broad protocol and service coverage spans HTTP variants, gRPC, messaging brokers and OAuth2/OIDC providers, reducing the need for separate mock tools.
• Pros: Contract-based generation, traffic imports and request verification support realistic, repeatable tests from existing specifications and recorded sessions.
• Pros: Free, open-source self-hosting and multiple deployment methods give teams control over where the tool runs.
• Cons: Self-hosting requires deployment and operational ownership rather than offering a managed SaaS option.
• Cons: The unauthenticated health probes need attention in exposed deployments, despite the available control-plane authentication and authorization options.
• Cons: HTTP/3 support is experimental and uses a separate UDP port, so it is not equivalent to the more established protocol options.

Alternatives

Microcks is another free, open-source option with a self-hosted distribution and broad platform availability; consider it if a community-driven CNCF Incubating project is a priority. WireMock offers a free forever plan capped at 1,000 calls per month, one user, three mock APIs and 10 requests per second, making it a clearer fit for a small, quota-bounded setup. WireMock also has a free forever option with those same core caps and community support.

Mockzilla has a free plan limited to 1K requests per month, 5 requests per second, one simulation and 10 MB of transfer; its Hobby plan is $10 a month. Mockoon is another freemium alternative with a free trial. Mockfly offers a Starter plan at no cost, capped at 500 requests per day, one project, four endpoints and two responses per endpoint; its Pro plan costs €15 a month.

Mockttp is free, with a Hobbyist plan for basic traffic viewing and rewriting, manual breakpoints and a built-in HTTP client; choose it when traffic inspection and rewriting are the priority. Mock Service Worker is an open-source, free-to-try alternative.

For more options, browse API Mocking Tools, Service Virtualization Software, Integration Testing Tools or API Design Tools.

Verdict

Choose MockServer if your team needs self-hosted service virtualization that reaches beyond HTTP mocks into contracts, messaging, identity and failure simulation. Its strongest case is the breadth of testing behavior in one free tool; its main drawback is the operational responsibility of self-hosting, compounded by health probes that are always unauthenticated. Teams wanting managed hosting or a tightly limited, simple mock service should look elsewhere.