Vinkius
Redox

Redox MCP for AI. Access structured clinical data from natural language.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Redox MCP on Cursor AI Code EditorRedox MCP on Claude Desktop AppRedox MCP on OpenAI Agents SDKRedox MCP on Visual Studio CodeRedox MCP on GitHub Copilot AI AgentRedox MCP on Google Gemini AIRedox MCP on Lovable AI DevelopmentRedox MCP on Mistral AI AgentsRedox MCP on Amazon AWS Bedrock

How this MCP server connects to your AI agent

Redox connects your AI agent directly to complex, standardized clinical data using FHIR and Redox Data Models. Search for patient records by identifier, pull active diagnoses, and write structured vital signs back to the EHR—all from a single chat interface.

What AI agents can do with Redox Automation

Create observation

This tool saves vitals or general observations directly back into the electronic health record.

Post data model

It sends a structured Redox Data Model event, useful for generalized system notifications.

Search condition

This tool retrieves active diagnoses and problem lists associated with a specific patient ID.

+ 1 more capabilities included
Find Patient Records

The agent searches connected systems for a patient using identifiers like MRNs or specific slugs.

Retrieve Clinical Conditions

It fetches a list of active diagnoses and conditions linked to a given patient ID, providing immediate medical context.

Write Back Vitals and Observations

The agent sends structured data bundles (FHIR) to record new vital signs or clinical observations directly into the EHR.

Send Standardized Health Events

It transmits asynchronous notifications or queries using standardized Redox JSON Data Models for broad system compatibility.

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with Redox: 4 Tools for Healthcare Interoperability

These tools allow you to programmatically manage core patient data tasks, including searching records, retrieving diagnoses, and writing structured observations via the FHIR standard.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Redox on Vinkius

Create Observation

This tool saves vitals or general observations directly back into the electronic health record.

Post Data Model

It sends a structured Redox Data Model event, useful for generalized system...

Search Condition

This tool retrieves active diagnoses and problem lists associated with a specific...

Search Patient

It searches for a patient record across the connected Redox FHIR API using...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Redox integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Redox, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,100+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week
Redox MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Redox. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

The headache of stitching together a patient record from different systems., Solved with Vinkius AI Gateway

Right now, if you need to know everything about a patient—their current vitals, their active diagnoses, and who they are—you have to click across three or four different tabs and maybe even log into two separate portals. You pull the name from one system, copy the condition list from another, and then manually input the blood pressure reading somewhere else. It’s slow, it's error-prone, and half the time you end up with data that isn't structured enough to be useful.

With this MCP, your agent handles all those clicks. You ask a single question, like 'What is P123's full clinical picture?' The agent executes multiple calls—searching for identity, retrieving conditions, and pulling demographic data—and hands you one clean, actionable answer. It’s the difference between manual data aggregation and real-time intelligence.

Write back observations with structured FHIR bundles using create_observation.

Before this MCP, documenting a new blood pressure reading meant finding the 'Notes' section in the EHR and typing: 'BP 120/80 today.' This was unstructured text. It couldn't be graphed, trended against other readings, or used automatically by billing systems.

Now, using `create_observation`, your agent sends a structured FHIR bundle that contains specific fields for the date, time, measurement type (Blood Pressure), and the exact value. The data isn't just written; it’s saved in a machine-readable format that immediately enhances patient care quality.

What your AI can actually do with this

Managing healthcare interoperability shouldn't require deep knowledge of FHIR standards or wrestling with multiple API endpoints. This MCP lets your agent interact with clinical systems using natural language. You can search for patient records across connected health systems, pulling complete patient identifiers and demographics. Need context? Your agent retrieves active diagnoses and problem lists associated with a specific patient ID.

Want to document vitals? You write structured observations back into the EHR environment. Furthermore, you manage complex data exchanges by sending standardized Redox Data Model events. This capability is critical for any AI-driven medical assistant. If you're building something that needs reliable access to clinical context and has multiple endpoints, check out Vinkius; it hosts this MCP alongside thousands of others so you don’t have to connect everything separately.

Built · Hosted · Managed by Vinkius Redox MCP - Access FHIR Clinical Data from AI
Server ID 019ea602-32ba-72a7-ab20-8e4001623152
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Questions you might have

How does Redox MCP help with FHIR standards? +

It handles the complexity of FHIR compliance for you. Instead of needing to know how to structure a FHIR resource, you just tell your agent what data you need (e.g., 'Get active conditions'), and it manages the protocol.

Can I use Redox MCP if I don't have an MRN? +

Yes. You can still search by other identifiers like destination slugs or specific patient IDs, as long as those identifiers are recognized within your connected systems.

What is the difference between `search_patient` and searching in a normal EHR UI? +

search_patient allows your agent to query multiple, disparate healthcare sources simultaneously. It's an automated search layer built on top of existing systems, not just a single directory lookup.

Is `post_data_model` for sending general notifications? +

Yes. This tool lets you send standardized events (like 'New Appointment' or 'Test Result Ready') that multiple different backend systems can understand, regardless of their internal API.

Does Redox MCP only work in development mode? +

No. The MCP supports switching between environments for testing and deployment. You manage your environment directly within the connection settings to ensure you're querying the correct data source.

Built & Managed by Vinkius 30s setup 4 tools

We've already built the connector for Redox. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.