Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

feat(@angular/cli): add schematics mcp tools #31730

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lekhmanrus wants to merge 1 commit into angular:main
base: main
Choose a base branch
Loading
from lekhmanrus:feat/no-ref/schematics-mcp-tools

Conversation

@lekhmanrus
Copy link
Contributor

@lekhmanrus lekhmanrus commented Nov 9, 2025

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Currently, Angular CLI does not provide MCP integration with schematics.

What is the new behavior?

Added new Angular schematics to streamline MCP tools setup within projects.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Copy link
Member

clydin commented Nov 9, 2025

Thank you for the extensive contribution.

However, the Angular team is currently evaluating the effectiveness across various models and agents regarding such an approach. For instance, many agents are currently capable of discovering and executing the existing schematics independently or with a set of project rules. Further, some will opt to create equivalent code directly as they would otherwise use the schematics and then remove the content with new.
Additionally, a feature of this size will most likely need to progress through a design process to vet such items as performance, security risks, and overall effectiveness.
lekhmanrus reacted with thumbs up emoji

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

Reviewers

No reviews

Assignees

No one assigned

Labels

area: @angular/cli detected: feature PR contains a feature commit

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /