Amazon Bedrock Knowledge Base Retrieval MCP Server: Free vs Paid — Is the Free Plan Enough?

⚡ Quick Verdict

Stay free if you only need apache 2.0 licensed source on github (awslabs/mcp) and self-hosted; runs locally via uvx or docker. Upgrade if you need amazon bedrock knowledge base storage and query charges and embedding model invocation costs (e.g., titan, cohere). Most solo builders can start free.

Try Free Plan →Compare Plans ↓

Who Should Stay Free vs Who Should Upgrade

👤

Stay Free If You're...

✓Individual user
✓Basic needs only
✓Personal projects
✓Getting started
✓Budget-conscious

👤

Upgrade If You're...

✓Business professional
✓Advanced features needed
✓Team collaboration
✓Higher usage limits
✓Premium support

What Users Say About Amazon Bedrock Knowledge Base Retrieval MCP Server

👍 What Users Love

✓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

👎 Common Concerns

⚠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

🔒 What Free Doesn't Include

🎯 Amazon Bedrock Knowledge Base storage and query charges

Why it matters: Hard dependency on AWS — only useful if your knowledge bases already live in Amazon Bedrock

Available from: AWS Usage (Pay-as-you-go)

🎯 Embedding model invocation costs (e.g., Titan, Cohere)

Why it matters: Requires the `mcp-multirag-kb=true` tag on knowledge bases for discovery, which is easy to forget and not obvious from error messages

Available from: AWS Usage (Pay-as-you-go)

🎯 Vector store costs (OpenSearch Serverless, Aurora, Pinecone, etc.)

Why it matters: 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)

Available from: AWS Usage (Pay-as-you-go)

🎯 Optional reranking model charges

Why it matters: Local-process model means each developer needs AWS credentials configured, which complicates rollout in larger teams without SSO/identity center setup

Available from: AWS Usage (Pay-as-you-go)

🎯 Data ingestion and S3 storage charges for source documents

Why it matters: Documentation assumes familiarity with Bedrock Knowledge Bases concepts (data sources, chunking, embeddings) — limited hand-holding for first-time RAG users

Available from: AWS Usage (Pay-as-you-go)

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.

Ready to Try Amazon Bedrock Knowledge Base Retrieval MCP Server?

Start with the free plan — upgrade when you need more.

Get Started Free →