Command
generate
Description
Before v6, ng update was just an internal tool, not available for community libraries.
It would be great to follow the same path for the mcp command, allowing it not to just expose Angular documentation but to act as a solution for any library to also expose a MCP server through the CLI.
In a similar way we can define schematics, we could define tools/resource we want to expose.
It would be built-in, avoiding having a third party tool to expose a MCP server for libraries.
PS: I used the generate command in the issue creation dropdown because mcp is not available
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Command
generate
Description
Before v6,
ng updatewas just an internal tool, not available for community libraries.It would be great to follow the same path for the
mcpcommand, allowing it not to just expose Angular documentation but to act as a solution for any library to also expose a MCP server through the CLI.In a similar way we can define schematics, we could define tools/resource we want to expose.
It would be built-in, avoiding having a third party tool to expose a MCP server for libraries.
PS: I used the
generatecommand in the issue creation dropdown because mcp is not availableDescribe the solution you'd like
No response
Describe alternatives you've considered
No response