Skip to main content
aitoolsatlas.ai
BlogAbout

Explore

  • All Tools
  • Comparisons
  • Best For Guides
  • Blog

Company

  • About
  • Contact
  • Editorial Policy

Legal

  • Privacy Policy
  • Terms of Service
  • Affiliate Disclosure
Privacy PolicyTerms of ServiceAffiliate DisclosureEditorial PolicyContact

© 2026 aitoolsatlas.ai. All rights reserved.

Find the right AI tool in 2 minutes. Independent reviews and honest comparisons of 875+ AI tools.

  1. Home
  2. Tools
  3. Amazon Bedrock Knowledge Base Retrieval MCP Server
OverviewPricingReviewWorth It?Free vs PaidDiscountAlternativesComparePros & ConsIntegrationsTutorialChangelogSecurityAPI
Integrations
A

Amazon Bedrock Knowledge Base Retrieval MCP Server

Open-source Model Context Protocol server that enables AI assistants to query and analyze Amazon Bedrock Knowledge Bases using natural language. Optimize enterprise knowledge retrieval with citation support, data source filtering, reranking, and IAM-secured access for RAG applications.

Starting at$0
Visit Amazon Bedrock Knowledge Base Retrieval MCP Server →
💡

In Plain English

Open-source Model Context Protocol server that enables AI assistants to query and analyze Amazon Bedrock Knowledge Bases using natural...

OverviewFeaturesPricingGetting StartedUse CasesLimitationsFAQ

Overview

The Amazon Bedrock Knowledge Base Retrieval MCP Server is an open-source implementation of the Model Context Protocol (MCP) maintained by AWS Labs. It bridges AI assistants and coding agents (such as Claude Desktop, Cursor, Cline, and Amazon Q Developer) with Amazon Bedrock Knowledge Bases, enabling them to perform retrieval-augmented generation (RAG) against enterprise data stored in AWS without writing custom integration code.

At its core, the server exposes a small set of MCP tools that let an AI client discover available knowledge bases, list their underlying data sources (S3 buckets, Confluence, SharePoint, Salesforce, web crawlers, etc.), and run natural-language queries against them. Results are returned with citations pointing back to the original source documents, which is essential for verifiable answers in regulated and enterprise settings. The server supports filtering by data source so that a single knowledge base containing multiple repositories can be queried selectively, and it integrates with Amazon Bedrock's reranking models to push the most relevant chunks to the top of the result set before they reach the LLM.

Because the server runs locally (typically launched via uvx or a similar Python runner) and authenticates using standard AWS credentials, all access to knowledge bases is governed by IAM policies. This means existing access controls, audit logging via CloudTrail, and VPC networking constraints continue to apply — the MCP server does not introduce a new authorization layer. Knowledge bases must be tagged with mcp-multirag-kb=true to be discoverable, giving administrators a simple opt-in mechanism for which corpora are exposed to AI agents.

The server is designed for developers building agentic applications, internal copilots, customer support assistants, and documentation chatbots that need grounded, citation-backed responses from proprietary data. It removes a significant amount of boilerplate around the Bedrock Agent Runtime APIs (Retrieve and RetrieveAndGenerate) and standardizes the contract so that any MCP-compatible client can consume the same knowledge base with no client-specific code. As part of the broader awslabs/mcp project on GitHub, it is released under the Apache 2.0 license and ships alongside companion servers for Bedrock AgentCore, SageMaker, Amazon Q Index, and other AWS AI services, making it a natural building block for teams already standardized on AWS.

🎨

Vibe Coding Friendly?

▼
Difficulty:intermediate

Suitability for vibe coding depends on your experience level and the specific use case.

Learn about Vibe Coding →

Was this helpful?

Key Features

  • •Natural language querying of Amazon Bedrock Knowledge Bases
  • •Citation support for all retrieved results with source attribution
  • •Data source filtering and prioritization capabilities
  • •Result reranking using Amazon Bedrock's advanced algorithms
  • •Knowledge base discovery and exploration tools

Pricing Plans

Open Source (Server)

$0

  • ✓Apache 2.0 licensed source on GitHub (awslabs/mcp)
  • ✓Self-hosted; runs locally via uvx or Docker
  • ✓No license, subscription, or seat fees
  • ✓Works with any MCP-compatible client (Claude Desktop, Cursor, Cline, Amazon Q Developer, etc.)

AWS Usage (Pay-as-you-go)

Variable

  • ✓Amazon Bedrock Knowledge Base storage and query charges
  • ✓Embedding model invocation costs (e.g., Titan, Cohere)
  • ✓Vector store costs (OpenSearch Serverless, Aurora, Pinecone, etc.)
  • ✓Optional reranking model charges
  • ✓Data ingestion and S3 storage charges for source documents
See Full Pricing →Free vs Paid →Is it worth it? →

Ready to get started with Amazon Bedrock Knowledge Base Retrieval MCP Server?

View Pricing Options →

Getting Started with Amazon Bedrock Knowledge Base Retrieval MCP Server

  1. 1Ensure you have Python 3.10+ installed and AWS CLI configured with appropriate credentials and profile
  2. 2Set up Amazon Bedrock Knowledge Base in your AWS account and tag with 'mcp-multirag-kb=true' for server discovery
  3. 3Install the MCP server using 'uvx awslabs.bedrock-kb-retrieval-mcp-server@latest' and configure your AI assistant (Kiro, Cursor, VS Code, Claude Desktop) to use the server
  4. 4Configure environment variables including AWS_PROFILE, AWS_REGION, and optional settings like KB_INCLUSION_TAG_KEY for filtering
  5. 5Test the integration by querying your knowledge base through your configured AI assistant and verify citation support is working correctly
Ready to start? Try Amazon Bedrock Knowledge Base Retrieval MCP Server →

Best Use Cases

🎯

Enterprise development teams using AWS who want their AI coding assistants (Cursor, VS Code, Kiro) to automatically pull in internal API documentation, coding standards, and architectural guidelines while writing code

⚡

DevOps and platform engineering teams querying runbooks, incident response procedures, and infrastructure documentation through AI assistants during incident triage without switching tools

🔧

Compliance and security teams enabling AI assistants to search policy documents, regulatory frameworks, and audit requirements stored in Bedrock Knowledge Bases with full citation trails for accountability

🚀

Technical writers and documentation teams using AI assistants to cross-reference and verify information across multiple knowledge bases when updating or creating new documentation

💡

Onboarding workflows where new engineers use AI assistants to query internal knowledge bases about project architecture, deployment processes, and team conventions in natural language

🔄

Multi-team organizations standardizing knowledge access across different AI tools—some teams using Cursor, others VS Code or Kiro—while maintaining consistent retrieval from the same Bedrock Knowledge Bases

Limitations & What It Can't Do

We believe in transparent reviews. Here's what Amazon Bedrock Knowledge Base Retrieval MCP Server doesn't handle well:

  • ⚠Results with IMAGE content type are not included in knowledge base query responses, limiting usefulness for diagram-heavy documentation
  • ⚠Reranking functionality requires additional IAM permissions, Bedrock model access enablement, and is only available in specific AWS regions
  • ⚠Knowledge bases must be pre-tagged with 'mcp-multirag-kb=true' to be discoverable—existing untagged knowledge bases require manual tagging
  • ⚠AWS credentials must be kept refreshed on the host when running via Docker, adding operational overhead for containerized deployments
  • ⚠Cannot query non-AWS knowledge systems; all content must be ingested into Amazon Bedrock Knowledge Bases first

Pros & Cons

✓ Pros

  • ✓Officially maintained by AWS Labs under the awslabs/mcp GitHub org, with active issue triage and alignment to current Bedrock APIs
  • ✓Returns citations with every retrieval, making answers auditable and suitable for regulated industries
  • ✓Supports data source filtering so a single multi-source knowledge base can be queried selectively without separate KBs
  • ✓Inherits AWS IAM, CloudTrail, and VPC controls — no new auth layer to manage or audit
  • ✓Optional integration with Bedrock reranking models improves relevance over raw vector similarity
  • ✓Standard MCP interface works across Claude Desktop, Cursor, Cline, Amazon Q Developer and other compliant clients

✗ Cons

  • ✗Hard dependency on AWS — only useful if your knowledge bases already live in Amazon Bedrock
  • ✗Requires the `mcp-multirag-kb=true` tag on knowledge bases for discovery, which is easy to forget and not obvious from error messages
  • ✗No built-in write/ingest tooling; document loading and KB sync must be handled separately (e.g., via the Document Loader MCP Server or AWS console)
  • ✗Local-process model means each developer needs AWS credentials configured, which complicates rollout in larger teams without SSO/identity center setup
  • ✗Documentation assumes familiarity with Bedrock Knowledge Bases concepts (data sources, chunking, embeddings) — limited hand-holding for first-time RAG users

Frequently Asked Questions

What is the Model Context Protocol and why does it matter?+

The Model Context Protocol (MCP) is an open standard developed by Anthropic for connecting AI assistants to external data sources. It has been adopted by major AI platforms including OpenAI, Google DeepMind, Microsoft, and thousands of developers. MCP provides a standardized way for AI assistants to access real-world data and tools, eliminating the need for custom integrations. This means you configure the server once and it works across Kiro, Cursor, VS Code, Claude Desktop, and other MCP-compatible tools without building separate plugins for each.

Do I need an existing Amazon Bedrock Knowledge Base to use this server?+

Yes, you must have at least one Amazon Bedrock Knowledge Base already set up and configured in your AWS account. The MCP server connects to existing knowledge bases rather than creating new ones. Your knowledge base must be tagged with the key 'mcp-multirag-kb' set to a value of 'true' for the server to discover and access it. You can also use the KB_INCLUSION_TAG_KEY environment variable to specify a custom tag key for filtering which knowledge bases are exposed to the server.

How do I install and configure the server for my AI assistant?+

Installation uses Python's uv package manager. First install uv from Astral, then install Python 3.10 via 'uv python install 3.10'. Configure the server in your AI assistant's MCP settings file by pointing to the 'awslabs.bedrock-kb-retrieval-mcp-server@latest' package via uvx. You'll need to set environment variables for AWS_PROFILE, AWS_REGION, and optionally BEDROCK_KB_RERANKING_ENABLED. Docker-based installation is also supported for containerized environments, though you'll need to manage AWS credential refresh on the host.

What are the ongoing costs for using this server?+

The MCP server software is completely free and open source. However, you will incur AWS service costs including Amazon Bedrock Knowledge Base query charges, vector database costs (OpenSearch Serverless, etc.), S3 storage costs for your data sources, and optional reranking model inference costs when that feature is enabled. Costs scale with usage volume, so light development use may be minimal while heavy production querying across large knowledge bases will increase proportionally.

How does reranking work and should I enable it?+

Reranking uses Amazon Bedrock's foundation models to re-score and reorder retrieval results by relevance to your query, improving the quality of information surfaced to your AI assistant. It is disabled by default (BEDROCK_KB_RERANKING_ENABLED=false) because it requires additional IAM permissions for bedrock:Rerank and bedrock:InvokeModel actions, model access enablement in your region, and incurs extra inference costs. Enable it when result quality is critical—such as querying complex technical documentation—and disable it for cost-sensitive or latency-sensitive use cases. Individual API calls can override the global setting.
🦞

New to AI tools?

Read practical guides for choosing and using AI tools

Read Guides →

Get updates on Amazon Bedrock Knowledge Base Retrieval MCP Server and 370+ other AI tools

Weekly insights on the latest AI tools, features, and trends delivered to your inbox.

No spam. Unsubscribe anytime.

What's New in 2026

In 2026, the awslabs/mcp project has expanded around this server with companion servers for Bedrock AgentCore, SageMaker AI, Amazon Q Index, and a dedicated Document Loader MCP Server, letting teams pair retrieval with ingestion and agent orchestration entirely through MCP. The Bedrock KB server itself has tracked recent Bedrock Agent Runtime updates including expanded reranking model support, finer-grained metadata filters, and improved handling of multi-source knowledge bases. The broader AWS Labs MCP catalog now ships with installation guidance for Cursor, Cline, Claude Desktop, and Amazon Q Developer, reflecting MCP's rapid adoption as the default integration surface for enterprise AI assistants.

User Reviews

No reviews yet. Be the first to share your experience!

Quick Info

Category

Integrations

Website

awslabs.github.io/mcp/servers/bedrock-kb-retrieval-mcp-server
🔄Compare with alternatives →

Try Amazon Bedrock Knowledge Base Retrieval MCP Server Today

Get started with Amazon Bedrock Knowledge Base Retrieval MCP Server and see if it's the right fit for your needs.

Get Started →

Need help choosing the right AI stack?

Take our 60-second quiz to get personalized tool recommendations

Find Your Perfect AI Stack →

Want a faster launch?

Explore 20 ready-to-deploy AI agent templates for sales, support, dev, research, and operations.

Browse Agent Templates →

More about Amazon Bedrock Knowledge Base Retrieval MCP Server

PricingReviewAlternativesFree vs PaidPros & ConsWorth It?Tutorial