Skip to main content
Glama
Mhdd-24

@mhdd_24/api-scenario-mcp

by Mhdd-24
README.md
# @mhdd_24/api-scenario-mcp

Generate complete multi-step API workflows.

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-scenario-mcp → API Scenario 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-scenario-mcp
```

### Option B — npx

```bash
npx @mhdd_24/api-scenario-mcp
```

### Option C — clone and build

```bash
git clone https://github.com/Mhdd-24/API-Scenario-MCP.git
cd API-Scenario-MCP
npm install
npm run build
node dist/index.js
```

---

## Configure Cursor

Edit `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "apiscen": {
      "command": "npx",
      "args": ["-y", "@mhdd_24/api-scenario-mcp"],
      "env": {
        "PROJECT_ROOT": "..."
      }
    }
  }
}
```

**Local development:**

```json
{
  "command": "node",
  "args": ["/absolute/path/to/API-Scenario-MCP/dist/index.js"]
}
```

---

## Environment variables

| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |

---

## Tools

| Tool | Description |
|------|-------------|
| `apiscen_status` | Health check for API Scenario MCP. |
| `apiscen_generate` | Generate a multi-step API workflow. |
| `apiscen_to_http` | Convert a scenario outline to HTTP steps. |

---

## License

ISC

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: status is a health check, generate creates a workflow, and to_http converts an outline to HTTP steps. There is no meaningful overlap or ambiguity among the three tools.

Naming Consistency4/5

All tools share the consistent apiscen_ prefix and use snake_case, but the naming pattern is slightly uneven: status is a noun, generate is a verb, and to_http is a converter-style phrase. The naming is still predictable and readable overall.

Tool Count5/5

Three tools is an appropriate size for this focused API scenario utility. Each tool supports a distinct part of the workflow without being redundant or bloated.

Completeness4/5

The core pipeline of generating a scenario and converting it to HTTP steps is covered, with a health check for operational use. Minor gaps exist, such as no explicit validation or management tools for scenarios, but they do not undermine the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues