[bug] remove mcp refuses a root server named 'ambiguous' without saying why
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start in src/remove.ts at mcpRemovalTarget(name) and trace how the root server name reaches the refusal check. Reproduce with teamai remove mcp ambiguous --force using the shown mcp/mcp.yaml entry. Done means the root server named ambiguous is removed and a removal branch is pushed instead of returning Nothing was removed.
Written by the indexing model from the issue text.
Description
Description
teamai remove mcp ambiguous refuses to remove a server named ambiguous from mcp/mcp.yaml, and prints no reason.
remove mcp <name>
-> mcpRemovalTarget(name) src/remove.ts
root file defines it -> return name // "ambiguous"
-> caller: target === 'ambiguous' // the refusal sentinel
-> ambiguous = true -> "Nothing was removed.", exit 1
mcpRemovalTarget returns string | 'ambiguous' | null, so the refusal sentinel shares its value space with real server names. Every real refusal logs its reason before returning the sentinel, so this is the only path that fails with no explanation.
Expected: the server is removed, as any other root server name is.
Reproduction
- In the team repo,
mcp/mcp.yaml:servers: - name: ambiguous transport: http url: https://a.example.com teamai remove mcp ambiguous --force- Output is
✖ Nothing was removed., exit code 1, and no removal branch is pushed.
Environment
- OS: macOS 26.5
- Node.js: v22.23.3
- teamai: 0.22.0 (
mainat a8ab8e00) - Provider: git
- AI tool(s): Claude Code
Logs
Output
$ teamai remove mcp ambiguous --force
✖ Nothing was removed.
exit code: 1
removal branch: <none>
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 376
- Avg merge
- 13h 49m
- Merged PRs (30d)
- 284
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Tencent/teamai-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Tencent/teamai-cli#848 ·
Maintainers usually reply within 1 day
-
[bug] codebase extract aborts on Node 24 with 'Fatal process out of memory: Zone' when parsing SwiftOpenbug
Difficulty 4/5 3-5 days Newbie friendliness 50/100
Tencent/teamai-cli#860 ·
Maintainers usually reply within 1 day
-
[bug] pull / push / status --dry-run still write: the loaders they use take no { dryRun }Possibly taken @jeff-r2026 claimed this 1 day ago. Open
Tencent/teamai-cli#850 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Swift AST: cross-file IMPLEMENTS/REFERENCES edges are dropped (module-scope symbols need no import)Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Tencent/teamai-cli#843 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Tencent/teamai-cli#836 ·
Maintainers usually reply within 1 day
All issues in Tencent/teamai-cli
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#611 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
polka-codes/test#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
GoogleChromeLabs/project-sesame#217 ·
Maintainers usually reply within 12 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
solana-foundation/solana-com#2202 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100