Skip to main content
Glama
ZGhey

careops-mcp

by ZGhey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to careops-mcp

No user-submitted related servers found.

    Related Servers

    • intakeq-mcp

      oktopeak
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to access IntakeQ practice management data including scheduling, intake forms, treatment notes, invoices, and client records with HIPAA-compliant audit logging.
      22
      60 npm
      MIT

    • clinic-mcp-server

      leomengineer
      F
      license
      A
      quality
      C
      maintenance
      Exposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.
      4
      -
    • 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.
      -

    • bookings-mcp

      satviksriv
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to manage a service business front desk by searching customers, checking real-time availability, creating and canceling appointments without double-booking, and generating revenue reports from actual data.
      9
      MIT

    • PodQuery

      rilhia
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop to query and analyze diabetes data from Omnipod 5 and Glooko through natural language, providing clinical audit and triage insights such as time in range, trends, and bolus analysis.
      12
      MIT
    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

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: compliance checking, client retrieval, client listing, scheduling, and audit verification. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (check_compliance, get_client, list_clients, schedule_visit, verify_audit_log). No mixing of conventions.

    Tool Count5/5

    With 5 tools covering compliance, client management, scheduling, and audit, the count is well-scoped for the care operations domain. Each tool adds clear value.

    Completeness4/5

    The tool set covers key workflows: compliance checks, client lookup, visit scheduling, and integrity verification. Minor gaps exist (e.g., no tool to update or cancel a visit), but the core lifecycle is supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources