Adding AWS MSK MCP server to mcp.json breaks Amazon Q CLI with ValidationException
Adding awslabs.aws-msk-mcp-server to ~/.aws/amazonq/mcp.json on macOS makes Amazon Q CLI fail on every prompt, including a simple hello, with "ValidationException: Improperly formed request." Is there a fix, or is disabling the MSK server entry the only workaround?
Originally asked on GitHub: https://github.com/awslabs/mcp/issues/912
4 answers
Unresolved: the issue was closed as not planned in January 2026 after being marked stale, and no maintainer confirmed a fix. A contributor said they opened a pull request to address it, and a later comment linked PR #1118, but the thread does not confirm the fix landed.
The failure reproduces on macOS when
awslabs.aws-msk-mcp-serveris added to~/.aws/amazonq/mcp.json. Every prompt — even a first "hello" — fails with:Amazon Q is having trouble responding right now: 0: unhandled error (ValidationException) 3: Error { code: "ValidationException", message: "Improperly formed request.", aws_request_id: "..." }The reported config was:
json{ "mcpServers": { "awslabs.core-mcp-server": { "command": "uvx", "args": ["awslabs.core-mcp-server@latest"] }, "awslabs.aws-msk-mcp-server": { "command": "uvx", "args": ["awslabs.aws-msk-mcp-server@latest", "--allow-writes"], "env": { "FASTMCP_LOG_LEVEL": "ERROR" }, "disabled": false, "autoApprove": [] } } }The only workaround reported in the thread is to disable or delete the MSK server entry; Q CLI then works again, at the cost of not being able to use that server. Switching Q CLI models between Sonnet 3.5, 3.7, and 4 did not help, and no root cause was given in the thread. General advice: when testing MCP servers, add them one at a time so a single failing server doesn't break the whole client.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Configured awslabs.aws-msk-mcp-server (uvx awslabs.aws-msk-mcp-server@latest --allow-writes, FASTMCP_LOG_LEVEL=ERROR) alongside awslabs.core-mcp-server in ~/.aws/amazonq/mcp.json. Q CLI then failed on every prompt with ValidationException "Improperly formed request."
Source: https://github.com/awslabs/mcp/issues/912 (opens external site)
Did this work for you?What @aarjvi17 tried on GitHub (Didn't work)
Switched Q CLI models between Sonnet 3.5, 3.7, and 4. The ValidationException persisted.
Source: https://github.com/awslabs/mcp/issues/912#issuecomment-3105197433 (opens external site)
Did this work for you?What @rajatechai tried on GitHub (Worked)
Disabled or deleted the awslabs.aws-msk-mcp-server entry from mcp.json. Q CLI worked again, but the MSK MCP server could no longer be used.
Source: https://github.com/awslabs/mcp/issues/912#issuecomment-3150890162 (opens external site)
Did this work for you?
Related questions
- AWS Diagram MCP server: generate_diagram fails with No module named 'sarif_om'
- DynamoDB MCP server fails: FastMCP.__init__() got an unexpected keyword argument 'version'
- AWS MCP server not using AWS_CONTAINER_AUTHORIZATION_TOKEN when run via Docker MCP Toolkit?
- EKS MCP server: how to switch AWS profiles or Kubernetes contexts dynamically?
- postgres-mcp-server: run_query fails with "No database connection available"