Add MCP feature for Angular Material components

[eneajaho]

Feature Description

Just like we can search for angular docs, we need mcp feature for angular material components.

Use Case

Having an easier time working with MCP and AI and angular material components

[andrewseguin]

Can you add more information about what you are looking for? We've had a good experience asking AI to integrate our components. Using MCP servers for this would require specific use cases and needs, otherwise it might just degrade the experience

[eneajaho]

1. Having up to date information about components. For example in v20, we have matButton that we can use instea of mat-flat-button and mat-stroked-button and others. Having this sorted out by the mcp server would help the ai model I believe.
2. I haven't found a good plugin to help me autocomplete Angular Material theming in scss files, so having MCP knowing exactly what is available for theming and what not, is helpful.
3. When using Angular Material, it works great when you use NgModules, but sometimes when using multiple directives, selectors and components, it's hard to get the imports right with AI model alone, having mcp that knows exactly what selector points too would be great.

[shhdharmen]

Not MCP, but taking inspiration from angular rules files, I recently published rules files for Angular Material on Angular-Material-Dev/angular-material-ai-rules GitHub repo. If Angular team finds it useful, I can raise MR to this repo.

[BrianMikinski]

Can you add more information about what you are looking for? We've had a good experience asking AI to integrate our components. Using MCP servers for this would require specific use cases and needs, otherwise it might just degrade the experience

An official MCP server for angular material and/or an instructions file for styling would be a massive win for the Angular community. The biggest issue working with the material component library is understanding which sass variables and properties should be used to get the styling you want. Copilot/Cursor usually doesn't start from a very good base when it's building styling and components for you and you end up having to do lots of manually lookups or updates when building out a design system for you app. I've gone so far now as to use agents to generate examples in my app for overriding styling, purely to give CoPilot and Cursor a base to work from when modifying my code. The instructions files help but they only get you so far.