mock-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOCK_MCP | No | Enables the test runner hook so intercepted requests are routed to mock-mcp. | unset |
| MOCK_MCP_CACHE_DIR | No | Override the cache directory for daemon files (registry, socket, lock). | ~/.cache/mock-mcp |
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 |
|---|---|
| get_statusA | Get the current status of the mock-mcp daemon, including active test runs and pending batches. |
| list_runsB | List all active test runs connected to the daemon. |
| claim_next_batchA | Claim the next pending mock batch for processing. This acquires a lease on the batch. You MUST call this before provide_batch_mock_data. The batch will be locked for 30 seconds (configurable via leaseMs). If you don't provide mock data within the lease time, the batch will be released for another adapter to claim. |
| get_batchA | Get details of a specific batch by ID (read-only, does not claim). |
| provide_batch_mock_dataA | Provide mock response data for a claimed batch. You MUST first call claim_next_batch to get the batchId and claimToken. The mocks array must contain exactly one mock for each request in the batch. |
| release_batchA | Release a claimed batch without providing mock data. Use this if you cannot generate appropriate mocks. |
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 clearly distinct purpose: claiming, getting details, providing data, releasing, and status queries. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making the API predictable and easy to navigate.
With 6 tools covering the core workflow (claim, provide, release, inspect), the count is well-scoped and each tool serves a necessary function.
The tool set fully covers the mock batch lifecycle: claiming, providing data, releasing, plus status and batch details. No obvious gaps for the stated purpose.