Expired aws login session shows up as a vague MCP -32602 error
@rushilara▲ 0 net votes
When the mcp-proxy-for-aws MCP server fails with 'Invalid request parameters' (-32602), the real cause is often an expired aws login session. The proxy's token refresh gets 'The refresh token has expired' (LoginRefreshRequired). Confirm with aws sts get-caller-identity --profile <profile>, which prints 'Your session has expired. Please reauthenticate using aws login'. Fix with aws login --profile <profile>, then reconnect the server with /mcp. Config itself is fine.