Skip to main content
Glama
NoBanks

ezyVet MCP Server

by NoBanks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ezyVet MCP Server

No user-submitted related servers found.

    Related Servers

    • vClinic MCP Server by v-clinic

      vClinic MCP Serverofficial

      v-clinic
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage virtual clinic data including patients, visits, diagnoses, treatments, lab/radiology orders, and search medical literature and internal knowledge base.
      -

    • mcp-cliniko

      andymillar84-cyber
      F
      license
      B
      quality
      D
      maintenance
      Provides integration with the Cliniko API for healthcare practice management, enabling patient, appointment, invoice, and payment operations via natural language.
      27
      -

    • ezyVet MCP

      sanjibani
      A
      license
      B
      quality
      D
      maintenance
      MCP server for ezyVet veterinary practice management. Enables reading and creating animals, contacts, appointments, consults, and invoices via natural language.
      17
      MIT

    • CharmHealth MCP Server

      talharazzaq-sudo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through an EHR API. It provides 16 tools for clinical, administrative, and communication workflows including appointments, medications, labs, tasks, messaging, and fax.
      MIT
    • xyte-mcp by xyte-io

      xyte-mcpofficial

      xyte-io
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to discover and call Xyte's device management API endpoints with typed validation, supporting fleet investigation, ticket management, and routine operations through natural language.
      3
      3 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct entity (appointments, animals, consults, contacts, invoices, products) with clear read/write boundaries, so no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_appointment, list_animals), making the set predictable.

    Tool Count5/5

    With 8 tools covering core entities in a veterinary practice system, the count is well-scoped and neither sparse nor excessive.

    Completeness2/5

    The tool set is read-heavy and lacks update/delete operations for most entities, and only appointments have a create function, leaving significant lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources