@mhdd_24/api-auth-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@mhdd_24/api-auth-mcp Probe https://api.example.com/users with and without Authorization header"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@mhdd_24/api-auth-mcp
Test API authentication and authorization.
Same architecture as @mhdd_24/sublime-mcp.
Full documentation: docs/WIKI.md
How it works (30 seconds)
You (chat) → MCP client → api-auth-mcp → API Auth APIs / CLIs / local toolsRelated MCP server: api-testing-agent
Prerequisites
Requirement | Notes |
Node.js 18+ | ESM TypeScript MCP server |
Credentials / CLIs | See environment variables below |
Install
Option A — npm (after publish)
npm install -g @mhdd_24/api-auth-mcpOption B — npx
npx @mhdd_24/api-auth-mcpOption C — clone and build
git clone https://github.com/Mhdd-24/API-Auth-MCP.git
cd API-Auth-MCP
npm install
npm run build
node dist/index.jsConfigure Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"apiauth": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-auth-mcp"],
"env": {
"API_AUTH_TOKEN": "..."
}
}
}
}Local development:
{
"command": "node",
"args": ["/absolute/path/to/API-Auth-MCP/dist/index.js"]
}Environment variables
Variable | Description |
| Optional bearer token |
Tools
Tool | Description |
| Show API auth test configuration. |
| Call URL with/without Authorization header. |
| Suggest auth test matrix for roles. |
License
ISC
Available Tools
3 toolsapiauth_matrixC
Suggest auth test matrix for roles.
Inputs: roles (required), endpoint (required).
apiauth_probeB
Call URL with/without Authorization header.
Inputs: url (required), token.
apiauth_statusB
Show API auth test configuration.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Free AI test helpers: injection inputs, OWASP mapping, release plans, response and tool-call packs.
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Authorized security scans, evidence, fix prompts and retests for AI-built web apps.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables conversational API testing via MCP, allowing users to make HTTP requests, decode JWT tokens, and validate JSON schemas through natural language.-
- FlicenseNot gradedqualityDmaintenanceEnables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.1-
- AlicenseNot gradedqualityCmaintenanceEnables end-to-end testing of OAuth authorization for an MCP server, exposing scoped tools like whoami and echo over streamable HTTP.ISC
- AlicenseBqualityCmaintenanceEnables scanning OpenAPI specifications for security gaps and generating security test checklists for APIs.314 npmISC