Resources · Claude connector

Claude Turquoise connectorWhat Claude can do in your Turquoise account.

The Claude Turquoise connector exposes 6 tools: 6 read, 0 write, 0 undocumented. Five query negotiated rates from Turquoise Health's pricing data, one per care setting; the sixth explores how payers, providers and health systems relate. Which tools you see depends on your organization's data access.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can query Turquoise

With this connector, you ask Claude a healthcare pricing question in plain language, and it queries Turquoise Health's negotiated rate data, split by care setting, while it answers. Turquoise presents it for benchmarking reimbursement rates, sizing markets, seeing what a payer pays in a given geography, or comparing rates across providers and plans.

Rates for physician-billed services. You ask what physician groups in a state are paid for a service, and analyze_professional_rates pulls the negotiated professional rates from Clear Rates, with geography and payer in the question.

Hospitals compared on a DRG. For inpatient or outpatient care at hospitals and ambulatory surgery centers, analyze_medical_rates queries facility-billed rates; Turquoise advises naming the code system, as in MS-DRG 470, rather than a bare number.

Who relates to whom. explore_knowledge_graph searches payers, providers and health systems and lists their relationships across geographies, service lines, network types and product lines.

What it will not do: Turquoise states that its connector tools are read-only and never alter anything in your platform account. Claude only sees the data sets your organization has access to, and a tool your organization has no access to does not appear. Nothing runs on a schedule: Claude calls these tools while it answers you. For recurring exports, look at the automation platforms on our Integrations hub.

Vocabulary

Five terms before you connect

Claude's vocabulary around this connector, in one minute.

Connector
The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
Tool
One named capability a connector opens to Claude. Claude decides which to call; the directory sheet lists every tool by name.
Authorization
The service's own sign-in screen, where you grant Claude the access it will use. Here it is your Turquoise login. Per person, revocable.
Approval
The confirmation Claude waits for before changing something in an account for you, shown in the chat when it matters.
MCP
The open standard that connectors run on: it is what lets an assistant like Claude read data from a service such as Turquoise.
Connect

Connect Turquoise to Claude in three steps

  1. 01

    Find Turquoise in the connector list

    Open Claude's settings, go to Customize, then Connectors, and look for Turquoise. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it for the organization before each member connects.

  2. 02

    Sign in to Turquoise

    Click Connect on its row and sign in in the window the service opens. Turquoise says the connector authenticates with the Turquoise account you already have. If the link breaks later, Disconnect and connect again.

  3. 03

    Review the authorization screen

    Read the screen Turquoise shows before you accept. It is the service's screen, not Claude's, and it decides what the access covers. You can withdraw that access later the same way.

Tools

The 6 tools, sorted by what they do

Turquoise gives Claude 6 tools: 6 that read your account, 0 that change something in it.

All six read. Turquoise describes each one in a table of its connector guide, and the names stay exactly as Claude shows them.

  • 6 read

What Claude reads (6)

6 tools

Six tools that query rates or relationships without touching your Turquoise account.

explore_knowledge_graph

Searches healthcare entities and walks their relationships across payers, providers, health systems, geographies, service lines, network types and product lines. It finds an entity, lists its relationships and retrieves the related data.

When it helps
you want to see which providers, networks or geographies are linked to a given payer.

Sourceturquoise.health · June 11, 2026 ↗

analyze_medical_rates

Returns negotiated rates for facility-billed medical services, such as inpatient and outpatient care at hospitals and ambulatory surgery centers, drawn from Clear Rates.

When it helps
you benchmark what hospitals in a market are paid for a DRG.
Watch out
Turquoise advises naming the code system, like MS-DRG, since one number can exist in several systems.

Sourceturquoise.health · June 11, 2026 ↗

analyze_drug_rates

Looks up what payers have negotiated for drugs given to patients in hospital, whether admitted or outpatient, using Clear Rates data. You can narrow by drug name or by therapeutic area.

When it helps
you compare what payers pay hospitals for one drug across a region.

Sourceturquoise.health · June 11, 2026 ↗

analyze_professional_rates

Covers physician-billed services: negotiated rates from physician groups, urgent care clinics and dialysis centers, from Clear Rates.

When it helps
you want the rates physician groups in one state are paid for a service, payer by payer.
Watch out
results follow your subscription, so stay within a state or market it covers.

Sourceturquoise.health · June 11, 2026 ↗

analyze_lab_rates

Covers lab work: the rates negotiated for laboratory and pathology services, whether a laboratory or a physician group bills them, taken from Clear Rates.

When it helps
you check what labs in a market are paid for a test, named with its code system, such as CPT 80053.

Sourceturquoise.health · June 11, 2026 ↗

analyze_devices_rates

Returns what has been negotiated for implanted devices, using the Device Rates data set, and filters by manufacturer, by product or by carve-out.

When it helps
you look at how one implant is reimbursed when it is carved out of a facility rate.
Watch out
Turquoise shows this tool only if your organization has access to Device Rates.

Sourceturquoise.health · June 11, 2026 ↗

Approvals

What Claude asks before acting

Claude's default is to stop and ask before any action it takes on an account for you. Every Turquoise tool documented here reads data, so in normal use there is nothing for Claude to confirm.

On Team and Enterprise workspaces, owners decide whether members may let some actions through without a new prompt, and they can restrict what a connector does for the whole organization, keeping reads and closing writes for instance. Claude works with the rights of the person who connected it, and Turquoise adds that the tools follow your organization's data access. The official per-tool read or write label only shows inside a connected account's settings.

Plans

Which plans include it

None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is published nowhere.

The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner turns a connector on before members connect. The publisher's guide names Claude plans in its setup steps; that line appears in the conflict below. For this connector's current state, open its directory sheet.

Limits

Where the Claude Turquoise connector stops

A connector is not an automation. Claude queries Turquoise while it answers you; nothing fires when new rates are loaded.

A tool list made only of reads is an observed floor, not a guarantee: an admin can open actions that no public sheet shows. The verification badge is not a security audit, and Anthropic says on every sheet that it does not decide a publisher's tools. Only Turquoise Health documents this connector, in a guide published in June 2026; no Claude help article covers it, and the tool descriptions on this page come from that guide.

Two official sources disagree

Which Claude plans can use the Turquoise connector?

What this page followsNeither is declared out of date. Anthropic's rule covers every connector and is the more recent text; Turquoise's line targets this connector but comes from the publisher and leaves out other plans. Check the directory sheet from your own account before relying on either.

Need help

Need help connecting Turquoise to Claude?

A person reads every message.

FAQ

Questions about the Claude Turquoise connector

01What can Claude do with the Turquoise connector?
Claude can query Turquoise Health's healthcare pricing data while it answers you. Five tools return negotiated rates by care setting: facility-billed medical services, physician-billed professional services, laboratory and pathology, drugs administered in hospitals, and implanted devices. A sixth explores the knowledge graph of payers, providers and health systems, with their relationships across geographies, service lines, network types and product lines. Turquoise suggests naming the code system with any billing code, and staying within a state or market your subscription covers.
02Can Claude change anything in my Turquoise account?
Turquoise says no: its guide states that all connector tools are read-only and can never alter anything in your platform account. The directory sheet lists six tools, all described as returning rates or relationships. Treat that as the publisher's statement and the public sheet's state today; an admin can open actions that no public page shows, so look at the sheet again if new tools appear. Nothing in the guide describes a tool that uploads, edits or deletes data.
03Does Claude ask before running a Turquoise query?
By default, Claude asks for confirmation before any action it takes on an account for you. The six Turquoise tools only read data, so normal use has nothing to confirm. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a new prompt, and they can restrict what the connector does for the whole organization. No source describes an approval step specific to these tools.
04Which Claude plans include the Turquoise connector?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. Anthropic's general rule opens remote connectors to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Turquoise's guide mentions a narrower set in its setup steps; both versions are side by side in the limits section. Check the directory sheet from your account.
05Does Claude see all of Turquoise's data?
No. Turquoise says the tools follow your organization's data access, so you only see the tools and results your subscription covers; the device rates tool, for instance, appears only with Device Rates access. If you belong to several Turquoise organizations, the connection uses the last one you used on the platform. More broadly, Claude never reaches beyond the rights of the person who connected it, and an owner on Team or Enterprise can restrict the connector for everyone.
06Why does a Turquoise tool or result seem to be missing?
Turquoise points to your organization's access. It explains that the tools you see follow your organization's data access, and that results do too, so a state or market outside your subscription will not return what you expect. If access was added recently, the tool list refreshes within a few minutes, according to the publisher. If you belong to several Turquoise organizations, the connection uses the last one you used on the platform, which can also explain a missing tool.
07Claude or an automation tool for Turquoise rate data?
They do different jobs, so choose by task rather than by ranking. Claude fits analysis in conversation: asking a pricing question, comparing providers on a code, exploring payer relationships, with tools called only while it answers. An automation platform fits repeated jobs that run on a schedule without you, such as a regular export into a report. The connector itself schedules nothing and keeps nothing running between conversations, so a recurring report needs its own automated setup.