ContextRx
Talk to our team
Home / Developers Developers

Connect once. Turn on the endpoints you need.

ContextRx speaks the Model Context Protocol, so the agent you build and run connects the way it already expects to — we provide the endpoints it calls. Start in the sandbox with no BAA, then unlock member-level Clinical Context when you're ready.

Talk to our team

MCP quickstart

Point your MCP-capable agent at the ContextRx server, authenticate with your key, and the endpoints you've enabled appear as tools. The Knowledge Base and de-identified population analytics work immediately; member-level Clinical Context appears once a BAA is signed.

1
Get a key. Create a free sandbox key — no BAA required for the Knowledge Base.
2
Connect over MCP. Add the ContextRx MCP server to your agent and pass your key.
3
Call an endpoint. Enabled endpoints surface as tools your agent can invoke.
# Sandbox MCP endpoint (JSON-RPC over HTTP)
POST https://www.contextrx.ai/sandbox/mcp
Authorization: Bearer crx_sandbox_…

# A BAA unlocks member-level Clinical Context
POST https://www.contextrx.ai/mcp
Authorization: Bearer crx_live_…

Every response carries the metadata your tooling expects — a schema version, a call id, and the pricing fields for that call.

Sandbox keys

Sandbox keys are free and let you explore the full Knowledge Base plus synthetic Clinical Context. They're rate-limited and never touch real PHI — the fastest way to see what your agent could know.

→
Sandbox keys are prefixed crx_sandbox_; production keys are crx_live_.
→
Upgrade to production from your dashboard once you've signed a BAA.
Get a sandbox key

Endpoint reference index

Every endpoint, grouped by block and labeled by whether it needs a BAA. One entry per endpoint; turn on what you need.

Knowledge BaseNo BAA
/knowledge/terminologyCode systems & crosswalks.
/knowledge/drugDrug facts & interactions.
/knowledge/coverageFormulary & benefit logic.
/knowledge/calculatorsDeterministic clinical scores.
/knowledge/guidelinesCare guidance & pathways.
/knowledge/sdohSocial determinants reference.
/knowledge/evidenceEvidence base lookups.
/knowledge/deviceDevice reference.
/knowledge/genomicsGenomics reference.
Clinical Contextmember: BAA
/context/memberIdentity-resolved patient: interactions, adherence, risk. PHI · BAA + consent.
/context/providerClinician context.
/context/populationDe-identified cohort comparison. No PHI, no BAA.
Agent SkillsScoped
/skillsClinician-approved patient process areas + integrations (CPG-on-FHIR / CDS Hooks / CQL) your agent calls.

MCP / HMCP compatibility

ContextRx is delivered over the Model Context Protocol (MCP), so any MCP-capable agent runtime can consume it without a custom integration.

Healthcare MCP (HMCP): as healthcare-specific MCP conventions converge, ContextRx tracks them so PHI scoping, consent, and audit travel with each call. Connect over standard MCP today; HMCP-aligned behavior is layered on without changing your integration.

Start building in the sandbox.

Free sandbox keys, the full Knowledge Base, and synthetic Clinical Context — no BAA required to start.

Get a sandbox key Talk to our team →