F
licenseA
qualityD
maintenanceEnables automatic generation of complete Maven projects (applications, plugins, libraries) with intelligent package detection, customizable file structure, and integrated ZIP export functionality.
8
1
-
mcp-auto-build
Related Servers
Alternatives to mcp-auto-build
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables triggering Jenkins builds from IDEs with Slack notifications, requiring only a one-time login.132 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze Java and Web projects, automatically generate unit tests (JUnit) and end-to-end tests (Selenium), and execute them directly through Maven or NPM commands.-
- FlicenseNot gradedqualityDmaintenanceAutomates Java Maven testing workflows with decision table-based test generation, security vulnerability scanning, JaCoCo coverage analysis, and Git automation.-
- AlicenseNot gradedqualityDmaintenanceAutomates routine DevOps tasks like Jenkins builds and GitLab merge requests through the MCP protocol, simplifying daily operations.4 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables scanning Java/Maven projects to generate TOGAF-standard architecture deliverables (Excel and PPTX) via natural language commands.6MIT
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation4/5
buildPackage is clearly the full end-to-end workflow, while buildBackend and buildFrontend are explicitly scoped to individual project types. getProjectInfo is distinct as an informational tool, so an agent can choose correctly based on whether a full or partial build is needed. There is minor potential overlap between buildPackage and the specific build tools, but the use-case descriptions resolve it.
Naming Consistency5/5
All tool names follow a consistent camelCase verb-first pattern: buildPackage, buildBackend, buildFrontend, getProjectInfo. The verbs are descriptive and the naming style is uniform across the entire server.
Tool Count5/5
Four tools is well-scoped for a build automation server: one full-build orchestrator, two project-type-specific builders, and one information-gathering tool. Each tool has a clear role, and none feel redundant or missing.
Completeness5/5
The tool surface covers the full build lifecycle: retrieving project metadata, building backend projects, building frontend projects, and performing a complete packaged build. There are no obvious dead ends or missing operations within the stated build-automation purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues