@mhdd_24/api-auth-mcp
# @mhdd_24/api-auth-mcp
Test API authentication and authorization.
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-auth-mcp → API Auth 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-auth-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-auth-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/API-Auth-MCP.git
cd API-Auth-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"apiauth": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-auth-mcp"],
"env": {
"API_AUTH_TOKEN": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/API-Auth-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `API_AUTH_TOKEN` | Optional bearer token |
---
## Tools
| Tool | Description |
|------|-------------|
| `apiauth_status` | Show API auth test configuration. |
| `apiauth_probe` | Call URL with/without Authorization header. |
| `apiauth_matrix` | Suggest auth test matrix for roles. |
---
## License
ISC
TDQS
Scored across 3 tools
Each tool has a distinct role: status shows the current auth configuration, probe actually executes a request, and matrix suggests test scenarios. There is minor potential confusion between status and matrix, but the descriptions separate present-state reporting from future/test-plan generation well enough.
All tool names follow a consistent apiauth_ prefix and lowercase snake_case style. Although the names are not strictly verb_noun, the pattern is uniform and predictable across the entire set.
Three tools is well-scoped for the narrow purpose of API auth testing. Each tool covers a meaningful and distinct aspect without unnecessary redundancy.
The set covers inspecting configuration, executing probes, and generating a test matrix, which forms a coherent workflow. A minor gap is the lack of a tool for updating or persisting auth configuration, but the current surface is sufficient for advisory and testing tasks.