App

Dentally integrations

Connect Dentally to any other app, or use it from your AI client over MCP. Dentally is amazing dental software for practice management created for private and NHS dental practices.

Connects with a tokendentally.co

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want to automate with Dentally?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Grok

Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Pair it

Connect Dentally with another app

What your agent can do with Dentally

Triggers and actions 4 triggers · 42 actions

  • Trigger
    New Appointment

    Triggers when a new appointment is booked.

  • Trigger
    New Invoice

    Triggers when a new invoice is raised.

  • Trigger
    New Patient

    Triggers when a new patient is added to the practice.

  • Trigger
    New Payment

    Triggers when a new payment is recorded.

  • Action
    Cancel an appointment

    Cancels the appointment matching `id` for the practice identified by `X-Practice-Id`. The appointment `state` is set to `Cancelled` and `cancelled_at` is recorded.

  • Action
    Create an appointment

    Creates a new appointment for the practice identified by `X-Practice-Id`. The appointment location (`site_id`) is determined by the site of the practitioner specified in `practitioner_id`. On success, the newly created appointment is returned in the `data` envelope with a state of `Pending`.

  • Action
    Get appointment by ID

    Returns the **single appointment** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing appointments.

  • Action
    Get calendar zone by ID

    Returns the single calendar zone matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing calendar zones.

  • Action
    Get fee by ID

    Returns the **single fee** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing fees. If no fee exists for that practice and `id`, the API responds with **404**.

  • Action
    Get fee schedule by ID

    Returns the single fee schedule matching `id` for the practice identified by `X-Practice-Id`. Dentally's user interface in the United Kingdom sometimes calls this a payment plan. The identifier is the same `id` returned when listing fee schedules.

  • Action
    Get invoice by ID

    Returns the **single invoice** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing invoices.

  • Action
    Get NHS contract by ID

    Returns the single NHS contract matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing NHS contracts.

  • Action
    Get patient account balance

    Returns the account balance for the patient matching `id`, for the practice identified by `X-Practice-Id`. The balance is the account the patient's invoices and payments are posted to. The `id` is the same patient `id` returned when listing patients. Monetary amounts are signed. A negative amount me

  • Action
    Get payment by ID

    Returns the payment matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing payments. If no payment exists for that practice and `id`, the API responds with 404.

  • Action
    Get practitioner by ID

    Returns the **single practitioner** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing practitioners.

  • Action
    Get response details

    Returns the details of a **single response communication** to a communication matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when [creating an SMS communication](#operation/send-communication).

  • Action
    Get site by ID

    Returns the **single site** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing sites.

  • Action
    Get the current practice

    Returns the **current practice**: the practice identified by the `X-Practice-Id` header.

  • Action
    Get treatment appointment by ID

    Returns the **single treatment appointment** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment appointments. If no treatment appointment exists for that practice and `id`, the API responds with **404**.

  • Action
    Get treatment by ID

    Returns the single treatment matching `id` for the practice identified by `X-Practice-Id`. Treatments are practice-wide. The identifier is the same `id` returned when listing treatments.

  • Action
    Get treatment category by ID

    Returns the single treatment category matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment categories.

  • Action
    Get treatment plan by ID

    Returns the **single treatment plan** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment plans. If no treatment plan exists for that practice and `id`, the API responds with **404**.

  • Action
    List allocations for a payment

    Returns a **paginated** list of payment allocations for the payment identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort. Use `limit` and the `met

  • Action
    List appointment cancellation reasons

    Returns a **paginated** list of appointment cancellation reasons for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List appointment reasons

    Returns a **paginated** list of appointment reasons for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List appointments

    Returns a **paginated** list of appointments for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List calendar zones

    Returns a paginated list of calendar zones for the practice identified by `X-Practice-Id`. A calendar zone is one occurrence of a scheduled, recurring block of diary time reserved for a specific purpose, for a practitioner or a room.

  • Action
    List fees

    Returns a **paginated** list of fees for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort. Optional query parameters allow filtering by fee schedule, treatment, and created/updated

  • Action
    List fee schedules

    Returns a paginated list of fee schedules for the practice identified by `X-Practice-Id`. Dentally's user interface in the United Kingdom sometimes calls these payment plans.

  • Action
    List invoice items

    Returns a **paginated** list of invoice items for the invoice identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List invoices

    Returns a **paginated** list of invoices for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, most recent created first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List NHS contracts

    Returns a paginated list of NHS contracts for the practice identified by `X-Practice-Id`.

  • Action
    List patients

    Returns a paginated list of patients for a practice.

  • Action
    List payments

    Returns a paginated list of payments for the practice identified by `X-Practice-Id`. Results are ordered by creation time, newest first (`created_at` descending), then by `id` descending for a stable sort. Use `limit` and the `meta.cursor` value from the response to retrieve further pages.

  • Action
    List practitioner availabilities

    Returns a **paginated** list of **availability slots** for one or more practitioners.

  • Action
    List practitioners

    Returns a **paginated** list of practitioners for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List rota schedule histories

    Returns a **paginated** list of **snapshot rota days** for the practitioner identified by `id` in the path. Each row describes the effective scheduled working hours and breaks for a single calendar date, as captured from the practice rota (including overrides that were active when the snapshot was t

  • Action
    List sites

    Returns a **paginated** list of all sites for the practice identified by `X-Practice-Id`. Use this to discover locations where the practice operates, including addresses, contact details, and opening hours.

  • Action
    List sundries

    Sundries are non-treatment items, such as toothbrushes or other products, that a practice sells and adds to invoices. Returns a **paginated** list of sundries for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id

  • Action
    List treatment appointments

    Returns a **paginated** list of treatment appointments for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List treatment categories

    Returns a **paginated** list of treatment categories for the practice identified by `X-Practice-Id`. Treatment categories are the folders a practice uses to group its treatment catalogue.

  • Action
    List treatment plan items

    Returns a **paginated** list of treatment plan items for the treatment plan identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List treatment plans

    Returns a **paginated** list of treatment plans for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.

  • Action
    List treatments

    Returns a **paginated** list of treatments for the practice identified by `X-Practice-Id`. Treatments are the practice-level catalogue of procedures that can be assigned to a patient treatment plan.

  • Action
    Search patients

    Returns a paginated list of patients for a practice, with optional filters.

  • Action
    Update an appointment

    Updates the appointment matching `id` for the practice identified by `X-Practice-Id`. Only the fields provided in the request body will be modified; omitted fields remain unchanged. If no appointment exists for that practice and `id`, the API responds with **404**. When `reason_id` is provided, it m

Reviews

What our customers say

Questions

Dentally, answered

Is there a Dentally MCP server?

APIANT's MCP server at https://mcp.apiant.ai works with Dentally. Add that address to any AI client that takes a remote MCP server and sign in once in your browser. Your client can then run Dentally actions on demand, or have APIANT build, test and run automations that use Dentally. Nothing to install.

What can start an automation from Dentally?

Any of Dentally's 4 triggers in the catalog, including New Appointment, New Invoice, New Patient and New Payment. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Dentally?

Any of Dentally's 42 actions, including Create an appointment, Update an appointment, Get appointment by ID and Get calendar zone by ID. Your agent maps the data both ways and tests every scenario before it ships.

Can I use Dentally directly from Claude, ChatGPT or Cursor?

Yes. Connect your AI client to APIANT once and it works with Dentally two ways. Ask it to do something in Dentally once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running on its own. A one-off action uses your plan's tasks the same way an automation step does.

Do I need to write code against the Dentally API?

No. APIANT connects to the Dentally API for you, with a token. Describe what you want in plain language and your agent builds it on the Dentally triggers and actions in the catalog. If you need an endpoint that is not there yet, your agent reads the Dentally API documentation and adds it.

Which apps can Dentally connect to?

Any app in the catalog; the list on this page pairs Dentally with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.