Skip to main content
MockServer lets you mock any system you integrate with over HTTP or HTTPS, and proxy live traffic for inspection and debugging. Use it in tests, local development, or CI pipelines to isolate dependencies and control responses.

Quick Start

Get MockServer running and mock your first request in under 5 minutes.

Running MockServer

Deploy via Docker, Helm, Maven, npm, or as a standalone JAR.

Creating Expectations

Define request matchers and response actions to control what MockServer returns.

REST API Reference

Explore the full REST API for managing expectations, verification, and state.

​
How MockServer works

MockServer acts as a controllable HTTP server. You configure it with expectations — rules that match incoming requests and define what response to return. You can then verify which requests were received after your tests run.
1

Start MockServer

Run MockServer via Docker, as a JAR, or embedded in your test framework.
2

Set up expectations

Use a client library or the REST API to define how MockServer should respond to requests.
3

Run your tests

Point your application at MockServer. It intercepts requests and returns your configured responses.
4

Verify requests

Assert that your application made the expected calls — method, path, headers, body, and more.

​
Explore by use case

OpenAPI Mocking

Auto-generate expectations from an OpenAPI v3 specification.

Response Templates

Return dynamic responses using Mustache, Velocity, or JavaScript templates.

Proxy & Record

Proxy live traffic, record requests and responses, then replay them.

Client SDKs

Use the Java, JavaScript, or Ruby client to control MockServer programmatically.