An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Redox 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 clinical EHR data.

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 · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Redox.

  1. 01

    Search patient

    This capability searches the Redox FHIR API to find specific patient records.

  2. 02

    Create observation

    Use this to save vitals or clinical observations back to the EHR via writeback.

  3. 03

    Search condition

    This capability retrieves a patient's active diagnoses or problem list items.

  4. 04

    Post data model

    This capability sends a Redox Data Model API event for standardized interoperability.

Real work

What teams actually run

01

Integration Testing

Developers verify how FHIR resources map to their applications by querying data through the agent.

02

Rapid Patient Lookup

Operations staff use the agent to quickly find a patient's active diagnoses.

03

Automated Clinical Updates

An agent sends vital signs back to the EHR after processing them.

04

Event Notification

The system sends appointment notifications using Redox Data Model events.

Automate a task

Put Redox 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

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

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put Redox 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

1002ms average. Fast in production.

Redox is checked daily against the live service.

Daily averagePeak 1337ms
Oct 3Today
Fastest day
813ms
Slowest day
1337ms
14-day trend
Stable-1%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 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 Redox, so you can see the experience inside your AI.

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

Redox Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_vkjMJUhpElzGUBW33LqwwW8NlPpFijvpbWdCCZWf/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 — Redox capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "redox-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_vkjMJUhpElzGUBW33LqwwW8NlPpFijvpbWdCCZWf/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 Redox in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Redox owners hand off.

This MCP is built for professionals working at the intersection of healthcare and software development.

  • 01

    HealthTech Developers

    They use the MCP to test clinical integrations and verify FHIR mapping in their code editors.

  • 02

    Clinical Operations

    They use the agent to look up patient conditions without opening a full EHR.

  • 03

    Digital Health Startups

    They use the connection to give their medical assistants real-time clinical data access.

FAQ

Questions Redox owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the MCP on Vinkius and then connect your client, such as Claude or Cursor, with a single click. Vinkius handles the hosting and credentials for you.

  • 02

    What data standards does this MCP support?

    This MCP supports both FHIR standards and Redox JSON Data Models for clinical interoperability.

  • 03

    Can I write data back to the EHR?

    Yes, you can use the create_observation capability to save vitals and clinical observations back to the EHR using FHIR bundles.

  • 04

    Is it possible to test in a sandbox?

    Yes, the MCP includes environment management so you can switch between development and production environments.

  • 05

    What do I need to get started?

    You will need a valid Redox API Key to authenticate your connection.

  • 06

    Can I search for patients across different healthcare systems?

    Yes, by using the search_patient capability with the specific destination_slug and identifier, you can query any connected system in your Redox network.

  • 07

    Does this support writing clinical data back to an EHR?

    Yes. The create_observation capability allows you to perform writeback operations by sending FHIR bundles containing vitals or other clinical observations.

  • 08

    What is the difference between FHIR capabilities and the Data Model capability?

    The search_patient and search_condition capabilities use the FHIR API for standardized resource access, while post_data_model uses Redox's proprietary JSON Data Models for broader interoperability events.

Explore

More in Developer Tools

Suggestions

Connect Redox to Claude, Cursor, ChatGPT & more