Loading ToolBench
MCP Server for Mockoon - create and manage mock APIs via LLMs
The server provides 17 tools with consistent naming (verb_noun pattern), reasonable descriptions, and Zod-based schemas. However, there are significant gaps in parameter descriptions, output schema documentation, and error handling guidance. Most tools lack recovery instructions when operations fail. The average tool scores 62/100 due to incomplete schema visibility (some param details inferred from type definitions rather than explicit descriptions) and minimal output documentation.
Create a new Mockoon environment
Create a new HTTP route with a single default response. Use create_route_with_responses to add multiple responses in one call.
Create a new HTTP route together with all its responses (default + conditionals) in a single call. The first response in the list is treated as the default unless one has isDefault=true.
Create a new databucket (data template) in a Mockoon environment
Delete a Mockoon environment by UUID. The environment file will be permanently removed from disk.
Delete a route from a Mockoon environment.
Delete a response from a route.
Output schemas are not documented. Tools return text content wrapped in MCP response format, but LLMs cannot predict field structure, making it difficult to chain tools or parse results reliably.
Error handling lacks recovery guidance. When operations fail (e.g., environment not found, server already running), responses are plain text with no actionable next steps or category (retryable/user-fixable/fatal).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 58 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 48 | - | v1 |
Delete a databucket from a Mockoon environment
Return full details of a single route including all responses (status codes, labels, rules, headers, body).
List all local Mockoon environment files. Returns the file path for each environment, which can be passed to start_mock. Searches the default storage directory and any extra directories set via MOCKOON_DATA_DIRS.
List all routes in a Mockoon environment with their UUIDs, method, endpoint and number of responses.
List the UUIDs of all Mockoon environments currently running as mock servers.
List all databuckets (data templates) in a Mockoon environment
Start a Mockoon mock server from a local environment JSON file. Use list_environments to find available file paths. Returns immediately with an error if the server is already running.
Stop a running Mockoon mock server. Returns an error message if no server is running for the given environment.
Update an existing response in a route.
Update the content of an existing databucket
Destructive operations (delete_route, delete_route_response, delete_environment, delete_template) have no dry-run or confirmation mechanism. Agents can accidentally delete resources without reversible safeguards.
Parameter descriptions for complex nested objects (e.g., 'responses' array in create_route_with_responses, 'rules' array, 'headers' array) are minimal. LLMs struggle to construct valid nested structures without detailed field-by-field guidance.
No pagination or result limits documented. list_routes, list_environments, and list_templates could return hundreds of items without documented limits, potentially exhausting LLM context windows.
update_route_response and update_template lack clear descriptions of what fields can be modified and which are required. Parameter descriptions do not explain the scope of the update operation.
No idempotency guarantees documented. Agents may retry start_server or create_route on network failures, risking duplicate resources or state conflicts. Tool descriptions should clarify retry safety.