aws / aws/amazon-q-developer-cli
Feature Request: Add capability to view raw MCP outputs
- 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
### Operating system
macOS 15.5.0 (24F74)
### Expected behaviour
Users should be able to view the raw outputs from MCP (Model Context Protocol) tool calls, allowing them to see the unprocessed data returned by the tools.
When querying data using an MCP, it's extremely important that users be able to see the raw results from the MCP in order to ensure the LLM is not hallucinating numbers.
Cline makes the possible and shows all MCP responses, and that feature alone is pushing me to Cline over Q CLI.
### Actual behaviour
Chat context is not relevant. This is a feature request to improve the ability of humans to detect and correct LLM hallucinations which are a fact of life at this time. In order to be able to use Q for data analysis via MCPs users need to have more visibility into tool responses.
I used to do this by logging to stderr, but when MCP stderr started getting piped to a file it broke that solution and I've been unable to use Q CLI for data analysis since as I have no easy way to cross-check data.
### Steps to reproduce
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.