aws / aws/amazon-q-developer-cli
Feature Request: Support toolAliases in mcp.json like agent
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again
### Operating system
macOS 14.3.1 (23D60)
### Expected behaviour
The mcp.json configuration file should support a `toolAliases` field that allows users to create custom aliases for MCP tools to resolve naming conflicts or provide more intuitive names. This would work similarly to how `toolAliases` is supported in agent configuration files.
### Actual behaviour
Currently, the mcp.json configuration file does not support `toolAliases`. Users cannot create custom aliases for MCP tools directly in the MCP configuration, which can lead to naming conflicts when multiple MCP servers provide tools with same names or when users want more intuitive tool names.
### Steps to reproduce
1. Create or edit an mcp.json file (either global at ~/.aws/amazonq/mcp.json or workspace-specific at .amazonq/mcp.json)
2. Try to add a `toolAliases` field to define custom aliases for MCP tools
3. Observe that this field is not recognized or supported in the MCP configuration
### Environment
```yaml
[q-details]
version = "1.13.2"
hash = "36e70d1cad4465a9ea479bb7f10d7973b717b4f7"
date = "2025-08-08T20:16:09.268082Z (3d ago)"
[system-info]
os = "macOS 14.3.1 (23D60)"
chip = "Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz"
total-cores = 4
memory = "16.00 GB"
[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
install-method = "brew"
[env-vars]
PATH = "/Users/USER/.sdkman/candidates/java/current/bin:/Users/USER/.sdkman/candidates/groovy/current/bin:/Users/USER/.sdkman/candidates/gradle/current/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.cargo/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Users/USER/.orbstack/bin"
QTERM_SESSION_ID = "933f7a72395e438189d11a9f3b9ef807"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.13.2"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"
[chat-settings]
[chat-trusted_tools]
fs_read=trusted
@github/search_issues=trusted
[chat-failed_request_ids]
none
[chat-context]
current_profile=default
profile_context=none
files=none
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Non sono indicati file sorgente o test. Inizia individuando il parser di mcp.json e il supporto esistente di toolAliases nella configurazione dell'agent, quindi segui il modo in cui i nomi degli strumenti MCP vengono registrati e risolti. Il lavoro è completato quando gli alias vengono accettati nella configurazione MCP globale e di workspace e vengono risolti senza conflitti di nomi.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- cli
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100