ezyVet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EZYVET_SCOPE | Yes | Scope string, e.g. read-animal read-contact read-appointment read-consult read-invoice read-user | |
| EZYVET_SITE_UID | Yes | Site UID for your practice | |
| EZYVET_CLIENT_ID | Yes | Client ID from ezyVet | |
| EZYVET_PARTNER_ID | Yes | Partner ID from ezyVet integration registration | |
| EZYVET_CLIENT_SECRET | Yes | Client secret from ezyVet |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_animalA | Fetch a single animal (patient) by ezyVet ID. |
| find_animalsB | Search animals by name / species / breed. Returns the standard
|
| create_animalB | Create a new animal (patient). |
| update_animalA | Patch an animal record. |
| get_contactC | Fetch a contact (the pet owner) by ID. |
| find_contactsC | Search contacts by name or email. |
| create_contactC | Create a new contact (owner). |
| find_appointmentsB | List appointments. Use |
| create_appointmentC | Book a new appointment. |
| find_consultsC | List clinical consults (visits). |
| create_consultC | Open a new clinical consult (visit record). |
| find_invoicesC | List invoices, optionally filtered by contact and date range. |
| list_speciesA | List animal species (dog, cat, rabbit, etc.). |
| list_breedsB | List animal breeds. |
| list_appointment_typesA | List appointment type definitions (consult, vaccination, surgery, etc.). |
| list_usersA | List practice users (vets, nurses, receptionists). |
| health_checkB | Verify credentials by minting an OAuth token and listing users. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct resource-action pair (e.g., create_animal, find_animals, get_animal, update_animal), with no overlapping purposes. All tools are clearly separable.
All tool names follow a consistent verb_noun pattern in snake_case. Create/find/get/update for nouns, and list_ for type enumerations, with no mixing of styles.
17 tools is well-scoped for a veterinary practice management server. Each tool serves a distinct purpose, covering animals, appointments, consults, contacts, invoices, and administrative lists without unnecessary bloat.
The set covers core CRUD for animals but misses update and delete for appointments, consults, contacts, and invoices. Creation and reading are well-covered, but missing mutability options create gaps for typical workflows.