workspace-build-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_CWD | No | cwd for mhdd24 (defaults to WORKSPACE_ROOT) | |
| ALIAS_APP_WS | No | Consumer app path – required for link | |
| ALIAS_CORE_WS | No | Library workspace (relative to root or absolute) – required for build | |
| WORKSPACE_ROOT | Yes | Monorepo / workspace root | |
| ALIAS_CORE_DIST | No | Dist folder under library ws (default dist/<project>) | |
| ALIAS_CORE_PACKAGE | No | npm package name to link (default @scope/<project>) | |
| ALIAS_CORE_PROJECT | No | Angular project name (default ui-core) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ws_statusA | Check workspace-build configuration: WORKSPACE_ROOT, alias paths, and whether ng/npm/mhdd24 are available. |
| ws_list_aliasesA | List configured aliases (core, app) with resolved absolute paths and package names. |
| ws_build_linkA | Build the UI library (core) and npm-link it into the consumer app. Runs scripts/workspace-build.ps1. |
| ws_build_onlyA | Build the UI library only (no npm link into the app). |
| ws_git_pushC | Run mhdd24 push with a commit message in the configured git working directory. |
| ws_git_smart_commitC | Run mhdd24 smart-commit in the configured git working directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.