AWS Knowledge MCP server for AI apps

What your AI apps can do with AWS Knowledge

Search and read AWS documentation
Check regional service availability

AWS Knowledge MCP tools

5 tools, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does	Suggested rule
`aws___read_documentation`	Fetch full AWS doc pages as markdown. `search_documentation` already returns verbatim page chunks, so don't re-read a URL whose chunk you already have to "confirm" or "round out" an answer -- the chunk is the real page text; treat it as authoritative.	Allow (read-only)
`aws___search_documentation`	AWS docs search. Each result's `context` is verbatim page text -- a real chunk of the actual page, not a short snippet -- and usually already contains the answer, so answer directly from it. Use `read_documentation` only when the chunks genuinely lack the needed detail.	Allow (read-only)
`aws___list_regions`	Retrieve a list of all AWS regions.	Allow (read-only)
`aws___get_regional_availability`	AWS resource availability per region.	Allow (read-only)
`aws___retrieve_skill`	Retrieve an AWS skill (workflows, references). Returns SKILL.md, or `file` if given.	Allow (read-only)

Suggested access for each AI app

5 tools marked read-only (aws___read_documentation, aws___search_documentation, aws___list_regions, aws___get_regional_availability, aws___retrieve_skill). These are usually safe to allow.

These are hints the server reports about its own tools, not guarantees.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same AWS Knowledge connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add AWS Knowledge to a workspace (no sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every AWS Knowledge tool, give Cursor only the read tools, or keep AWS Knowledge away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the AWS Knowledge MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect AWS Knowledge in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Amazon Web Services endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http aws-knowledge 'https://knowledge-mcp.global.api.aws'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "aws-knowledge": {
      "url": "https://knowledge-mcp.global.api.aws"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Amazon Web Services MCP documentation for what your client needs.

Before you connect

No account needed.

Server details

Detail	Value
Publisher	Amazon Web Services
Endpoint	`https://knowledge-mcp.global.api.aws`
Authentication	No sign-in
Categories	Development
Tool list	5 tools, observed 29 October 2026 (discovery)

Amazon Web Services MCP documentation

AWS Knowledge MCP server for Claude, Codex and Cursor