Medicare coverage is complex: clinicians must check NCDs, LCDs, ICD\u201110 codes, and whether a drug is under Part B or Part D, all before billing. Doing this correctly can mean the difference between payment and denial.<\/p>\n\n\n\n
The CMS Coverage Connector in Claude cuts through the manual work. It links Claude directly to Medicare Part B coverage policies, so you can ask in plain language and instantly get structured answers from the official CMS database with no authentication or portal navigation needed.<\/p>\n\n\n\n
In this article, we will walk through exactly what the CMS Coverage Connector is, what Medicare Part B it covers, and what it does not, how each of its seven tools works, how to set it up in Claude, and the most practical workflows it enables for clinicians, billers, and coding professionals.<\/p>\n\n\n\n
TL;DR: CMS Coverage Connector in Claude<\/strong><\/p>\n\n\n\n It connects Claude to the official CMS Medicare Coverage Database, letting you query NCDs, LCDs, and drug coverage policies through plain language conversation<\/p>\n\n\n\n The CMS Coverage connector gives Claude access to Medicare Part B coverage policies from the CMS Coverage Database, including national coverage determinations and local coverage determinations. The connector draws from the same government database that all Medicare coverage decisions are based on, meaning the information Claude returns is authoritative, not summarized from a third-party source.<\/p>\n\n\n\n The MCP <\/a>endpoint behind this connector is maintained by deepsense.ai and is publicly available without requiring a paid subscription or authentication. The connector works immediately after enabling no authentication is required. That makes it one of the most accessible healthcare connectors available in Claude, and one of the most practically useful for day-to-day clinical operations work.<\/p>\n\n\n\n The connector provides seven distinct tools organized across four categories. Each tool is designed for a specific kind of coverage inquiry, and Claude will automatically select and combine the right tools based on how you phrase your question.<\/p>\n\n\n\n This is the broadest entry point for national policy questions. This tool performs a unified search for all national coverage documents, NCDs, NCAs, CALs, MEDCAC meetings, and technology assessments. <\/p>\n\n\n\n Use it for finding national coverage policies and analyses, checking coverage for new technologies, understanding Medicare’s position on treatments, researching coverage decision rationale, and tracking MEDCAC meetings and technology assessments. Example prompts that trigger this tool include asking whether Medicare covers PET scans or looking for all national coverage analyses related to cardiac devices.<\/p>\n\n\n\n This goes one level deeper; once you know a specific policy exists, this tool retrieves the full document. It retrieves complete information for a specific coverage document by ID and type. Use it for reading full policy text, understanding coverage criteria, checking indications and limitations, finding coding <\/a>requirements, and accessing complete NCA or CAL details.<\/p>\n\n\n\n If a Search National Coverage query returns a document number, following up with Get Coverage Document gives you everything in that policy: the coverage criteria, the coding requirements, and the effective dates.<\/p>\n\n\n\n It handles comparative research efficiently. This tool retrieves multiple National Coverage Determinations in a single request, up to 20 NCDs. Use it for efficiently fetching details for multiple policies, comparing coverage across related conditions, building comprehensive coverage summaries, and reducing API <\/a>calls when analyzing multiple NCDs. <\/p>\n\n\n\n For anyone trying to understand how Medicare approaches an entire disease area, say, all diabetes-related NCDs, this tool lets Claude retrieve them all simultaneously and present a comparative analysis in one response.<\/p>\n\n\n\n It addresses the regional layer of Medicare policy. This tool performs a unified search for all local coverage documents, final LCDs, proposed LCDs, and billing articles. <\/p>\n\n\n\n Use it for finding local and regional coverage policies, checking state-specific requirements, understanding local medical necessity criteria, accessing billing and coding guidance, and tracking proposed policy changes. A billing team in California dealing with a physical therapy claim, for instance, can search specifically for LCDs applicable to their state and find the exact local requirements that apply.<\/p>\n\n\n\n This handles policy monitoring. This tool tracks recent coverage changes, both national and local policies. Use it for monitoring policy changes, staying current on coverage updates, tracking new technologies and treatments, planning for policy implementations, and identifying policy revisions in your region. <\/p>\n\n\n\n For national scope, it tracks NCDs, NCAs, CALs, MEDCAC meetings, and technology assessments updated within a configurable lookback period of up to 120 days. For practices that need to stay ahead of coverage changes before they affect their claim submission process, this tool is the most operationally valuable.<\/p>\n\n\n\n This handles a question that comes up constantly in drug coverage: is this drug covered under Part B, or does it belong in Part D? This tool searches the Self-Administered Drug Exclusion List for oral drugs not covered under Medicare Part B because they are covered under Part D instead. <\/p>\n\n\n\n Use it for verifying if an oral drug is Part B covered, understanding why a drug claim was denied under Part B, determining the correct benefit category, guiding patients to Part D coverage for oral medications, and finding excluded drugs by HCPCS code or name.<\/p>\n\n\n\n It resolves the jurisdiction question that local coverage work always requires. This tool finds Medicare administrative contractors by state or contractor ID. Use it for identifying which MAC covers your state, finding MAC contact information, determining applicable local policies, and understanding jurisdiction coverage.<\/p>\n\n\n\n This tool works alongside Search Local Coverage once you know which MAC administers your state, you can filter local coverage searches to only return policies from that contractor.<\/p>\n\n\n\n To add the connector to Claude, open Claude Desktop<\/a> and select your profile icon in the bottom left. Navigate to Settings, then Connectors. Browse the available connectors catalog and search for \u201cCMS Coverage\u201d or find it under Healthcare connectors.<\/p>\n\n\n\n Click on the CMS Coverage Connector and click \u201cEnable\u201d or \u201cAdd Connector.\u201d The connector will be activated immediately. No authentication is required the connector works as soon as it is enabled in your account.<\/p>\n\n\n\n To verify the connection is working, ask Claude: \u201cDoes Medicare cover PET scans?\u201d Claude should use the CMS Coverage connector to search policies and return an answer based on the current NCD rather than just drawing on its training knowledge. If you see Claude citing specific NCD document numbers and effective dates, the connector is active and working correctly.<\/p>\n\n\n\n For team and enterprise users, the connector can be made available across an organization through the same admin settings used for other connectors. Because no authentication is required, there is no user\u2011level credentialing to manage. Administrators simply enable the connector for the organization, and all members can use it immediately.<\/p>\n\n\n\n The real value of the connector shows up in the workflows where healthcare professionals spend the most time manually searching and cross\u2011referencing. Prior authorization preparation is one of the clearest use cases. When preparing a prior authorization for a PET scan in California, Claude will search national coverage for the PET scan NCD and retrieve the full coverage criteria from the complete document.<\/p>\n\n\n\n Use the Get Contractors tool to identify California\u2019s MAC and search local coverage with a contractor filter for billing guidance, then list the required documentation, covered indications, and ICD\u201110 codes all in a single response. That multi\u2011step workflow, which previously involved separate searches across multiple CMS database interfaces, now happens in one conversation.<\/p>\n\n\n\n For drug coverage disputes, the connector resolves claim denials that practices sometimes chase for weeks without understanding the root cause. When asked whether oral imatinib is covered under Medicare Part B, Claude searches the SAD exclusion list, finds imatinib in the exclusion list, and explains.<\/p>\n\n\n\n That it is a self\u2011administered oral drug excluded from Part B confirms it is covered under Part D prescription drug plans instead and provides HCPCS codes for the excluded formulations. For a billing team that received a denial on an oral chemotherapy claim, this answer clarifies both the reason and the correct path forward in under a minute.<\/p>\n\n\n\n Policy monitoring using the What\u2019s New tool is particularly useful for compliance officers and coding managers who need to track regulatory changes affecting their practice. When asked about Medicare coverage changes in the last month affecting a practice in Texas. Claude uses the What\u2019s New tool with a national scope to check recent NCD, NCA, and CAL changes.<\/p>\n\n\n\n Then searches the local scope filtered by the Texas contractor to check LCD updates, summarizes new and revised policies, highlights those relevant to the specified specialty, and notes effective dates for upcoming changes. This kind of summary, built from live CMS data, replaces what previously required either a dedicated compliance service subscription or hours of manual database monitoring.<\/p>\n\n\n\n NCDs are national policies that grant, limit, or exclude Medicare coverage for a specific medical item or service. <\/p>\n\n\n\n They are developed and published by CMS and apply to all states. If an NCD does not specifically exclude or limit an indication or circumstance, or if the item or service is not mentioned at all in an NCD or in a Medicare manual, coverage may be decided at the local level by a Medicare Administrative Contractor (MAC) through a Local Coverage Determination (LCD).<\/p>\n\n\n\n LCDs cannot contradict NCDs but exist to clarify them or address common coverage issues in a specific region. Think of NCDs as federal regulations and LCDs as state\u2011level rules built on top of them. <\/p>\n\n\n\n Always verify both the NCD and the relevant LCDs before submitting claims, because compliance with both is essential for successful reimbursement. Even if your documentation is strong and the procedure is medically necessary, a lack of coverage under the correct NCD or LCD can still lead to denials.<\/p>\n\n\n\n These two factors, NCDs and LCDs, directly determine whether Medicare will reimburse you for a service. The CMS Coverage Connector in Claude handles this two\u2011layer structure automatically. When you ask about coverage for a procedure, Claude searches NCDs first and retrieves the full national policy if one exists. <\/p>\n\n\n\n If no NCD applies, Claude then checks LCDs in the relevant jurisdiction. You do not need to know in advance whether coverage is national or local; Claude figures that out from the CMS database and surfaces the right policies for your question.<\/p>\n\n\n\n\n
What Is the CMS Coverage Connector in Claude?<\/strong><\/h2>\n\n\n\n
The Seven Tools and What Each One Does<\/strong><\/h2>\n\n\n\n
1. Search National Coverage <\/strong><\/h3>\n\n\n\n
2. Get Coverage Document<\/strong><\/h3>\n\n\n\n
3. Batch Get NCDs<\/strong> <\/h3>\n\n\n\n
4. Search Local Coverage<\/strong><\/h3>\n\n\n\n
5. What’s New<\/strong><\/h3>\n\n\n\n
6. SAD Exclusion List<\/strong> <\/h3>\n\n\n\n
7. Get Contractors<\/strong><\/h3>\n\n\n\n
\n The CMS Coverage Connector<\/strong> pulls from the official Medicare Part B database<\/strong>, handling complex rules such as identifying when drugs like imatinib<\/strong> are excluded under the SAD List<\/strong> and instead fall under Part D<\/strong> \u2014 helping avoid weeks of claim denials.\n
\n With features that track policy updates up to 120 days back<\/strong>, it can detect changes like new Local Coverage Determinations (LCDs)<\/strong> early. This transforms manual portal searches into instant, structured answers<\/strong> that combine national policies, local variations,<\/strong> and coding requirements<\/strong> for faster reimbursements.\n
\n<\/div>\n\n\n\nHow to Set Up the Connector<\/strong><\/h2>\n\n\n\n
Step 1: Open Claude Desktop and Go to Connectors<\/strong><\/h3>\n\n\n\n
Step 2: Enable the CMS Coverage Connector<\/strong><\/h3>\n\n\n\n
Step 3: Test That the Connector Is Working<\/strong><\/h3>\n\n\n\n
Step 4: Enable the Connector Across Your Organization <\/strong><\/h3>\n\n\n\n
Practical Workflows That Save Real Time<\/strong><\/h2>\n\n\n\n
1. Streamline Prior Authorization Workflows<\/strong><\/h3>\n\n\n\n
2. Resolve Drug Coverage Disputes Quickly<\/strong><\/h3>\n\n\n\n
3. Monitor Policy Changes Automatically<\/strong><\/h3>\n\n\n\n
Understanding NCDs vs. LCDs: Why Both Matter<\/strong><\/h2>\n\n\n\n
1. NCDs and LCDs Are<\/strong><\/h3>\n\n\n\n
2. NCDs and LCDs Work Together<\/strong><\/h3>\n\n\n\n
3. Both Layers Matter for Claims<\/strong><\/h3>\n\n\n\n
Using This Alongside Other Healthcare Connectors<\/strong><\/h2>\n\n\n\n