$ loading_
Programmatically manage MockServer mocks, request verification, and state cleanup via MCP.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mockserver-mcp" yet — see the docs or source repo.
Create a MockServer HTTP expectation: when a GET request is sent to /users/42, return status 200 with JSON {"id":42,"name":"Alice"}.A matching mock expectation is created in MockServer for later test calls.
Verify whether MockServer has received any POST /orders requests and report the result.
Returns the verification result indicating whether the request was recorded by MockServer.
Clear current MockServer expectations and recorded requests to reset the test environment.
MockServer state is cleared so the next test run starts fresh.
Developers can use it to create HTTP mock expectations in MockServer when backend services are unavailable or real APIs should not be called.
During integration or automated testing, teams can verify whether specific requests actually reached MockServer to confirm expected system behavior.
Between test runs, it can clear MockServer state so old expectations or recorded requests do not affect new results.
This is an MCP tool for interacting with MockServer. It supports programmatic creation of HTTP mock expectations, request verification, state cleanup, and MockServer instance management.
Based on the description, it mainly supports four actions: creating mock HTTP expectations, verifying requests, clearing state, and managing MockServer instances.
It is designed to interact with MockServer, so it typically requires a MockServer environment. The provided materials do not specify installation, configuration, or connection details; see the source repository.
Mock, replay, verify, and chaos-test APIs and LLM dependencies via MCP.
Run a lightweight local MCP mock server for predictable testing.
Test gateway connectivity, identity propagation, and mock MCP tools.
Simulate dynamic actions for any query with persistent state across sessions.
Build a mock MCP HTTP server for integration, health checks, and tool testing.
Start deterministic mock MCP servers from JSON fixtures for testing.