Angular CLI MCP server integration via Gemini CLI behaves inconsistently (requests have no discernible pattern)
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 14h 23m
- Merged PRs (30d)
- 162
Description
### 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_
Contributor guide
Research direction
Start by reproducing the issue with `ng mcp`, the generated MCP JSON, Gemini CLI `settings.json`, and the `list_projects` request. Compare runs where tools are discovered or invoked successfully with the ENOENT failure; done means the Angular CLI MCP server behaves consistently across repeated prompts and project directories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100