workspace-build-mcp
Related Servers
Alternatives to workspace-build-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables automated packaging of Maven backend and npm frontend projects, with SVN version retrieval and both step-by-step and one-click build workflows.4Apache 2.0
- AlicenseBqualityDmaintenanceProduction-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.141MIT
- AlicenseAqualityCmaintenanceEnables automated pull-request review workflows for Angular repositories by providing tools to generate, read, and save diffs, and to fetch review templates.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables building, diffing, syncing, testing, inspecting, and publishing Dify 1.11.1 workflow DSL through a single stdio MCP tool with safety gates and local state.Apache 2.0
- AlicenseAqualityFmaintenanceEnables building, verifying, previewing, deploying, diagnosing, updating, and rolling back full-stack Micro apps through typed local MCP tools backed by micro-cli.688 npmMIT
- FlicenseAqualityCmaintenanceEnables inspecting local Git repositories and automating delivery tasks such as status checks, diffs, commits, pull requests, and deployments using git and GitHub CLI.6-
TDQS
Scored across 6 tools
All tools have clearly distinct purposes: building with/without linking, two different git operations, listing aliases, and checking status. No overlap between any tool's functionality.
All tools follow the consistent `ws_verb_noun` pattern using snake_case, e.g., ws_build_link, ws_git_push, ws_list_aliases. Naming is predictable and readable.
With 6 tools, the server is well-scoped for workspace build management. Each tool serves a distinct and necessary purpose without being overly numerous or sparse.
The tool surface covers core workflows: building, git operations, and configuration inspection. Minor gaps exist (e.g., no tool to clean or reset workspace), but the set is sufficient for primary tasks.