Skip to content

Allowing MCP server to discover and call available Angular schematics #32922

Description

@matthieu-crouzet

Command

mcp

Description

Today, when I'm using LLM with the Angular MCP server, code is generated directly by the LLM but for some cases it would provide better result if it is using the available schematic (Angular ones or external libraries ones).

Describe the solution you'd like

When using the Angular MCP server, I would expect LMM to be aware of which Angular schematics are available in the project (the ones from Angular + the ones from external libraries).
I would love that the Angular MCP server is able to read the schematic description and input, to know if it should use it or not and how to call it.

Describe alternatives you've considered

No response

Activity

  1. MarkTechson commented on Apr 2, 2026

    @MarkTechson

    Hi @matthieu-crouzet - in this case, the angular-developer skill is a way to give the LLM instructions on how to use some Angular tooling. You can have a look : github.com/angular/skills

    Happy to answer more questions.

  2. matthieu-crouzet commented on Apr 3, 2026

    @matthieu-crouzet
    Author

    Hello @MarkTechson, maybe I'm mistaken.
    From what I see in the skills, there are references only to Angular schematic (generating-code-ng-generate-or-ng-g).
    There is nothing to let the LLM knows that others libraries could also provides schematics.
    I think we can add a sentence like

    You can find all the available schematics by running ng g --help and more detail on each schematic by running ng g <schematic-name> --help

    Additionnal question:
    Is it planned to expose these skills in a claude code plugin or vscode agent plugin ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions