@mhdd_24/api-mocking-mcp
# @mhdd_24/api-mocking-mcp
Create mock endpoints and responses.
Same architecture as [@mhdd_24/sublime-mcp](https://github.com/Mhdd-24/Sublime-MCP).
**Full documentation:** [docs/WIKI.md](./docs/WIKI.md)
---
## How it works (30 seconds)
```
You (chat) → MCP client → api-mocking-mcp → API Mocking APIs / CLIs / local tools
```
---
## Prerequisites
| Requirement | Notes |
|-------------|--------|
| **Node.js 18+** | ESM TypeScript MCP server |
| **Credentials / CLIs** | See environment variables below |
---
## Install
### Option A — npm (after publish)
```bash
npm install -g @mhdd_24/api-mocking-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-mocking-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/API-Mocking-MCP.git
cd API-Mocking-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"apimock": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-mocking-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/API-Mocking-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |
---
## Tools
| Tool | Description |
|------|-------------|
| `apimock_status` | Health check for API Mocking MCP. |
| `apimock_mock` | Generate a mock response for an endpoint. |
| `apimock_collection` | Generate a mock collection JSON. |
---
## License
ISC
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.