[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Dentrix Ascend API and MCP server: Let your AI agent work your front desk lists. > Dentrix Ascend has an API, but only for software vendors approved into the Henry Schein One API Exchange (checked 27 Oct 2026). Henry Schein One announced an MCP layer inside Ascend on 28 Apr 2026, with no developer docs for connecting your own agent. Cotlet runs 13 tools hosted in your own login, over MCP for agents and REST for scripts. Bring Dentrix Ascend schedules and administrative status reports into your permitted workflow. Use MCP or REST with your agent, automation tools or scripts. [MCP setup](https://cotlet.dev/integrations/dentrix-ascend-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/dentrix-ascend-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Henry Schein One - Page: https://cotlet.dev/integrations/dentrix-ascend-api-mcp-server ## What can you automate in Dentrix Ascend? - Find unverified insurance before visits - Work the unconfirmed appointments list - List patients overdue for recare - Follow up on outstanding claims - Fill the schedule from broken appointments - Weekly production and missed visits report ## Does Dentrix Ascend have an MCP server or an API? - The API Exchange takes vendors through an online application and a security review; a practice cannot get its own key. - The MCP layer has three tiers: Ask, a preview for questions inside Ascend; Orchestrate, pre-built agents for select customers; and Build, with no date yet. - Henry Schein One's own Eligibility Pro already checks payer portals for you, with a per-request cost. - We found no Dentrix Ascend app on Zapier and no community MCP server on GitHub. | What you need | Official API and MCP | GitHub server | Cotlet | |---|---|---|---| | Your own agent on your own practice | Approved vendors only | None exists | Yes, your login | | Eligibility list and verification | Inside Ascend | None exists | Yes, Pro asks first | | Unconfirmed appointments and recare | Recare agent, select customers | None exists | Yes | | Outstanding claims and Power Reports | Ask preview inside Ascend | None exists | Yes, read only | | Sanctioned by Henry Schein One | Yes, official | None exists | Uses the web app | Checked 27 Oct 2026. Sources: [Henry Schein One: Dentrix Ascend opens its MCP layer (28 Apr 2026)](https://www.henryscheinone.com/about-us/press-release/dentrix-ascend-opens-mcp-layer/), [Henry Schein One: Dentrix Ascend API Exchange announced (13 Jul 2023)](https://investor.henryschein.com/news-releases/news-release-details/2023/Henry-Schein-One-Announces-Dentrix-Ascend-API-Exchange-07-13-2023/default.aspx), [Henry Schein One: API Exchange customer FAQs](https://www.henryscheinone.com/dental-solutions/api-exchange/customer-faqs/), [Dentrix Ascend Help: Verifying eligibility statuses](https://hsps.pro/DentrixAscend/Help/Verifying_eligibility_statuses.htm), [Dentrix Ascend Help: Eligibility Essentials and Pro overview](https://hsps.pro/DentrixAscend/Help/Dentrix_Ascend_Eligibility_Essentials_and_Pro_overview.htm) ## How does Cotlet connect to Dentrix Ascend? 1. **Sign in to Dentrix Ascend.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Dentrix Ascend password, you type every MFA code, and paid eligibility requests wait for your OK. ## Connect Dentrix Ascend to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Dentrix Ascend for agents.** Sign up, log in to Dentrix Ascend in its Cloud Browser with your Organization and username, then press Enable for agents. 2. **Paste the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Dentrix Ascend next to your other apps. Use a Dentrix Ascend user of your own with a unique email: Henry Schein One's MFA rules say shared logins trigger more verification codes. If you enable Dentrix Ascend after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-dentrix-ascend \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-dentrix-ascend": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-dentrix-ascend] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: dentrix_ascend_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: dentrix_ascend_write ``` ## How to use the Dentrix Ascend REST API ### Create your Cotlet API key Sign in to Dentrix Ascend in its Cotlet Cloud Browser and enable the app for agents. Your user needs schedule, insurance and report security rights; enter the MFA code yourself. Create a Cotlet API key with access to Dentrix Ascend and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. ### Make your first Dentrix Ascend API request cURL: list_appointments: ``` curl "https://cotlet.dev/api/v1/dentrix-ascend/appointments?from=2026-11-02&to=2026-11-02" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read one location and reporting date range A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "dentrix-ascend", "tool": "list_appointments", "result": { "location": "Main Street Dental", "appointments": [ { "appointment_id": "apt_40211", "start": "2026-11-02T08:00:00-06:00", "duration_minutes": 60, "patient": "Ava Morales", "patient_id": "pt_1182", "provider": "Dr. Ellis", "operatory": "OP 2", "procedures": [ "D1110", "D0120" ], "status": "Confirmed", "eligibility": "Eligible" } ] } } ``` Replace the dates with your reporting day and read `result.appointments`. The operation reads one location per call without cursor or page-size inputs. Appointment timestamps keep their offset and durations use minutes. Compare confirmation state and timing as well as IDs when preparing an administrative queue. Insurance eligibility covers primary insurance only; Unable to Verify does not mean Ineligible. These reads return no clinical notes, charts, images or prescriptions. ### Dentrix Ascend workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read appointments and unconfirmed appointments into an administrative follow-up queue without sending messages. | | Make | HTTP > Make a request | Read eligibility states into a staff review list that distinguishes Unable to Verify from Ineligible. | | Python or Node.js | REST API | Read outstanding and patient claims into an administrative report without resubmission or clinical interpretation. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Dentrix Ascend; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/dentrix-ascend-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Dentrix Ascend API endpoints and MCP tools ### Schedule and confirmations One location per call. Marking a confirmation records your call; Dentrix Ascend sends the patient nothing. - **List appointments** (`list_appointments`, read): Appointments on the schedule in a date range, with patient, provider and status. - **List unconfirmed appointments** (`list_unconfirmed_appointments`, read): The Unconfirmed Appts list for a day or week, with the last automated reminder. - **List broken appointments** (`list_broken_appointments`, read): Appointments on the Pinboard, ASAP or Broken/No Show list. - **Find patient** (`find_patient`, read): Patients by name, phone or birth date, with status and primary insurance. - **Set confirmation status** (`set_confirmation_status`, write): Marks an appointment Confirmed, Left Message, Unreachable or Unconfirmed. ### Insurance eligibility Primary plans only, as in Dentrix Ascend. A request needs the "Request Eligibility" security right, and a Pro request costs money, so it always asks first. - **List insurance eligibility** (`list_insurance_eligibility`, read): The Insurance Eligibility list for upcoming appointments, by Eligible, Ineligible and Unable to Verify. - **Request eligibility verification** (`request_eligibility_verification`, write, asks first): Asks the payer for a patient's eligibility with Essentials or Pro. ### Recare Active patients by default. A recare note stays inside the practice. - **List recare due** (`list_recare_due`, read): Patients from the Recare Management report, filtered by due date and scheduled recare. - **Add recare note** (`add_recare_note`, write): Adds or replaces the note on a patient's recare type. - **Add patient note** (`add_patient_note`, write): Adds a patient note to the record, up to 5,000 characters. ### Claims and reports Read only. Power Reports show synced data with its "Data as of" time, so the newest entries appear after the next sync. - **List outstanding claims** (`list_outstanding_claims`, read): Unresolved claims from the Outstanding Claims report, with status and age. - **Get patient claims** (`get_patient_claims`, read): A patient's claims from the Insurance Claims page, with status and attachments. - **Run Power Report** (`run_power_report`, read): Runs a report from Power Reporting by name and returns its rows. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/dentrix-ascend-api-mcp-server#tools ## Who can see my Dentrix Ascend session, and how do I revoke it? - **What we store.** Your logged-in Dentrix Ascend profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 13 Dentrix Ascend tools. Never the cookie. - **What the session sees.** What your user role sees: schedule, patients, insurance and reports at your locations. - **What no tool touches.** Clinical notes, charts, images, prescriptions, payments, users and settings. - **If Ascend asks to verify.** MFA sends a code by email or text. You type it in, we never do. - **How to cut access.** Disable for agents, reset the browser, or deactivate the user in Ascend. Patient data is protected health information. Your agreement with Henry Schein One covers it inside Dentrix Ascend; sending it to an AI agent or to Cotlet is your practice's own decision under HIPAA. Cotlet does not sign a BAA. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet. ## Is it against Henry Schein One's rules? Account safety > To protect against bots and non-humans, a user is logged out automatically when there is inappropriate usage. > > [Dentrix Ascend Help, Logging in, checked 27 Oct 2026](https://hsps.pro/DentrixAscend/Help/Logging_in.htm) After such a logout, the next sign-in shows a CAPTCHA and may ask for MFA. Henry Schein One also says it is "strengthening our security to prevent unauthorized connections" from vendors outside its API Exchange, and it sued one such vendor in October 2025 over access to Dentrix desktop databases. Its customer license is not published, so we could not quote it. Cotlet works through the Ascend web app in your own login, but Henry Schein One could still treat it as unapproved access. We found no public case of a practice account closed for this (checked 27 Oct 2026). How we keep your account looking like you: - Your own Dentrix Ascend user, signed in by you - One Cloud Browser with its own IP and cookies, so no new-device check every call - Paid Eligibility Pro requests wait for your OK - No tool deletes, schedules or changes a patient record - If Henry Schein One objects, we pause the Dentrix Ascend tools for everyone within 24 h > If you get a CAPTCHA at sign-in, solve it yourself in the Cloud Browser. Cotlet never solves one. ## What happens when Dentrix Ascend changes? - **12 h** between tests of the Dentrix Ascend reads - **24 h** between tests of confirmations and notes - **$0** for a call to a Dentrix Ascend tool paused for repair Dentrix Ascend is a web app that Henry Schein One updates in place. When a page moves or a column is renamed, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the list.** list_insurance_eligibility for tomorrow, by Unable to Verify, Ineligible and Eligible. 2. **Picks the gaps.** Patients never verified or verified last month. 3. **Waits for your OK.** Each verification request shows up in your Cotlet console first. 4. **Reports the result.** Eligible or not, and whether benefits can be imported. | Action | Undo | |---|---| | Set a confirmation status | Set it again: Unconfirm, Left Message or Unreachable | | Request an Essentials check | No; it only updates the status from the payer's answer | | Request a Pro check | No, and the per-request fee applies | | Add a recare note | Edit the note in the patient Overview | | Add a patient note | Edit or delete it under Patient Information > Notes | 1 of 13 tools asks first: request_eligibility_verification, because a Pro request carries a fee from Henry Schein One. Confirmations and notes stay inside the practice and reach no patient, so they run at once. Switch the wait off per tool for a scheduled run. > Essentials and Pro need an eTrans User ID for the location, and Pro needs a payer connection. Without them the request fails and costs nothing on our side. MCP call: ``` { "name": "request_eligibility_verification", "arguments": { "appointment_id": "apt_40214", "level": "essentials" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/dentrix-ascend/appointments/apt_40214/eligibility-verification/request \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"level":"essentials"}' ``` Tool output: ``` { "appointment_id": "apt_40214", "patient_id": "pt_2045", "level": "essentials", "carrier": "Delta Dental", "result": "Eligible", "verified_at": "2026-10-27T09:12:00-06:00", "import_available": true } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/dentrix-ascend`, with the same key and price. A failed call costs nothing. The tools table lists the REST path of each tool. ## How much does the Dentrix Ascend MCP server cost? **About $29 a month** for a two-dentist location that works its lists every business day, 4,940 credits. Henry Schein One bills Dentrix Ascend and Eligibility Pro as before. | Job | Calls | Credits | |---|---|---| | Check insurance before visits | 5 × 22 | 1,100 | | Work the unconfirmed list | 7 × 22 | 1,540 | | Recare list and notes | 12 × 4 | 480 | | Outstanding claims follow-up | 6 × 4 | 240 | | Production and missed appointments | 2 × 4 | 80 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,940 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No API Exchange membership needed, only a login The month is our example: the eligibility and unconfirmed lists every business day, recare, claims and two reports every week. Henry Schein One does not publish Dentrix Ascend or Eligibility Pro prices. Dollars at the $29 pack rate. ## Dentrix Ascend MCP server: official, vendor or hosted | Option | What it does | Where it stops | |---|---|---| | [Ascend MCP layer](https://www.henryscheinone.com/about-us/press-release/dentrix-ascend-opens-mcp-layer/) | Ask preview for questions in plain language inside Ascend; pre-built agents for eligibility, claims reconciliation and recall gaps. | Agents for select customers; Build has no date; no docs for Claude, ChatGPT or your own agent. | | [Henry Schein One API Exchange](https://www.henryscheinone.com/dental-solutions/api-exchange/api-exchange-vendors/) | Approved vendors connect forms, analytics, communications and AI products through the API. | For vendors, not practices. You buy their product and its workflows. | | Eligibility Pro | Henry Schein One's own add-on: checks payer portals and imports benefits. | Eligibility only, with a per-request or monthly fee. | | GitHub | We found no Dentrix Ascend MCP server or CLI. | Nothing to install. | | Zapier, Make, n8n | We found no Dentrix Ascend app. | Only through a vendor that has its own app. | If your plan includes the MCP agents or Eligibility Pro, use them: they are official and sanctioned. Cotlet is for a practice that wants its own agent on its own lists today, without waiting for the Build layer or buying a vendor product. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Dentrix Ascend tools. ## Dentrix Ascend API and MCP: questions ### Can I use the Dentrix Ascend API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. ### How do I get access? Create a free account at https://cotlet.dev, open Dentrix Ascend under Integrations in the console and log in to Dentrix Ascend in its Cloud Browser. The trial starts with your first app, no card asked. ### Which Dentrix Ascend security rights does the user need? The tools see what your user role sees. Requesting an eligibility check needs the "Request Eligibility" right, the Insurance A/R overview needs "Review Insurance", and Eligibility Pro payer setup needs "Payer Connection Portal" (Dentrix Ascend Help, checked 27 Oct 2026). ### Does an eligibility check cost money? A Pro request does: Dentrix Ascend Help says each Pro request has a per-transaction cost, paid per request or through a monthly package. Essentials uses standard payer data. request_eligibility_verification waits for your approval on every call. ### Is patient data covered by my Henry Schein One agreement? Your agreement with Henry Schein One covers data inside Dentrix Ascend. Sending patient data to an AI agent or to Cotlet is a separate decision for your practice under HIPAA. Cotlet does not sign a BAA. No tool reads clinical notes, charts, images or prescriptions. ### Does it work with Dentrix desktop (G-series)? No. These tools are for Dentrix Ascend, the cloud version you open in a browser. Dentrix desktop runs on a server in your office and has no web login. ### Does it say "recall" or "recare"? Dentrix Ascend calls it recare. Ask your agent either way; list_recare_due reads the Recare Management report. ### Is the MCP server different from the REST API? Only the door is different. Both expose the same 13 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Henry Schein One? No. Cotlet is independent and not affiliated with Henry Schein One or Dentrix. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.