@mhdd_24/ai-gateway-mcp
# @mhdd_24/ai-gateway-mcp
MCP server for Manage multiple LLM providers.
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 → ai-gateway-mcp → AI Gateway 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/ai-gateway-mcp
```
### Option B — npx
```bash
npx @mhdd_24/ai-gateway-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/AI-Gateway-MCP.git
cd AI-Gateway-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"aigw": {
"command": "npx",
"args": ["-y", "@mhdd_24/ai-gateway-mcp"],
"env": {
"AI_GATEWAY_URL": "...",
"AI_GATEWAY_TOKEN": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/AI-Gateway-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `AI_GATEWAY_URL` | Gateway URL |
| `AI_GATEWAY_TOKEN` | Token |
---
## Tools
| Tool | Description |
|------|-------------|
| `aigw_status` | Show manage multiple llm providers configuration / health. |
| `aigw_list` | List manage multiple llm providers entities. |
| `aigw_inspect` | Inspect a manage multiple llm providers artifact. |
| `aigw_compare` | Compare two manage multiple llm providers items. |
---
## License
ISC
TDQS
Scored across 4 tools
The four tools are mostly distinct: status reports health/configuration, list enumerates entities, inspect drills into one artifact, and compare contrasts two items. There is mild potential overlap between status and inspect, but descriptions are clear enough for an agent to select the intended operation.
All tool names follow the same aigw_<verb> pattern using simple, consistent verbs. This creates a predictable convention across the entire tool set.
Four tools is a reasonable, focused count for a read-only gateway observability utility. It sits slightly low for a server claiming to 'manage' providers, but the count itself is not excessive or trivial.
The tool surface only supports reading and comparing gateway entities; there are no create, update, delete, or configuration-change operations. Given the 'manage' framing, this is a significant functional gap that would prevent agents from actually managing providers.