An MCP server powered by fastMCP for inspecting local or remote OpenAPI specs.
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":"openapi-tools-mcp","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.
# OpenAPI Tools MCP and CLI A [Model Context Protocol](https://spec.modelcontextprotocol.io/) server powered by [fastMCP](https://pypi.org/project/fastmcp/) plus a JSON command-line interface for inspecting local or remote OpenAPI specs. Both interfaces expose the same summary, listing, filtering, retrieval, `$ref` resolution, and source-line behavior. The server also publishes MCP metadata (`instructions` and `website_url`) to guide clients toward local-file OpenAPI inspection workflows. ## Add as an MCP server Add this server to your MCP client configuration (PyPI): ```json { "mcpServers": { "openapi-tools": { "command": "uvx", "args": [ "--from", "openapi-tools-mcp", "openapi-tools-mcp" ] } } } ``` This launches the `openapi-tools-mcp` entrypoint from PyPI via `uvx`. TOML version (PyPI): ```toml [mcp_servers.openapi-tools] command = "uvx" args = ["--from", "openapi-tools-mcp", "openapi-tools-mcp"] ``` You can also install directly from GitHub with `uvx`: ```bash uvx --from git+ssh://git@github.com/kardaj/openapi-tools-mcp.git openapi-tools-mcp ``` ## Use the command-line interface Run the CLI ephemerally from PyPI with `uvx --from`: ```bash uvx --from openapi-tools-mcp openapi-tools-cli info ./openapi.yaml | jq ``` For persistent use, install the package as a uv tool and call the dedicated CLI entry point: ```bash uv tool install openapi-tools-mcp openapi-tools-cli info ./openapi.yaml ``` Run `openapi-tools-cli --help` (or `-h`) for a single help page covering `info`, `list`, and `get`, including supported sections, output shapes, reference and filter behavior, and examples. Each command has its own section; shared source, header, and help arguments appear once. Command-specific help, such as `openapi-tools-cli list --help`, shows that command's details and examples. Start with `info` to confirm the OpenAPI version, API metadata, and server base URLs. Use `list` to discover names, then `get` …
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.