wiremock-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIREMOCK_URL | No | The base URL of the WireMock instance to manage. | http://localhost:8080 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wiremock_statusA | Check the configured WireMock Admin API health and version. |
| mock_listB | List WireMock stub mappings from the configured instance. |
| mock_getA | Get one WireMock stub mapping by ID. |
| mock_createB | Create a WireMock stub mapping, preserving advanced WireMock fields. |
| mock_updateA | Update a WireMock stub mapping by ID, preserving advanced WireMock fields. |
| mock_deleteB | Delete one WireMock stub mapping by ID. |
| mock_resetA | Destructively reset runtime mappings to the configured WireMock backing-store defaults. |
| request_listC | List requests from the WireMock request journal. |
| request_getA | Get one WireMock request journal entry by ID. |
| request_unmatchedA | List request journal entries that matched no WireMock stub. |
| request_countC | Count request journal entries matching a WireMock request pattern. |
| request_clearA | Clear the entire WireMock request journal without deleting mappings. |
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 12 tools
Each tool has a distinctly different purpose: status, mock CRUD, and request journal operations. There is no ambiguity between listing, getting, creating, updating, deleting mocks, or between request list/get/unmatched/count/clear.
Most tools follow a clear resource_action pattern (mock_list, request_get, etc.). The only deviation is wiremock_status, which uses a noun phrase instead of an action verb, but it is still understandable and consistent with the resource-based naming.
12 tools is well-scoped for a WireMock admin server, covering status, mock lifecycle management, and request journal operations without excessive overlap or unnecessary additions.
The tool surface provides full CRUD for stub mappings and a robust set of request journal operations. Minor gaps exist (e.g., no tool for managing global settings or scenarios), but the core WireMock workflows are effectively covered.