Spring Boot example that exposes SpringDoc OpenAPI operations as safe MCP tools.
Turn any SpringDoc-powered Spring Boot API into a production-ready MCP gateway. Swagger MCP Bridge discovers your OpenAPI operations, publishes them as safe MCP tools, and adds a smart gateway layer for API discovery, validation, response shaping, and multi-step workflow orchestration. This repository intentionally separates the public surfaces so each one reads naturally in its own ecosystem:…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Turn any SpringDoc-powered Spring Boot API into a production-ready MCP gateway. Swagger MCP Bridge discovers your OpenAPI operations, publishes them as safe MCP tools, and adds a smart gateway layer for API discovery, validation, response shaping, and multi-step workflow orchestration. This repository intentionally separates the public surfaces so each one reads naturally in its own ecosystem: Project / docs | Swagger MCP Bridge | Maven dependency | | Official MCP Registry server | | Runnable…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.