Skip to content
Custom Connectors

Full read-write Claude connector for ezyVet

Make Claude run front-desk admin in ezyVet

Vet clinics lose hours a day to lookups, bookings, and billing chases in ezyVet. A custom connector puts Claude on that work with scoped API access, and every change to the record or the calendar waits for your approval.

ezyVet, part of IDEXX, is cloud practice management software for veterinary clinics and hospitals, holding animal records, owner contacts, the appointment book, consults, and invoicing. Teams want Claude on the front-of-house work: looking up patients and owners, managing the day's bookings, and keeping contact details and billing follow-up current.

What is an ezyVet MCP server?

An ezyVet MCP server is a small hosted service that exposes ezyVet's data and actions to Claude over the Model Context Protocol, so Claude can operate industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can ezyVet's current connector do today?

Today, ezyVet does not ship a first-party Claude or MCP connector, so reaching it from Claude means a custom integration against the ezyVet partner API, and hand-wired access tends to be read-leaning. A purpose-built ezyVet connector adds scoped write actions like booking appointments and updating contacts, with separated tools and approval on anything changed or sent.

What does full read-write ezyVet access unlock?

Full read-write means Claude can run the desk between consults. It can pull an animal's record and vaccination history, book or move an appointment, correct an owner's phone number, attach a referral document to the record, and summarize open invoices by client, all inside the scopes granted to the API credentials.

  • Look up an animal's record, owner contact details, and vaccination history
  • Pull today's appointment list by resource and flag gaps or no-shows
  • Book or reschedule an appointment, after you approve the slot
  • Update an owner's contact details, like phone and email, after you approve
  • Summarize open invoices and outstanding balances by client
  • Attach a document, like a referral summary, to a clinical record, for your review

Can Claude look up patient records in ezyVet?

Yes, Claude can pull an animal's record through the ezyVet API, including owner contact details and vaccination history, and answer questions like which patients are overdue or which owner a callback belongs to. Reads are separated from writes, so lookups never change anything.

Can Claude book appointments in ezyVet?

Yes, Claude can read the appointment book, find an open slot for the right resource, and create or reschedule the booking once you approve it. It verifies the animal and owner first, and no booking is made or moved without a human confirming.

Can Claude help with invoicing in ezyVet?

Yes, Claude can pull invoices from the API, summarize open balances by client, and draft follow-up messages for your review. It keeps the receivables picture current and the follow-up queue ready. Nothing is sent to a client without your approval.

How an ezyVet connector works

We build a small MCP server that authenticates to the ezyVet API with OAuth 2.0 client credentials, requesting only the scopes your clinic's workflows need, so the connector holds exactly the access ezyVet granted and nothing more. Read tools and write tools are separated: looking up animals, owners, and the schedule can never modify a record. Writes like booking or editing contacts are explicit tools, and destructive or outbound actions are gated behind human approval. The server runs as a remote connector your team adds to Claude.

Frequently asked questions

Does ezyVet have a Claude or MCP connector?
No first-party one exists. ezyVet publishes a partner REST API with OAuth 2.0 access at developers.ezyvet.com, but neither ezyVet nor IDEXX ships an official Claude connector, and none is listed in the Claude connector directory. A custom connector built against the partner API gives your clinic that access on your terms: scoped credentials, separated read and write tools, and approval gates on anything that changes the record.
Is connecting Claude to ezyVet safe for clinic data?
Access runs through ezyVet's own OAuth credential system, where each credential carries specific scopes, so the connector can never exceed what your clinic authorized. On top of that we separate reads from writes, require approval on destructive or outbound actions, and keep the connector's job administrative: scheduling, record upkeep, and billing follow-up. Treatment decisions and clinical judgement stay entirely with your veterinary team.
Can Claude manage veterinary appointments in ezyVet?
Yes. The ezyVet API exposes the appointment book, so Claude can read today's list by resource or clinician, flag gaps and no-shows, and create or reschedule bookings once you approve each change. Paired with animal and contact lookups, it can confirm it has the right patient and owner before touching the calendar, which is where most manual booking mistakes happen.

Using Claude Code?

The same connector works in the terminal: connect ezyVet to Claude Code.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.