AWS Support MCP Server: Incorrect uvx command syntax (drafted by Amazon Q Developer)
Describe the issue
Bug Description
The documentation or examples for the AWS Support MCP Server show incorrect uvx command syntax that prevents the server from starting.
Incorrect Syntax (Current)
{
"mcpServers": {
"awslabs_support_mcp_server": {
"command": "uvx",
"args": [
"-m", "awslabs.aws-support-mcp-server@latest",
"--debug",
"--log-file",
"./logs/mcp_support_server.log"
],
"env": {
"AWS_PROFILE": "your-aws-profile"
}
}
}
}
Correct Syntax (Should be)
{
"mcpServers": {
"awslabs_support_mcp_server": {
"command": "uvx",
"args": [
"--from", "awslabs.aws-support-mcp-server@latest",
"awslabs.aws-support-mcp-server",
"--debug",
"--log-file",
"./logs/mcp_support_server.log"
],
"env": {
"AWS_PROFILE": "your-aws-profile"
}
}
}
}
Issue Details
• uvx doesn't support the -m flag (that's a Python convention) • The correct uvx syntax is uvx --from package@version executable-name • The executable name is awslabs.aws-support-mcp-server, not aws-support-mcp-server
Environment
• uvx version: 0.8.9 • Platform: macOS
Impact
MCP server fails to start with the incorrect syntax, preventing users from using AWS Support API functionality.
Links
https://awslabs.github.io/mcp/servers/aws-support-mcp-server
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. If you wish to exclude this issue from being marked as stale, add the "backlog" label.