Swagger MCP Bridge
Expose your Spring Boot OpenAPI operations as guarded MCP tools so your agent can call your API safely during integration work.
Overview
Swagger MCP Bridge is a MCP server for the Build phase that exposes SpringDoc OpenAPI operations from Spring Boot as safe MCP tools over HTTP.
What is this MCP server?
- Spring Boot + SpringDoc OpenAPI example bridged to MCP (Swagger MCP Bridge v0.1.0)
- streamable-http MCP at http://localhost:8080/mcp when running the sample container
- Docker runtime hint with port mapping 8080:8080 for local trials
- Designed to expose OpenAPI operations as safe, bounded MCP tools rather than raw HTTP chaos
- Server version 0.1.0
- MCP URL http://localhost:8080/mcp
- Docker OCI package with published port 8080:8080
Community signal: 2 GitHub stars.
What problem does it solve?
Agents struggle to use your REST API reliably when only OpenAPI docs exist in a browser and no structured, permissioned tool surface is registered.
Who is it for?
Solo builders on Spring Boot who want a copy-paste pattern to connect OpenAPI-defined endpoints to Claude Code or Cursor.
Skip if: Non-Spring stacks or teams that need a managed multi-tenant MCP gateway without running their own container.
What do I get? / Deliverables
After you run the bridge against your Spring Boot app, your agent can call documented operations as MCP tools on localhost during integration and smoke testing.
- HTTP MCP endpoint mapping OpenAPI operations to agent-invokable tools
- Repeatable local pattern for agent-driven API smoke tests
Recommended MCP Servers
Journey fit
API bridging belongs in Build when you wire backends and want agents to exercise documented endpoints instead of guessing URLs. Integrations subphase is where OpenAPI-backed MCP tooling connects your running service to agent workflows.
How it compares
Reference MCP bridge for OpenAPI-backed Spring services, not a generic browser automation or npm security server.
Common Questions / FAQ
Who is swagger-mcp-bridge for?
Developers shipping Spring Boot APIs who want their agent to invoke documented endpoints through MCP instead of unstructured HTTP prompts.
When should I use swagger-mcp-bridge?
Use it while building or hardening API integrations when SpringDoc OpenAPI is already on the service and you are testing agent-driven workflows locally.
How do I add swagger-mcp-bridge to my agent?
Run the Docker image with port 8080 exposed, then add an MCP server entry pointing streamable-http transport to http://localhost:8080/mcp in your agent config.