The Redox MCP server is an open, model-agnostic gateway that lets your technically sophisticated healthcare integration team manage, configure, monitor, and automate your Redox environment through any AI client you already trust. You can access the MCP server without downloading software, locking into a proprietary model, or giving up control over your data.
- Your Redox organization must be opted in to the MCP server to access it. Learn how to enable AI features.
- You must have installed the Redox MCP server with the AI agent of your choice. Learn how to access the MCP server.
Natural language prompts help you take direct action in your Redox environment. We provide several example prompts for you to get started using the Redox MCP server.
Review our prompts by category and replace any bracketed placeholders with real IDs, names, or values. You can use these prompts with any AI agent you choose. Make sure to test any configuration changes in a staging environment first and specify the environment in each prompt.
Talk to your Redox Account Manager with any questions.
Manage authentication in your Redox environment.
Prompt to use | Purpose |
|---|---|
Create a new OAuth API key in environment [ID] for [your system name]. | Manage API credentials for environment access. |
List all OAuth API keys configured in environment [ID]. | Review all API credentials for environment. |
Delete OAuth API key [ID] from environment [ID]. | Manage API credentials for environment access. |
Manage sources, destination, and subscriptions in your Redox environment.
Prompt to use | Purpose |
|---|---|
Create a new source in environment [ID] named [X] with data model [PatientAdmin]. | Set up data pipelines (i.e., subscriptions). |
Create a new destination in environment [ID] pointed at endpoint [URL] for connected organization [Y]. | Set up data pipelines (i.e., subscriptions). |
Show me all sources configured in environment [ID]. | Review already configured assets for subscriptions. |
Update the endpoint URL for destination [ID] to [new URL] and verify it. | Manage data pipeline (i.e., subscriptions). |
Create a subscription between source [ID] and destination [ID] in environment [ID]. | Manage data flow by setting up a subscription with a source and destination. |
Using the [Org A + EHR] subscription as a template, set up an identical subscription for connected [Org B]. | Copy configuration to set up a new subscription with a different connected organization. |
Manage data operation assets (i.e., config modifiers, filters, translation sets) in your Redox environment.
Operation type | Prompt to use | Purpose |
|---|---|---|
Any | Copy this [asset] and apply it to my new subscription. | Duplicate config modifiers, filters, or translation sets from one connection and apply them to another without rebuilding from scratch. |
Config modifier | Create a config modifier on this source — no traffic yet. | Unlike the Redox dashboard, our MCP server can create config modifiers without an existing log. This removes a common blocker during early subscription setup. |
Config modifier | Create a config modifier on source [ID] — no traffic yet. | Unlike the Redox dashboard, our MCP server can create config modifiers without an existing log. This removes a common blocker during early subscription setup. |
Config modifier | Duplicate config modifier [X] from subscription [ID] subscription and apply it to the [Org B] subscription in environment [ID]. | Duplicate config modifiers across subscriptions. |
Config modifier | Create a config modifier in environment [ID] that maps [source field] to [target field] for all ADT (PatientAdmin) events. | Create config modifiers across subscriptions. |
Config modifier | Restore the previous version of config modifier [ID]. | Restore config modifiers across subscriptions. |
Filter | Show me the filters currently applied to subscription [ID]. | View filters at a glance. |
Filter | Create a filter on subscription [ID] that only passes through NewPatient and PatientUpdate event types. | Control which events flow through a subscription. |
Filter | Update the filter on subscription [ID] to exclude events where [field] is null. | Manage filters across subscriptions. |
Translation set | List all translation sets in environment [ID]. | View translations at a glance. |
Translation set | Show me the current translation mappings for translation set [ID]. | View translation mappings across subscriptions. |
Translation set | Add a translation to set [ID] to map value [A] to [B]. | Edit and manage translation mappings across subscriptions. |
Translation set | Show me any new translations added to translation set [ID] since [date]. | View changes to translation sets at a glance. |
Translation set | Update my translation table with these new facility mappings. | Add or update values in translation sets conversationally. This removes the obstacle of navigating nested menus for routine maintenance tasks. |
Manage and audit how config modifiers, filters, and translation sets are promoted.
Prompt to use | Purpose |
|---|---|
How does staging asset compare to production for my connection to this org? | Get a diff of your staging and production environments, then promote assets directly once you know the gaps, all in one conversation. |
Promote config modifier [ID] from staging environment [ID] to production environment [ID]. | Promote validated assets from staging to production. |
Promote translation set [ID] from staging to production. | Promote validated assets from staging to production. |
Compare the sources, destinations, config modifiers, and filters for subscription [ID] in staging vs. production and summarize any differences. | Get a diff view of staging and production assets. |
Promote all assets (config modifiers, filters, translation sets) associated with subscription [ID] from staging [ID] to production [ID]. | Promote validated assets from staging to production. |
For subscription [ID], retrieve all associated config modifiers in production and flag any that aren't on their latest version. | View and compare asset versions. |
Prompt to use | Purpose |
|---|---|
List all members and their roles in environment [ID]. | Review user access and roles across environments. |
Assign [user email] the role of [role name] in environment [ID]. | Control user access and roles across environments. |
Monitor and set up alerts for traffic in your Redox environment.
Prompt to use | Purpose |
|---|---|
Create an alert rule in environment [ID] that fires when the error rate exceeds 5% on destination [ID]. | Set up monitoring and notifications for pipeline activity. |
Show me all triggered alerts in environment [ID]. | Review triggered alerts for preemptive monitoring or troubleshooting. |
Update alert rule [ID] to notify [email] instead of the current recipient. | Update monitoring and notifications for pipeline activity. |
Monitor and troubleshoot traffic in your subscriptions.
Prompt to use | Purpose |
|---|---|
Show me any failed logs for this subscription in the last 24 hours. | Search and filter logs by connection, time range, or status to quickly surface errors and understand what happened without navigating the Redox dashboard. |
Search for failed logs on subscription [source ID] from the past 24 hours". | Investigate traffic errors. |
Find logs for patient MRN [X] sent through source [ID] in the last 7 days. | Search payloads and metadata to investigate traffic. |
Run log inspector on log [ID] in environment [ID] and summarize what happened. | Investigate and troubleshoot traffic errors. |
Prompt to use | Purpose |
|---|---|
How many active connections do I have and what events are they subscribed to? | Get an instant summary of your integration landscape (i.e., sources, destinations, subscriptions, and transaction volumes) without manually pulling reports. |
How many transactions did organization [ID] process last month, broken down by connection? | Retrieve transaction volumes and activity summaries. |
Give me a CSV export of transaction metrics for organization [ID] for Q1. | Retrieve transaction volumes and activity summaries. |
Show me product-level metrics for organization [ID] over the past 30 days. | Retrieve transaction volumes and activity summaries. |