2,500+ MCP servers ready to use
Vinkius

R2R MCP Server for CrewAI 6 tools — connect in under 2 minutes

Built by Vinkius GDPR 6 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="R2R Specialist",
    goal="Help users interact with R2R effectively",
    backstory=(
        "You are an expert at leveraging R2R 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 R2R "
        "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)
R2R
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 R2R MCP Server

Connect your R2R (Rag to Riches) deployment to an AI agent, bringing your RAG infrastructure inside your chat interface. By linking this server, the AI can query its own constructed knowledge base on demand.

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

What you can do

  • Vector Search — Perform semantic similarity queries across your document database to retrieve contextually relevant chunks of information.
  • Execute RAG Queries — Use the 'rag_query' endpoint to have the R2R server directly summarize information based on vector data.
  • Knowledge Management — Call the API to list ingested documents, read metadata attributes, and filter logical collections.
  • Instance Health Monitoring — Quickly ping the connection using health checks to verify your system is responsive.

The R2R 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 R2R to CrewAI via MCP

Follow these steps to integrate the R2R MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py. CrewAI auto-discovers 6 tools from R2R

Why Use CrewAI with the R2R MCP Server

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

01

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

02

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

03

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

04

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

R2R + CrewAI Use Cases

Practical scenarios where CrewAI combined with the R2R MCP Server delivers measurable value.

01

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

02

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

03

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

04

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

R2R MCP Tools for CrewAI (6)

These 6 tools become available when you connect R2R to CrewAI via MCP:

01

get_document

Retrieves details for a specific document

02

get_health

Checks the health status of the R2R server

03

list_collections

Lists all document collections

04

list_documents

Lists all ingested documents in the R2R system

05

rag_query

Executes a RAG (Retrieval-Augmented Generation) query

06

search

Performs a vector search across ingested documents

Example Prompts for R2R in CrewAI

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

01

"Perform a vector search for 'Company Holiday Policy 2026'."

02

"Query the RAG engine to summarize known advanced RAG chunking strategies."

03

"Verify the operational health of the R2R server."

Troubleshooting R2R MCP Server with CrewAI

Common issues when connecting R2R to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

Rate limiting or 429 errors

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

R2R + CrewAI FAQ

Common questions about integrating R2R MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect R2R to CrewAI

Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.