MCP server for AWS Knowledge Base retrieval using Bedrock Agent Runtime
MCP Aws Kb MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Aws Kb directly instead of describing what you should do. MCP server for AWS Knowledge Base retrieval using Bedrock Agent Runtime.
Once MCP Aws Kb is connected, these are the calls the assistant has available:
retrieve_from_aws_kb — Perform retrieval operations using the AWS Knowledge BaseInputs — - query (string): The search query for retrievalYou will need 5 environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REGION, AWS_KB_IDS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as with, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Aws Kb's toolset — retrieve_from_aws_kb, Inputs — is a fair guide to whether it matches your workflow. It is maintained by sammcj; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Aws Kb's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| retrieve_from_aws_kb | Perform retrieval operations using the AWS Knowledge Base. |
| Inputs | - query (string): The search query for retrieval. |
{
"mcpServers": {
"aws-kb-retrieval": {
"command": "docker",
"args": [ "run", "-i", "--rm", "-e", "AWS_ACCESS_KEY_ID", "-e", "AWS_SECRET_ACCESS_KEY", "-e", "AWS_REGION", "-e", "AWS_KB_IDS", "mcp/aws-kb-retrieval-server" ],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_ACCESS_KEY_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_SECRET_ACCESS_KEY_HERE",
"AWS_SESSION_TOKEN": "YOUR_OPTIONAL_SESSION_ID_FOR_SSO_TEMPORARY_CREDENTIALS_HERE",
"AWS_REGION": "YOUR_AWS_REGION_HERE",
"AWS_KB_IDS": "[\"kb-12345\", \"kb-67890\"]"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| AWS_SESSION_TOKEN | Credential the server authenticates with. | Yes |
| AWS_REGION | Configuration value read at startup. | Optional |
| AWS_KB_IDS | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.