@mhdd_24/api-mocking-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root. |
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 |
|---|---|
| apimock_statusB | Health check for API Mocking MCP. |
| apimock_mockC | Generate a mock response for an endpoint. |
| apimock_collectionC | Generate a mock collection JSON. |
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 3 tools
The three tools are clearly distinct: status is a health check, mock generates a single endpoint response, and collection generates a full mock collection. There is no ambiguity in their purposes.
All tool names share the consistent apimock_ prefix and follow a simple noun pattern (status, mock, collection). This makes the toolset predictable and easy to navigate.
Three tools is well-scoped for a simple API mocking utility. Each tool serves a single clear purpose without unnecessary bloat.
The core capabilities of checking service health, generating a single mock, and generating a collection are covered. A minor gap is the lack of configuration options (e.g., status codes or headers), but the surface is otherwise sufficient for basic mocking.