mockoon-mcp
Related Servers
Alternatives to mockoon-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to configure and manage session-based REST and WebSocket mock servers for application development and testing. It allows for dynamic endpoint setup, request history inspection, and real-time WebSocket communication through natural language commands.8-
- AlicenseBqualityCmaintenanceEnables AI to manage whistle mock rules, values, and inspect network sessions, facilitating API mocking and debugging through natural language.176 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables instant creation of mock API servers from OpenAPI specs or natural language descriptions, with built-in fake data generation, CRUD endpoints, and configurable delays/errors for testing.-

RequestBin MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI coding agents to create webhook bins, inspect and replay HTTP requests, and stand up mock API endpoints directly from the editor.138 npmMIT- AlicenseAqualityCmaintenanceAn MCP server for interacting with MockServer, enabling AI assistants to create mock HTTP expectations, verify requests, clear state, and manage MockServer instances programmatically.643 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMock Server AI - MCP server providing AI-powered tools and automation by MEOK AI Labs7 npmMIT
TDQS
Scored across 21 tools
Each tool targets a specific operation on a distinct resource (environments, routes, responses, templates, servers). Tools like get_route and get_default_response are clearly differentiated by scope. No two tools have overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_environment, list_routes, set_default_response). No mixed conventions or irregular names.
21 tools is well-scoped for an API mocking server. It covers environment, route, response, template, and server lifecycle without excess. Each tool serves a clear purpose.
The tool set covers CRUD for routes, environments, and templates, plus server start/stop and response management. A notable gap is the lack of an update_environment tool, but overall the surface is comprehensive for typical mocking workflows.