MCP server
GunSpec MCP server
Connect Claude, Cursor, VS Code or any other Model Context Protocol client to the catalog. The hosted server provides 44 read-only tools (39 single-call tools and 5 workflows) and uses your existing API key and plan.
Server URL
https://mcp.gunspec.io- Server
- SDK
- Single-call tools
- 39
- Workflows
- 5
- Uptime, 30 days
At a glance
The information a client needs to connect.
| Property | Value |
|---|---|
| Endpoint | https://mcp.gunspec.io |
| Transport | Streamable HTTP. Every message is a POST to the endpoint. |
| Protocol | MCP 2026-07-28. Earlier 2025 revisions are supported through a stateless fallback. |
| Authentication | Your GunSpec API key in the X-API-Key header, or as Authorization: Bearer. |
| Tools | 44 read-only tools: 39 single-call tools and 5 workflows. |
| Sessions | None. Each request is independent, so reconnecting does not lose any state. |
| MCP Registry | Listed as io.gunspec/mcp in the official MCP Registry. View the listing, or see installing from the registry. |
| Limits | Your plan's API quota and rate limit, plus a separate daily allowance for MCP calls: Explorer 20, Builder 500, Studio 2,500, Enterprise 10,000 calls a day. See Usage and limits. |
How it works
The server is a thin layer over the public API. It is not a separate API.
- Your client sends a tool call with your key. The server converts it into a GunSpec API request authenticated with that key.
- The API processes the request exactly as it processes a direct request, with the same plan gates and rate limit. MCP calls also have their own daily allowance, which is lower than the plan allowance.
- The tools are the same tools the official TypeScript SDK provides, so each tool always matches the SDK method it calls.
- When the API refuses a call, the refusal is returned as a tool result that the model can read and explain. The connection remains open.