Connect ezyVet to Claude Code

Make Claude run front-desk admin in ezyVet. From the terminal, inside the sessions where you already work.

How do you connect ezyVet to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ezyVet, you add a ezyVet MCP server: a small hosted service that exposes ezyVet's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ezyVet account. No API keys pasted into config files.

claude mcp add --transport http ezyvet https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ezyVet once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ezyVet access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ezyVet API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ezyVet changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ezyVet connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ezyVet connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ezyVet account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ezyVet's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to ezyVet?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ezyVet account it signs in with. Revoking access is one click in ezyVet.

More on the ezyVet connector

ezyVet connector for claude.ai Jane + Claude Code Acuity Scheduling + Claude Code QuickBooks Online + 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.

Build my connector Talk to us