angular / angular/angular-cli

Angular CLI MCP server integration via Gemini CLI behaves inconsistently (requests have no discernible pattern)

Abierto
#32,130 3 comentarios 0 reacciones 0 asignados Ver en GitHub
area: @angular/cli needs: investigation
Lenguaje dominante
TypeScript
Estrellas
27k
Forks
11.8k
Merge medio
14 h 23 min
PR fusionados (30 d)
162

Descripción

### Command

other

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

MCP requests/invocations against the Angular CLI MCP server are inconsistent across runs, and no meaningful pattern can be identified. Because of this, best-practice requirements cannot be reliably met.

### Minimal Reproduction

- Generate mcp json with 'ng mcp'
- Add Server to Gemini CLI settings.json
- Start Gemini CLI and the Angular MCP server
- In Gemini CLI, write a prompt such as: “Create an Angular 21 Form Signals component and use the Angular CLI MCP server.”
- Observe that outcomes are inconsistent across runs (tools sometimes discovered, sometimes not; invocations sometimes succeed, sometimes fail) with no clear pattern

### Exception or Error

```text
Hallo! I will create an Angular component that uses Signals for form management. First, I need to inspect the existing Angular project to
understand its structure and version.
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ list_projects (angular-cli MCP Server) {} │
│ │
│ ENOENT: no such file or directory, scandir '/home/user/some_system_drive/V:/XSD' │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ You are running Gemini CLI in your home directory. It is recommended to run in a project-specific directory. │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Using: 1 MCP server
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ > Type your message or @path/to/file

Note: The inconsistent behavior also occurs beyond this specific message and is not limited to a single command or error
```

### Your Environment

```text
Angular CLI : 21.0.3
Node.js : 22.18.0
Package Manager : npm 10.9.3
Operating System : linux x64
```

### Anything else relevant?

_No response_

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza reproduciendo el problema con `ng mcp`, el JSON MCP generado, el `settings.json` de Gemini CLI y la solicitud `list_projects`. Compara las ejecuciones en las que las herramientas se descubren o invocan correctamente con el fallo ENOENT; se considera terminado cuando el servidor MCP de Angular CLI se comporta de forma consistente con prompts y directorios de proyecto repetidos.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
angular, typescript
Área
cli, developer-experience
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.