mcp-forgelisted

# mcp-forge — turn any API into a Claude-callable tool surface ## When to use this skill Trigger when the user wants Claude (or any MCP client) to be able to *invoke* a remote API as native tools. Strong signals: - Mentions of "MCP server", "MCP for X", "wrap API as MCP", "Model Context Protocol" - A pasted OpenAPI/Swagger spec, Postman collection, or list of REST endpoints - A documentation URL where you can read the API surface (Stripe, GitHub, internal services) Do *not* trigger for: pure client-side API calls, simple `fetch` wrappers, or when an existing first-party MCP already covers the surface (check the MCP registry first — see step 1 below). ## The output contract A working MCP server, in a single directory, that: 1. **Builds clean** — `npm install && npm run build` succeeds with zero warnings. 2. **Connects** — registers without error against `claude mcp add` and answers `tools/list`. 3. **Is safe** — secrets read from env, never logged; rate limits and 5xx retried with exponential backoff and jitter; PII redacted from error messages. 4. **Is typed** — every tool's `inputSchema` is a real Zod schema, not a hand-written JSON blob. Response types are inferred. 5. **Ships with an install path** — README has copy-paste install for Claude Code, plus the bare `claude mcp add` command. ## Workflow ### 1 — Reconnaissance (do not skip) Before writing code: - Ask the user for the API source. Accept: OpenAPI URL/file, docs URL, raw endpoint list, or a Postman export