← Explore all mcp servers

DOCUMENTATION SEARCH / Amazon Web Services

AWS Knowledge MCP

Retrieves official AWS documentation, regional availability and task guidance without granting access to an AWS account.

“The Knowledge MCP server does not require authentication but is subject to rate limits.”

01 / THE REASONING

Why this made the selection.

  • The page describes a remote general-availability server for AWS documentation, code samples, agent skills, and regional availability, reached at a public Streamable HTTP URL.
  • It says the endpoint does not require authentication or an AWS account, which is a different boundary from the local AWS Labs servers that call account APIs.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server (setup, access and capability sections)
  • https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server

Our findings

  • The documented tools retrieve documentation, regions, availability and skills; they do not manage AWS account resources.
  • The guide provides a Kiro-specific JSON example and warns that client configuration formats differ.
  • The page presents a fully managed remote server for documentation, code samples, agent skills, and regional availability of AWS APIs and CloudFormation resources, and it says that server is in general availability.
  • Clients are told to use Streamable HTTP against https://knowledge-mcp.global.api.aws. The server does not require authentication or an AWS account, but it is rate limited and requires public internet access.
  • The page says not every MCP client supports remote servers. Telemetry collected through the server is not used for machine learning model training or improvement.

Not established by this review

  • Authentication, service availability and tool execution were not tested.
  • The hosted implementation source and licence were not established.
  • The server was not started and its tools were not called.
  • A pin does not verify transitive dependencies.
  • No tools/list or tool call was made.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Add https://knowledge-mcp.global.api.aws using a client that supports Streamable HTTP.
  2. Use the documented proxy only if the client cannot connect remotely.

Before you start

  • Network access and a compatible MCP client; no AWS account is required.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "aws-knowledge-mcp-server": {
      "url": "https://knowledge-mcp.global.api.aws",
      "type": "http",
      "disabled": false
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server

    Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample

Evidence & Ask