Skip to content

AWS Knowledge MCP Server endpoint returning 404 error #177

@ajitnk-lab

Description

@ajitnk-lab

Issue Description

The aws-knowledge-mcp-server configured in Amazon Q CLI is failing to load with a connection closed error during initialization. The remote endpoint https://knowledge-mcp.global.api.aws is returning a 404 error.

Configuration

The server is configured in ~/.aws/amazonq/mcp.json as:

"aws-knowledge-mcp-server": {
  "type": "stdio",
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://knowledge-mcp.global.api.aws"
  ],
  "env": {
    "NODE_OPTIONS": "--max-old-space-size=1024",
    "FASTMCP_LOG_LEVEL": "ERROR"
  },
  "timeout": 120000,
  "disabled": false
}

Error Details

Q CLI Log Error:

Error loading server aws-knowledge-mcp-server: McpError(ErrorData { code: ErrorCode(-32002), message: "connection closed: initialize response", data: None })

HTTP Response:

$ curl -I https://knowledge-mcp.global.api.aws
HTTP/2 404 
date: Wed, 29 Oct 2025 07:20:59 GMT
x-amzn-requestid: 76cbdafc-26d3-4c7c-8ada-be07d3730b50
x-cache: Error from cloudfront
via: 1.1 3caf9df4ca497afd40efb87f8957a7fa.cloudfront.net (CloudFront)
x-amz-cf-pop: HIO52-P4
x-amz-cf-id: eiMTzNZCUaKEuPIKjQ2wq_eL8QrxAN4hhS6bTyiD4ru_e7GGyEsLXQ==

Environment

  • mcp-remote version: 0.1.29 (latest)
  • Node.js version: v20.19.5
  • OS: Linux (Ubuntu)
  • AWS CLI: Configured and working (credentials verified)

Expected Behavior

The AWS Knowledge MCP server should successfully initialize and provide knowledge base functionality.

Actual Behavior

The server fails to initialize due to the remote endpoint returning a 404 error, causing the MCP server to fail loading in Q CLI.

Questions

  1. Is https://knowledge-mcp.global.api.aws the correct endpoint for the AWS Knowledge MCP server?
  2. Is this service currently available or has it been deprecated?
  3. Are there alternative endpoints or authentication requirements?
  4. Should this be reported to AWS instead of the mcp-remote project?

Workaround

Currently disabling the server in the configuration to avoid initialization errors:

"disabled": true

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions