mcp-angular-cli
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ng_generateC | Run 'ng generate' to create a new Angular artifact (component, service, etc.) |
| ng_addC | Run 'ng add' to add a package to the Angular workspace |
| ng_newC | Run 'ng new' to create a new Angular workspace |
| ng_runC | Run 'ng run' to execute a custom architect target |
| ng_updateC | Run 'ng update' to update Angular packages and run migrations. |
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 5 tools
Each tool has a clearly distinct purpose corresponding to a specific Angular CLI command: ng_new creates workspaces, ng_add adds packages, ng_generate creates artifacts, ng_run executes targets, and ng_update updates packages. There is no overlap or ambiguity between these functions.
All tool names follow a consistent 'ng_' prefix pattern with a verb suffix (add, generate, new, run, update), using snake_case uniformly. This predictable naming makes it easy to identify and select the correct tool.
With 5 tools, the server is well-scoped for its purpose of exposing key Angular CLI commands. It covers essential operations, though it might be slightly thin if advanced CLI features are excluded, but it's reasonable for core workflows.
The tool set covers major Angular CLI operations: creating workspaces, adding packages, generating artifacts, running targets, and updating packages. Minor gaps may exist, such as missing build or serve commands, but core lifecycle tasks are well-represented.