Angular CLI

You can use the Angular CLI MCP Server to automate Angular workspace tasks via MCP. It lets you generate components and services, add packages, create workspaces, and run custom architect targets from an LLM or agent, streamlining Angular project workflows.

How to use

You interact with the server through an MCP client or tool integrated into your workflow. The server exposes a set of actions aligned with the Angular CLI commands so you can generate artifacts, add dependencies, scaffold workspaces, and trigger custom targets without leaving your automation environment. You can run commands that map to ng generate, ng add, ng new, ng run, and ng update, and you can point these actions at your local Angular project or workspace.

How to install

Prerequisites you need before installing:
- Node.js (recommended LTS version) and npm
- Access to a terminal or shell with npm in your PATH

Install the MCP server globally so you can run it from anywhere:

npm install -g @talzach/mcp-angular-cli

Alternatively, install the MCP server locally in your project as a development dependency:

npm install --save-dev @talzach/mcp-angular-cli

Run the server directly when you want to start using it in your environment:

npx @talzach/mcp-angular-cli

If you are using a custom MCP client configuration, you can point the client to the MCP server using the following example configuration.

{
  "mcpServers": {
    "angular-cli": {
      "command": "npx",
      "args": ["-y", "@talzach/mcp-angular-cli"]
    }
  }
}

Additional sections

Configuration details, security considerations, and practical usage notes help you get started and stay productive. Below you’ll find concrete examples of how to invoke the server, what actions you can perform, and how to integrate the server with your MCP workflow.

Example actions you can perform with the server include:

• Generate an Angular component or service
• Add a package to the workspace
• Create a new Angular workspace
• Run a custom architect target
• Update Angular packages and dependencies

If you want to run the server from a local build output after development, you can start it from the built index, using a Node command that points to the dist index file.

node /path/to/your/mcp-angular-cli/dist/index.js

Available tools

generate

Trigger ng generate to scaffold Angular artifacts such as components, services, directives, or pipes in your workspace.

add

Trigger ng add to add packages to your Angular workspace, integrating new dependencies into your project.

new

Trigger ng new to create a new Angular workspace or application with a starter setup.

run

Trigger ng run to execute custom architect targets defined in your Angular project.

update

Trigger ng update to update Angular packages and dependencies across your workspace.