MCP Spring Boot Toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_entityA | Generate a JPA Entity class with Lombok annotations, audit fields, and proper mappings |
| generate_controllerB | Generate a Spring Boot REST Controller with CRUD endpoints and proper exception handling |
| generate_serviceA | Generate a Spring Boot Service with interface and implementation following best practices |
| generate_dtoB | Generate Request/Response DTOs with validation annotations and MapStruct mapper |
| generate_repositoryB | Generate a Spring Data JPA Repository with custom query methods |
| generate_exception_handlerB | Generate global exception handler with @ControllerAdvice and custom exceptions |
| generate_application_propertiesB | Generate application.yml configuration for Spring Boot with common settings |
| analyze_pomA | Analyze pom.xml for dependency issues, version conflicts, and suggest improvements |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_api | Review a Spring Boot REST API controller for best practices |
| debug_exception | Help debug a Spring Boot exception with stack trace analysis |
| optimize_query | Optimize a JPA/Hibernate query for better performance |
| security_audit | Perform a security audit on Spring Boot configuration and code |
| migration_plan | Create a migration plan for upgrading Spring Boot version |
| design_microservice | Design a Spring Boot microservice architecture |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| project-structure-guide | Recommended package structure for scalable Spring Boot applications |
| security-guide | Security best practices: JWT, OAuth2, CORS, CSRF, rate limiting |
| architecture-guide | Layered architecture patterns: Controller → Service → Repository with DTOs and Mappers |
| api-design-guide | RESTful API design patterns: versioning, pagination, filtering, error responses |
TDQS
Scored across 8 tools
Each tool targets a distinct artifact in the Spring Boot architecture: entity, controller, service, DTO, repository, exception handler, and application properties. The analyze_pom tool is clearly separate for dependency analysis. No two tools appear to generate the same type of output.
Seven tools follow the consistent verb_noun pattern 'generate_<artifact>', and analyze_pom also follows the same verb_noun pattern with a different verb. The naming is predictable and clearly indicates the action and target.
With 8 tools, the server is well-scoped for a Spring Boot code generation toolkit. It covers the essential layers and configuration without excessive granularity, making it easy for an agent to select the right tool.
The set covers core generation needs (entity, controller, service, repository, DTO, exception handler, application properties) and includes pom analysis. Missing are tools for project scaffolding, security configuration, or tests, but these are minor gaps that can be worked around or generated manually.