aws / aws/amazon-q-developer-cli
bug: Q CLI MCP specifies invalid protocol version when using mcp-remote proxy
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 439
- PR merge metrics
- No merged PRs in 30d
Description
### 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
MasOS 15.6
### Expected behaviour
When using the mcp-remote proxy, I expect Q to be able to connect to remote MCP servers.
### Actual behaviour
When Q attempts to connect to the MCP server, no supported protocol version is specified. mcp-remote just passes the version through to the remote server:
[2025-08-11T00:24:18.539Z][7926] {
"jsonrpc": "2.0",
"id": 0,
"method": "initialize",
"params": {
"protocolVersion": "2",
"capabilities": {},
"clientInfo": {
"name": "Q CLI Chat (via mcp-remote 0.1.18)",
"version": "1.0.0"
}
}
The current protocol version is 2025-06-18.
Presumably Q is using an older version of the protocol (this is fine), but that ID is apparently not passed.
amazon-q-developer-cli/crates/chat-cli/src/mcp_client/transport/base_protocol.rs:
//! Referencing https://spec.modelcontextprotocol.io/specification/2024-11-05/basic/messages/
//! Protocol Revision 2024-11-05
This results in the MCP tool not loading. Modifying mcp-remote to override the protocol version seems to be a workaround, albeit not well tested and unsupported.
### Steps to reproduce
"mcpServers": {
"Some-MCP-Server": {
"command": "/path/to/npx",
"args": [
"/path/to/mcp-remote",
"https://some.mcpserver.com/sse",
"--transport",
"sse-first",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer SOme-MCP-Server-Token"
}
}
Run q chat, observe server timeout during startup.
### Environment
```yaml
[q-details]
version = "1.13.2"
hash = "e44ee53d76813a5ef107dcd0d6181b089cb5b2f2"
date = "2025-08-08T20:32:47.811878Z (2d ago)"
variant = "full"
[system-info]
os = "macOS 15.6.0 (24G84)"
chip = "Apple M3 Max"
total-cores = 16
memory = "64.00 GB"
[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "VSCode"
install-method = "unknown"
[env-vars]
PATH = "/Users/USER/.nvm/versions/node/v20.19.3/bin:/Users/USER/bin:/Users/USER/.local/bin:/usr/local/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/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/.nvm/versions/node/v20.19.3/bin:/Users/USER/bin:/Users/USER/.local/bin"
QTERM_SESSION_ID = "565054e08f8c4de1871aee6189dab788"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.13.2"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER"
__CFBundleIdentifier = "com.microsoft.VSCode"
```
Contributor guide
Assessment
This issue has not been assessed yet.