Run MockServer with Docker in seconds:
docker run -d --rm -p 1080:1080 mockserver/mockserverFor more configuration options see the Docker documentation.
For usage guide please see: www.mock-server.com
Architecture, code structure, infrastructure, and operations documentation is available in the docs/ directory.
MockServer includes a built-in MCP server for AI coding assistant integration at /mockserver/mcp. See llms.txt and AI Integration docs.
Please see: Change Log
| Discussions |  |
| Feature Requests | |
| Issues / Bugs | |
| Roadmap | |
| Security | |
MockServer requires Java 11+. Java 11 is the minimum supported version to maximise compatibility — approximately 23% of Java projects still run on Java 11.
Security Note: MockServer is a development and testing tool only. See SECURITY.md for important security considerations.
Maven Central contains the following MockServer artifacts under the org.mock-server groupId. Every artifact ships in two forms — -no-dependencies (shaded, zero transitive deps, recommended) and the plain form (transitive deps declared in the POM, for the rare case where you need to override versions yourself).
Server:
- mockserver-netty-no-dependencies / mockserver-netty — Netty-based HTTP(S) mock + proxy server (embed in tests or run standalone)
- mockserver-war — deployable WAR for hosting MockServer in a servlet container (mock mode)
- mockserver-proxy-war — deployable WAR for hosting MockServer in a servlet container (proxy mode)
Java client:
- mockserver-client-java-no-dependencies / mockserver-client-java — Java client for the MockServer REST API
Test framework integrations:
- mockserver-junit-rule-no-dependencies / mockserver-junit-rule — JUnit 4
@Rule - mockserver-junit-jupiter-no-dependencies / mockserver-junit-jupiter — JUnit 5 extension (
@MockServerSettings,@MockServerTest) - mockserver-spring-test-listener-no-dependencies / mockserver-spring-test-listener — Spring
TestExecutionListener - mockserver-integration-testing-no-dependencies / mockserver-integration-testing — shared integration-test helpers
Build-tool plugin:
- mockserver-maven-plugin — Maven plugin to start, stop, and fork MockServer during the build lifecycle
Tip: The
-no-dependenciesartifacts bundle all dependencies into a single JAR with packages relocated undershaded_package.*, so they declare zero transitive dependencies. This avoids classpath conflicts with versions of Netty / Jackson / Guava / Bouncy Castle that your project already uses, and it removes the noise from CVE scanners flagging unused transitive dependencies. See the Maven Central page for full coordinates, snapshot repository setup, and the executablejar-with-dependenciesform for command-line use.
6.0.0 breaking change: the
<classifier>shaded</classifier>form has been removed. Replacemockserver-netty:<version>:shadedwithmockserver-netty-no-dependencies:<version>(and likewise for the other shaded artifacts). The replacement produces the same shaded bytes; only the coordinates change.
SNAPSHOT builds are published to the Sonatype Central Portal snapshot repository at https://central.sonatype.com/repository/maven-snapshots/org/mock-server/.
NPM Registry contains the following module:
- mockserver-node - a Node.js module and Grunt plugin to start and stop MockServer
- mockserver-client-node - a Node.js client for both the MockServer and the proxy
Docker Hub contains the following artifacts:
- MockServer Docker Container - a Docker container containing the Netty MockServer and proxy
- MockServer Helm Chart - a Helm Chart that installs MockServer to a Kubernetes cluster (latest: 5.15.0). See the Install MockServer Helm Chart guide for all available versions and configuration options.
- mockserver-client-java
- a Java client for both the MockServer and the proxy (use the
-no-dependenciesartifact to avoid transitive dependencies) - mockserver-client-node
- a Node.js and browser client for both the MockServer and the proxy
- mockserver-client-python - a Python client for both the MockServer and the proxy
- mockserver-client-ruby
- a Ruby client for both the MockServer and the proxy
- MockServer Browser Admin - a React + TypeScript SPA for managing MockServer expectations via a web UI
If you have any problems, please check the project issues and avoid opening issues that have already been fixed. When you open an issue please provide the following information:
- MockServer version (i.e. 5.15.0)
- How your running the MockServer (i.e maven plugin, docker, etc)
- MockServer log output, at INFO level (or higher)
- What the error is
- What you are trying to do
Pull requests are, of course, very welcome! Please read our contributing to the project guide first. Then head over to the open issues to see what we need help with. Make sure you let us know if you intend to work on something. Also check out the project roadmap to see what is already in the backlog.
Feature requests are submitted to GitHub issues and tracked on the project roadmap.