Connect Vlada to the tools you already use.
Add one secure connection. Sign in once. Ask a healthcare question in plain English, or call a governed tool directly, and get the answer with its sources attached.
$5 of free queries to start · every answer traced to its source · more credit on request
From connection to your first answer in minutes.
Add Vlada
Add one secure MCP connection in the tool where you want to use it.
- Claude Code
- ChatGPT
- Cursor
- Another MCP client
- Your own application
Sign in
Vlada opens a secure browser sign-in. Your account determines:
- Which organization you belong to
- Which healthcare Worlds you can use
- Which tools are available
- Which data you may access
Ask or build
In an AI client, ask in plain English. In an application, call a tool directly.
Every result includes the answer and the evidence behind it.
One connection, your tool of choice.
Pick your client for the exact setup. Only the selected client's instructions appear, so you are never reading four guides at once.
Connect Vlada to Claude Code
- 1Create your API key at
vladahealth.com/account. It is shown once — copy it. - 2Copy and run this in your terminal, pasting your key into the header.terminal$ claude mcp add --transport http vlada https://mcp.vladahealth.com/mcp --header "Authorization: Bearer <your-api-key>"
- 3Open Claude Code, run
/mcp, and confirm Vlada shows connected. - 4Ask a first question to confirm your tools.Then ask
Use Vlada. List the healthcare tools available to my organization. Do not call a tool yet.
Claude Code supports remote HTTP MCP servers with a per-server --header. Your key scopes the tools your organization is entitled to.
The connection is simple because the hard work is already done.
Vlada has already collected, organized, connected, and governed the public healthcare record. You do not need to rebuild that infrastructure before asking a useful question.
To answer one healthcare question, a team may need to:
- 01Find the correct public source
- 02Download and process enormous files
- 03Understand a new schema
- 04Resolve providers, facilities, payers, and codes
- 05Choose the correct historical release
- 06Join incompatible datasets
- 07Apply healthcare payment methodology
- 08Validate the result
- 09Preserve the evidence
- 10Build and maintain the pipeline
The healthcare data work is already done. One connection makes it usable.
- 1ConnectOne secure MCP or API connection.
- 2AskA question in plain English, or a direct tool call.
- 3InspectThe answer and its receipts, together.
Ask naturally, or call directly.
MCP and the Data API use the same healthcare data, identity system, methodologies, and evidence model.
The AI can
- Understand the question
- Choose the right Vlada capability
- Call the tool
- Interpret the structured result
- Show the answer with its evidence
→ Vlada API
→ structured healthcare result
→ evidence metadata
Use it for
The answer, and the evidence behind it.
What is the commercial benchmark for CPT 70553 in Connecticut, and what evidence supports it?
Example structure. Available fields and values depend on the question, your access, and current source coverage.
Plain-English questions, typed and sourced answers.
Ask in natural language; the agent picks the right capability and returns a structured answer with its evidence.
- What does an insurer pay for a service?
- What does a hospital post?
- How does a price compare with Medicare?
- Who is this provider?
- Where do they practice?
- Which facilities belong to this health system?
- What would Medicare pay?
- Which plans are gaining enrollment?
- How do benefits or Stars compare?
- What public prices and payment references exist?
- How does access vary by plan?
- Where does paid spending exceed compatible public references?
- Run a bounded query across the healthcare data included in my access.
Eight healthcare Worlds through one connection.
Identity · Codes · Geography · Policy · Time · Provenance
Explore the Worlds →Live coverage, and the limits stated plainly.
These are current, measured counts, not marketing rounding. Methodologies are kept separate, so a fee schedule is never blended with a percentage of charges, and each answer returns its own limitations.
Coverage as of 2026-07-14.
Built for production, not just a demo.
The same secure substrate that runs the Employer Agent. Access is authenticated, scoped, bounded, and auditable.
Every connection authenticates through a secure browser sign-in. No shared keys pasted into config files.
Your account determines the Worlds, tools, and data you are permitted to use. Access is scoped, not global.
Custom queries are read-only and resource-bounded, with a separate async lane for heavy pulls. No write path, no runaway jobs.
Every answer carries a content hash and resolves to the public source file behind it, so requests and results are replayable and reviewable.
One connection. The public healthcare record, usable.
Create your free account to connect over MCP, or talk to us about the Data API and production integrations.
Prefer a terminal? Copy the connect command instead — either door lands in the same account.