Can my AI agent directly run RAG without calling external LLMs?

Yes! Use the `retrieve_and_generate` capability. Your agent passes the query and a designated Bedrock model ARN. Bedrock handles fetching chunks from the local vector index and synthesizing the final answer inside AWS boundaries, returning a fully grounded response instantly.

How can I check if new uploaded documents are successfully indexed in my agent?

Just ask your agent to list ingestion jobs for a specific Knowledge Base ID and Data Source ID. It will report back the exact status (e.g., SYNCING, COMPLETED, FAILED) of chunks being mapped to your vector layout.

Can I see exactly where an answer came from in my documentation?

Absolutely. Both the standard `retrieve` functionality and `retrieve_and_generate` calls will parse out the specific origin document URLs (e.g., S3 paths) and expose the exact raw text snippets that mathematically matched your query vector.

Amazon Bedrock KB MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: Amazon Bedrock KB
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to Amazon Bedrock KB through the Vinkius — pass the Edge URL in the `mcps` parameter and every Amazon Bedrock KB tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Amazon Bedrock KB Specialist",
    goal="Help users interact with Amazon Bedrock KB effectively",
    backstory=(
        "You are an expert at leveraging Amazon Bedrock KB tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Amazon Bedrock KB "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Amazon Bedrock KB MCP Server

Connect your Amazon Bedrock account to any AI agent and empower it with managed vector databases, enterprise RAG workflows, and semantic search directly inside AWS.

When paired with CrewAI, Amazon Bedrock KB becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Amazon Bedrock KB tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Managed RAG — Generate grounded LLM responses using internal document sets in a single explicit call
Semantic Retrieval — Query vector indexes to retrieve exact top-K text chunks and their origin document URLs
Data Sources — Inspect and paginate attached storage buckets feeding the knowledge base
Ingestion Jobs — Track real-time syncing status of chunking pipelines mapping documents across the vector layout
Knowledge Base Introspection — List available vector stores and exact embedding models assigned directly to your region

The Amazon Bedrock KB MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Amazon Bedrock KB to CrewAI via MCP

Follow these steps to integrate the Amazon Bedrock KB MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 6 tools from Amazon Bedrock KB

Why Use CrewAI with the Amazon Bedrock KB MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Amazon Bedrock KB through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Amazon Bedrock KB + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Amazon Bedrock KB MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Amazon Bedrock KB for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Amazon Bedrock KB, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Amazon Bedrock KB tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Amazon Bedrock KB against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Amazon Bedrock KB MCP Tools for CrewAI (6)

These 6 tools become available when you connect Amazon Bedrock KB to CrewAI via MCP:

get_knowledge_base

Get an explicit AWS Bedrock knowledge base

list_data_sources

List Data Sources bound explicitly to an AWS Bedrock KB

list_ingestion_jobs

List AWS Bedrock KB explicit sync operations

list_knowledge_bases

List AWS Bedrock knowledge bases

retrieve

Query a vector index securely via AWS Bedrock

retrieve_and_generate

Generate explicitly grounded LLM responses using Bedrock KB

Example Prompts for Amazon Bedrock KB in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Amazon Bedrock KB immediately.

"Which knowledge bases and embedding models do I have setup?"

"Run a retrieval query for 'onboarding process checklist' on my KB and show me the top 3 snippets."

"Check the status of the S3 ingestion job for my Documentation bucket."

Troubleshooting Amazon Bedrock KB MCP Server with CrewAI

Common issues when connecting Amazon Bedrock KB to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Amazon Bedrock KB + CrewAI FAQ

Common questions about integrating Amazon Bedrock KB MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.