Enterprise DNA
M MCP Servers Developer low

Neo1228/spring-boot-starter-swagger-mcp

by Various

Turn SpringDoc OpenAPI into production-ready MCP tools for Spring Boot: discovery, validation, workflows, and guardrails.

N

MCP

Neo1228/spring-boot-starter-swagger-mcp

Added 1 June 2026

#api-gateway #java #java-17 #java-25 #llm-tools #mcp #model-context-protocol #openapi

Overview

A Spring Boot starter that converts SpringDoc OpenAPI specifications into MCP tools. It enables discovery, validation, workflows, and guardrails for MCP-based interactions with Spring Boot services.

Best for

Best for
Spring Boot developers who want to expose their OpenAPI-defined services as MCP tools with minimal configuration

Use cases

  • Expose OpenAPI endpoints as MCP tools in Spring Boot
  • Add validation and guardrails to MCP workflows
  • Automate discovery of SpringDoc API definitions for MCP

Notes

A Spring Boot starter that converts SpringDoc OpenAPI specifications into MCP tools. It enables discovery, validation, workflows, and guardrails for MCP-based interactions with Spring Boot services.

2 stars on GitHub. Last updated 2026-05-17. Licensed Apache-2.0.

Use cases

  • Expose OpenAPI endpoints as MCP tools in Spring Boot
  • Add validation and guardrails to MCP workflows
  • Automate discovery of SpringDoc API definitions for MCP

Pros

  • Leverages existing SpringDoc OpenAPI setup for MCP conversion
  • Provides built-in production-ready features like guardrails and validation
  • Easy integration as a Spring Boot starter

Cons

  • Low community adoption with only 2 stars on GitHub
  • Tied to Spring Boot and SpringDoc, limiting flexibility outside that ecosystem
  • May lack extensive documentation or examples due to early stage

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Leverages existing SpringDoc OpenAPI setup for MCP conversion
  • Provides built-in production-ready features like guardrails and validation
  • Easy integration as a Spring Boot starter

Cons

  • Low community adoption with only 2 stars on GitHub
  • Tied to Spring Boot and SpringDoc, limiting flexibility outside that ecosystem
  • May lack extensive documentation or examples due to early stage