Spring Toolkit MCP
Related Servers
Alternatives to Spring Toolkit MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.15107 npm15Apache 2.0
- AlicenseCqualityDmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server that provides security scanning, project mapping, and vulnerability fix generation to AI coding assistants.127 npm2MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.33 npmMIT
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.MIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1523 npm3MIT
TDQS
Scored across 44 tools
Most tools have distinct purposes, especially the Actuator endpoints each targeting a specific resource. However, there are aliases (e.g., spring_project_summary / analyze_project_structure, spring_generate_mockmvc_tests / generate_mockmvc_test) that create ambiguity, and the testing tools (run_maven_tests, run_gradle_tests, run_specific_test) could be confused despite different contexts.
The majority follow a verb_noun pattern (list_, get_, run_, inspect_). Some tools have a 'spring_' prefix while others do not, causing minor inconsistency. Overall, the naming is predictable and readable, with only a few deviations.
With 44 tools, the number is high for typical agent usability. While each Actuator endpoint is distinct, the sheer count risks overwhelming agents. The scope is broad (project analysis, testing, and monitoring), but the tool set could be consolidated, e.g., by making Actuator endpoints configurable or merging some similar tools.
The tool set covers project analysis, code review, test generation, test execution, and nearly all Actuator endpoints. Minor gaps include no tool for creating or building a Spring Boot project, and no coverage of Spring Boot's configuration management (like env properties are read-only). Overall, it's comprehensive for analysis and monitoring.