Angular Toolkit MCP
A Model Context Protocol server that provides Angular project analysis and refactoring capabilities, enabling LLMs to analyze component usage patterns, dependency structures, and perform safe refactoring with breaking change detection.
README Documentation
Angular Toolkit MCP
A Model Context Protocol (MCP) server that provides Angular project analysis and refactoring capabilities. This server enables LLMs to analyze Angular projects for component usage patterns, dependency analysis, code quality issues, and provides automated refactoring assistance.
Key Features
- Component Analysis: Detect deprecated CSS classes and component usage violations
- Safe Refactoring: Generate contracts for safe component refactoring with breaking change detection
- Dependency Mapping: Map component dependencies across modules, templates, and styles
- ESLint Integration: Lint Angular files with automatic ESLint configuration discovery
- Project Analysis: Analyze buildable/publishable libraries and validate import paths
- Component Documentation: Retrieve component data and documentation, list available components
Use Cases
- Angular project migration and refactoring
- Component usage analysis and dependency mapping
- Deprecated CSS class detection and reporting
- Component contract generation for safe refactoring
- Breaking change detection during component updates
- Code quality analysis and improvement
Quick Start
Install and run via npx (no manual build required):
{
"mcpServers": {
"angular-toolkit": {
"command": "npx",
"args": [
"@push-based/angular-toolkit-mcp@latest",
"--workspaceRoot=/absolute/path/to/your/angular/workspace",
"--ds.uiRoot=packages/ui"
]
}
}
}
Required Node.js version: 18 or higher
Configuration
Prerequisites
- Node.js (version 18 or higher) with ESM support
Installation & Setup
For Users
Simply use npx as shown in the Quick Start section above. No installation or build required.
For Contributors (Local Development)
-
Clone the repository
-
Install dependencies and build the MCP
npm install npx nx build angular-mcp -
Locate the built server
After building, the server will be available at
packages/angular-mcp/dist/main.js
MCP Configuration
Add the server to your MCP client configuration (e.g., Claude Desktop, Cursor, Copilot, Windsurf or other MCP-compatible clients):
For Users (npx - Recommended)
{
"mcpServers": {
"angular-toolkit": {
"command": "npx",
"args": [
"@push-based/angular-toolkit-mcp@latest",
"--workspaceRoot=/absolute/path/to/your/angular/workspace",
"--ds.uiRoot=relative/path/to/ui/components",
"--ds.storybookDocsRoot=relative/path/to/storybook/docs",
"--ds.deprecatedCssClassesPath=relative/path/to/component-options.mjs"
]
}
}
}
For Contributors (Local Development)
When developing locally, point to the built server:
{
"mcpServers": {
"angular-toolkit-mcp": {
"command": "node",
"args": [
"/absolute/path/to/angular-toolkit-mcp/packages/angular-mcp/dist/main.js",
"--workspaceRoot=/absolute/path/to/your/angular/workspace",
"--ds.uiRoot=relative/path/to/ui/components",
"--ds.storybookDocsRoot=relative/path/to/storybook/docs",
"--ds.deprecatedCssClassesPath=relative/path/to/component-options.mjs"
]
}
}
}
Note:
ds.storybookDocsRootandds.deprecatedCssClassesPathare optional. The server will start without them. Tools that require these paths will return a clear error prompting you to provide the missing parameter.
Note: The example file contains configuration for
ESLintofficial MCP which is required for the toolkit to work properly.
Configuration Parameters
Required Parameters
| Parameter | Type | Description | Example |
|---|---|---|---|
workspaceRoot | Absolute path | Root directory of your Angular workspace | /Users/dev/my-angular-app |
ds.uiRoot | Relative path | Directory containing UI components | packages/ui |
Optional Parameters
| Parameter | Type | Description | Example |
|---|---|---|---|
ds.storybookDocsRoot | Relative path | Root directory containing Storybook documentation used by documentation-related tools | storybook/docs |
ds.deprecatedCssClassesPath | Relative path | JavaScript file mapping deprecated CSS classes used by violation and deprecated CSS tools | design-system/component-options.mjs |
When optional parameters are omitted:
ds.storybookDocsRoot: Tools will skip Storybook documentation lookups (e.g.,get-ds-component-datawill still return implementation/import data but may have no docs files).ds.deprecatedCssClassesPath: Tools that require the mapping will fail fast with a clear error. Affected tools include:get-deprecated-css-classes,report-deprecated-css,report-all-violations, andreport-violations.
Deprecated CSS Classes File Format
The component-options.mjs file should export an array of component configurations:
const dsComponents = [
{
componentName: 'DsButton',
deprecatedCssClasses: ['btn', 'btn-primary', 'legacy-button']
},
{
componentName: 'DsModal',
deprecatedCssClasses: ['modal', 'old-modal']
}
];
export default dsComponents;
Example Project Structure
my-angular-workspace/
├── packages/
│ ├── ui/ # ds.uiRoot
│ │ ├── button/
│ │ ├── modal/
│ │ └── ...
│ └── design-system/
│ └── component-options.mjs # ds.deprecatedCssClassesPath
├── storybook/
│ └── docs/ # ds.storybookDocsRoot
└── apps/
└── my-app/
Troubleshooting
- Server not starting: Ensure all paths are correct and the server is built
- Permission errors: Check that the Node.js process has read access to all specified directories
- Component not found: Verify that component names in
component-options.mjsmatch your actual component class names - Path resolution issues: Use absolute paths for
workspaceRootand relative paths (from workspace root) for other parameters
Available Tools
Component Analysis
-
report-violations: Report deprecated CSS usage in a directory with configurable grouping format -
report-deprecated-css: Report deprecated CSS classes found in styling files -
get-deprecated-css-classes: List deprecated CSS classes for a component
Component Analysis
-
list-ds-components: List all available Design System components in the project with their file paths and metadata -
get-ds-component-data: Return data for a component including implementation files, documentation files, and import path -
build-component-usage-graph: Maps where given Angular components are imported (modules, specs, templates, styles) so refactors touch every file
Tool behavior with optional parameters
The following tools work without optional params:
get-project-dependenciesbuild-component-usage-graphget-ds-component-data(documentation section is empty ifds.storybookDocsRootis not set)- Component contract tools:
build_component_contractdiff_component_contractlist_component_contracts
The following tools require optional params to work:
-
Requires
ds.deprecatedCssClassesPath:get-deprecated-css-classesreport-deprecated-cssreport-all-violationsreport-violations
-
Requires
ds.storybookDocsRootfor docs lookup (skipped otherwise):get-ds-component-data(docs files discovery only)
Component Contracts
-
build_component_contract: Generate a static surface contract for a component's template and SCSS -
diff_component_contract: Compare before/after contracts for parity and surface breaking changes -
list_component_contracts: List all available component contracts in the .cursor/tmp/contracts directory
Project Analysis
-
get-project-dependencies: Analyze project dependencies and detect if library is buildable/publishable. Checks for peer dependencies and validates import paths for components -
lint-changes: Lint changed Angular files using ESLint rules. Automatically resolves ESLint config by walking up the directory tree
Component Contract Workflow
The component contract system provides a safety net for Angular component refactoring:
- Generate Initial Contract: Create a baseline contract before refactoring
- Perform Refactoring: Make your component changes
- Generate New Contract: Create a contract after refactoring
- Compare Contracts: Detect breaking changes and API differences
# 1. Generate initial contract
User: build_component_contract for my-component
# 2. Make component changes...
# 3. Generate new contract and compare
User: build_component_contract for my-component
User: diff_component_contract old-contract.json new-contract.json
Angular Project Integration
This MCP server is designed for Angular project analysis and refactoring. It helps with:
- Migration Planning: Identify all usages of deprecated components/classes
- Refactoring Safety: Generate contracts to ensure no breaking changes
- Documentation Access: Quick access to component documentation and examples
- Code Quality: Analyze and improve code quality across your Angular project
Documentation
For comprehensive documentation, guides, and workflows, see our Documentation Hub.
Contributing
Please read our Contributing Guide.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Sponsored by