AWS Knowledge MCP setup: documentation and regions

A documentation question and a question about your own AWS account require different evidence. Begin here with a public service feature. Record the service name, target region and exact question. This makes it easier to tell whether the answer applies to the application you are planning.

Connect AWS Knowledge over HTTP

AWS documents https://knowledge-mcp.global.api.aws as a remote Streamable HTTP endpoint. According to AWS, the Knowledge connection requires neither authentication nor an AWS account, although request limits apply. The example connects that documentation service to VS Code.

{
  "servers": {
    "aws-knowledge": {
      "type": "http",
      "url": "https://knowledge-mcp.global.api.aws"
    }
  }
}

Save the configuration in .vscode/mcp.json or add the entry to an existing servers object. Start the connection and inspect its tool list. The VS Code guide helps with the initial entry; this HTTP example does not use an additional local proxy.

Match documentation to regional information

The provider documents tools including search_documentation, read_documentation, list_regions and get_regional_availability. Choose the request around the question. A general service description does not establish the availability of a particular feature in a particular region.

Check the first regional question

1. Choose a familiar service and one feature. Record a complete region identifier so the question does not drift between locations with similar names.

2. Search for the relevant public documentation. Retrieve the specific source passage and keep its full address in your notes.

3. Check regional availability for the same service and feature. Compare the response with the region in your original question.

4. Keep a short record of the service, feature, region, source and retrieval date. If you use the result to plan a setup, check account requirements as a separate step.

Recognise the limits of a documentation answer

Finding instructions does not tell you which resources exist in your account. Keep this connection separate from one that calls AWS APIs on your behalf. The documentation server comparison helps with source selection; permissions planning helps prepare a later account connection.

Must I put AWS keys in the configuration?

AWS states that this Knowledge endpoint does not require authentication. The example therefore includes no AWS keys. Other AWS MCP servers can have different requirements.

Does a regional answer prove my account can access it?

No. Keep public availability, account enablement and your own permissions separate. Those questions can have different answers even for the same service and region.

What if the response only describes the service generally?

Make the question more specific by naming the feature and region. A general product description cannot replace evidence for the regional property you need.

Why does a repeated request fail?

Check the error message, time and possible request limits. Avoid rapid retry loops and do not change several connection settings at the same time.

Use the AWS Knowledge registry search for additional declarations. Compare the endpoint and sources before selecting an entry with a similar name.

Vendor documentation read on 3 October 2026. Run the proposed checks in your own environment.

1. AWS: Knowledge MCP connection and tools
   Show retrieval command

   curl -s https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server
2. AWS: MCP server overview
   Show retrieval command

   curl -s https://github.com/awslabs/mcp
3. VS Code: MCP configuration
   Show retrieval command

   curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers

All posts