AI Unified Process Spring Boot layers - service and REST API implementation and tests
94
95%
Does it follow best practices?
Impact
93%
1.03xAverage score across 4 eval scenarios
Passed
No findings from the security scan
The aiup-spring-boot skills work without any MCP servers — they fall back to your own knowledge and the
documentation links inside each skill. For authoritative, up-to-date API lookups, configure the optional MCP server
below in your agent. It is advisory only; nothing in these skills hard-requires it.
| Server | Type | URL | Used by |
|---|---|---|---|
| JavaDocs | http | https://www.javadocs.dev/mcp | spring-service, spring-rest, spring-service-test, spring-rest-test |
Add this to your project's .mcp.json (the Tessl tessl mcp start bridge can stay alongside it):
{
"mcpServers": {
"JavaDocs": { "type": "http", "url": "https://www.javadocs.dev/mcp" }
}
}For other agents (Cursor, Gemini, Codex, Copilot), add the same server to that agent's MCP configuration file.
aiup-coreaiup-core's .mcp.json wires up context7 (https://mcp.context7.com/mcp), a general library-documentation
server that also resolves the Spring Boot, Spring Framework, and Testcontainers reference documentation. With
aiup-core installed (a prerequisite for this plugin) you get those lookups without configuring anything here.
Tessl ships it with the plugin: tessl install reads the plugin's bundled .mcp.json and writes it into the MCP
configuration of each agent it configures, as the Claude Code marketplace install does. If your agent does not list
it after the install — an agent Tessl does not configure, or a manual skill copy — configure the server above
manually as shown.