Fix: remove mcp configuration files from project templates

[Marina-L-Stoyanova]

Removed the default mcp.json files containing Ignite UI MCP server configurations from the project template.

After this fix, users can decide whether to include MCP configuration by selecting the appropriate ai-config option or through the wizard.

[coveralls]

coverage: 88.338%. remained the same — mstoyanova/remove-mcp-from-templates into master

[Copilot]

🔵 Needs a closer look

Removing the template file drops the angular-cli MCP server from the CLI-first Angular flow (unless re-added via ig ai-config logic), and the docs that claim .vscode/mcp.json is created by ig new become inaccurate.

Pull request overview

This PR removes the default VS Code MCP configuration files (.vscode/mcp.json) from the shipped project templates so MCP setup becomes opt-in via ig ai-config / the ig new wizard choices rather than being scaffolded unconditionally.

Changes:

• Removed the Angular template’s .vscode/mcp.json that previously included angular-cli, igniteui-cli, and igniteui-theming MCP servers.
• Removed the React and Web Components templates’ .vscode/mcp.json that previously included igniteui-cli and igniteui-theming MCP servers.

File summaries

File	Description
packages/igx-templates/igx-ts/projects/_base/files/__dot__vscode/mcp.json	Removes default VS Code MCP config from Angular base template.
packages/cli/templates/webcomponents/igc-ts/projects/_base/files/__dot__vscode/mcp.json	Removes default VS Code MCP config from Web Components base template.
packages/cli/templates/react/igr-ts/projects/_base/files/__dot__vscode/mcp.json	Removes default VS Code MCP config from React base template.

Review details

Suppressed comments (2)

packages/cli/templates/webcomponents/igc-ts/projects/_base/files/__dot__vscode/mcp.json:1

• With template-level .vscode/mcp.json removed, documentation that says ig new "also gets an initial .vscode/mcp.json" becomes inaccurate unless the user explicitly selects the VS Code assistant during ig new/ig ai-config. For example: packages/igniteui-mcp/igniteui-doc-mcp/docs_baseline/webcomponents/general-how-to-mcp-e2e.md:98-101 currently states this unconditionally. The docs should reflect that .vscode/mcp.json is only created when the VS Code assistant is selected (or --assistants vscode is passed).
  packages/igx-templates/igx-ts/projects/_base/files/__dot__vscode/mcp.json:1
• Removing this file drops the previously-scaffolded angular-cli MCP server entry for CLI-created Angular projects. In the ig new flow, packages/cli/lib/commands/new.ts always calls configure(), but configureMCP() in packages/cli/lib/commands/ai-config.ts only calls addMcpServers(assistant) with no additionalServers, and addMcpServers() only writes igniteui-cli + igniteui-theming (see packages/core/util/mcp-config.ts). As a result, users selecting VS Code in the wizard will no longer get the angular-cli MCP server that this deleted template file used to provide.

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.