openapi-tools vs io.github.mgaruccio/openapi-navigator
openapi-tools is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
openapi-tools is a plugin bundle for AI coding tools published by Alex Kopylov. No marketplace we read lists it any more. io.github.mgaruccio/openapi-navigator is an MCP server published by mgaruccio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace alex-kopylov/zweihander | Removed on 2026-10-24 Version: 0.3.1 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.1 Downloads/month (PyPI): 99 Downloads/week (PyPI): 14 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | openapi-toolsno longer listed · | io.github.mgaruccio/openapi-navigator |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (openapi-navigator) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/alex-kopylov/zweihander | github.com/mikegaruccio/openapi-navigator |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of openapi-tools
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
OpenAPI CLI expert for @desplega.ai/oapi — register specs, execute requests, manage auth
-
DevsForge Enterprise API Specification Architect delivering comprehensive OpenAPI development methodologies, API documentation excellence, and integration optimization frameworks…
-
Use this agent to update, synchronize, or validate the OpenAPI specification (openapi.yml) against the actual REST API implementation. This includes adding new endpoints, updating…
-
MCP server that fronts any OpenAPI service: discover operations from its spec and call them
-
Expose an OpenAPI document to agents as a search-first tool catalog over your existing API.
-
Automate API security directly in Claude Code with 42Crunch - automatically audit OpenAPI specs, detect vulnerabilities aligned with OWASP API Security risks (including…
What each says it does
openapi-tools
Skills for listing and inspecting OpenAPI endpoints on running services.
io.github.mgaruccio/openapi-navigator
Navigate and query OpenAPI specs with fuzzy search, pagination, and API testing
How to run each
openapi-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.mgaruccio/openapi-navigator As a local MCP server: PyPI package
claude mcp add --transport stdio openapi-navigator -- uvx openapi-navigatorCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: openapi-tools · What it can do: io.github.mgaruccio/openapi-navigator · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.