An astronaut overseeing a futuristic data hub

Connect R2R to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Give your AI agent direct access to your document knowledge base.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 6 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through R2R.

  1. 01

    Search

    This capability performs a vector search across your ingested documents to find semantically relevant information.

  2. 02

    Rag query

    This capability executes a full RAG query to generate responses based on your retrieved vector data.

  3. 03

    List documents

    This capability pulls a list of all documents currently ingested in your R2R system.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through R2R.

  1. 04

    Get document

    This capability retrieves specific metadata and details for a single document.

  2. 05

    Get health

    This capability checks the connection status to ensure your R2R instance is responsive.

  3. 06

    List collections

    This capability shows you all the document collections you have organized in the system.

Real work

What teams actually run

01

RAG Debugging

Test how your agent retrieves specific information by running vector searches directly in your IDE.

02

Knowledge Auditing

Check your document collections and metadata to ensure your knowledge base is up to date.

03

Automated Summarization

Ask your agent to summarize large datasets by triggering RAG queries against your R2R engine.

04

System Health Checks

Quickly confirm your R2R deployment is online and responding to requests.

Automate a task

Put R2R to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

R2R works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put R2R to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

850ms average. Fast in production.

R2R is checked daily against the live service.

Daily averagePeak 1133ms
Oct 3Today
Fastest day
693ms
Slowest day
1133ms
14-day trend
Slowing+28%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of R2R, so you can see the experience inside your AI.

It does not authenticate your account with R2R. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

R2R Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_Psy9XiP4IhGY7SchHirciLtxL89aKlE6LAoJStd2/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — R2R capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "r2r-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Psy9XiP4IhGY7SchHirciLtxL89aKlE6LAoJStd2/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up R2R in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work R2R owners hand off.

This MCP is built for technical users who already run R2R and want to use that data within their AI workflows.

  • 01

    AI and ML Engineers

    They use the MCP to query vector instances directly through their AI client instead of using external scripts.

  • 02

    Data Custodians

    They use the capability to browse metadata and verify that document ingestions were successful.

  • 03

    Backend Developers

    They use the connection to audit engine responses and test semantic retrieval limits.

FAQ

Questions R2R owners ask.

  • 01

    What do I need to connect this MCP?

    You need your R2R Base URL and an Auth Key if your deployment requires authentication.

  • 02

    Which AI clients can I use with this?

    You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    How does the agent access my documents?

    The agent uses the search and rag_query capabilities to interact with your R2R vector database.

  • 04

    Can I see what documents are in my system?

    Yes, you can use the list_documents capability to see all ingested files or get_document to see specific details.

  • 05

    Is my data hosted by Vinkius?

    Vinkius hosts the MCP connection and manages the credentials, but the data remains in your R2R deployment.

  • 06

    What URL should I use for the R2R API URL?

    If you are running R2R locally via Docker, it's typically http://localhost:7272. If you are using SciPhi Cloud or have it deployed on your own infrastructure, provide the exact public or private endpoint.

  • 07

    Do I need an R2R API Key?

    It depends on your deployment. Open deployments for local testing may not require a key. Production deployments or SciPhi Cloud environments require you to provide the generated key.

  • 08

    What is the difference between RAG and Search?

    The search capability issues a standard vector similarity match—it returns relevant raw snippets from your database. The rag_query capability asks the R2R server to perform the search and compute an intelligent answer wrapping those snippets using an LLM.

  • 09

    Are document ingestions possible via chat?

    No. This integration is designed for observational toolsets (listing documents, inspecting states, querying the index). Heavy ingestions of PDFs or websites should be handled through scripts or the dashboard.

Connect R2R to Claude, Cursor, ChatGPT & more