Turn API documentation (a docs URL, OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, an HTML page or pasted text) into an MCP server: an evidence-only entry, tested and live-verified, served by platform-mcp-hub. MCP server, CLI and Claude Code plugin.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"api-to-mcp-forge","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# api-to-mcp Turn an API's documentation into a working MCP server. Give it a docs URL, an OpenAPI/Swagger file, a Postman collection, RAML, WSDL, a GraphQL endpoint, an HTML reference page or pasted text; the model reads it and writes an **evidence-only entry** (every tool cites the documented endpoint), and api-to-mcp runs the deterministic steps: lint, run config, contract tests, a stdio smoke test in Python and TypeScript, and a live verification against the real API. The result is not generated code. It is one JSON entry describing the API, which the runtime serves as an MCP server: `api-to-mcp serve <category> <id>` (or `platform-mcp-hub serve --entry my_entry.json`). By default the entry is **generic**: its tools are the API's own operations (from an OpenAPI/Swagger description, `draft_entry` writes them), and the answer is passed through, with optional field selection. Any HTTP API qualifies. ## Three ways to use it - **Claude Code plugin** (skill `/api-to-mcp`, the `api-to-mcp` agent and the MCP server together): ```bash claude plugin marketplace add tonyyang0504/api-to-mcp claude plugin install api-to-mcp@api-to-mcp ``` Then: `/api-to-mcp https://developer.example.com/openapi.json`, or ask the `api-to-mcp` agent. Needs `uv` on PATH. - **Any MCP client**: `api-to-mcp mcp` (stdio) or `api-to-mcp mcp --http --port 8090`. Tools: `doctor`, `workspace`, `catalog_search`, `catalog_get`, `template_entry`, `ingest_openapi`, `read_docs`, `draft_entry`, `save_entry`, `lint_entry`, `generate_server`, `try_tool`, `test_server`, `live_verify` ([docs/TOOLS.md](docs/TOOLS.md)). - **CLI**: every tool is a command: `api-to-mcp ingest <url>`, `api-to-mcp save jobs my_board entry.json`, `api-to-mcp test jobs my_board`, `api-to-mcp serve jobs my_board`, ... (`api-to-mcp --help`). ## Install ```bash uvx --from api-to-mcp-forge api-to-mcp doctor # or: pip install api-to-mcp-forge / uv tool install api-to-mcp-forge ``` The PyPI package is `api-to-mcp-…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.