mockserver-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOCKSERVER_HOST | No | MockServer hostname | localhost |
| MOCKSERVER_PORT | No | MockServer port | 1080 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mockserver_create_expectationB | Create a mock HTTP expectation on MockServer. Define request matching criteria and the response to return. |
| mockserver_verifyC | Verify that requests matching criteria were received by MockServer. Returns verification result with match count. |
| mockserver_clearA | Clear expectations and recorded requests from MockServer. Optionally filter by request matcher. |
| mockserver_resetA | Perform a full reset of MockServer, clearing all expectations and recorded requests. |
| mockserver_retrieve_requestsB | Retrieve recorded requests from MockServer. Optionally filter by request matcher. |
| mockserver_statusA | Get MockServer connection status and configuration. Returns host, port, and reachability. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a unique purpose: creating expectations, clearing/resetting (partial vs full), retrieving requests, checking status, and verifying requests. No ambiguity.
All tools follow the pattern 'mockserver_verb' or 'mockserver_verb_noun', using snake_case consistently.
Six tools cover the essential operations for a mock server (create, clear, reset, retrieve, status, verify) without being excessive.
Core functionality is covered, but a tool to list current expectations would provide more complete lifecycle management.