Carebit MCP server
Related Servers
Alternatives to Carebit MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables integration with the Cliniko practice management system through MCP tools and resources. Supports patient management, appointment scheduling, and practice data access through natural language interactions.-
- AlicenseAqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to look up members, their memberships and credentials, events and event bookings, and clubs and other organisations in a sports membership platform, and, when writes are enabled, to change the dates of a member's membership.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to search a membership database's people and organisations, read a contact's summary and membership history, list events with ticket types and attendance lists, read invoices, and find and count segments. When writes are enabled, it also lets clients record who attended an event.MIT
- AlicenseAqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to read a financial adviser's CRM data—clients, households, reviews due, tasks, cases, plans and notes—and, when writes are enabled, create tasks and notes.14MIT
- FlicenseBqualityDmaintenanceProvides integration with the Cliniko API for healthcare practice management, enabling patient, appointment, invoice, and payment operations via natural language.27-
TDQS
Scored across 15 tools
Most tools target distinct resources or actions, but the scheduling-related tools (get_clinician_agenda, find_availability, list_bookings) all return diary, availability, or booking data, creating some risk of misselection. The descriptions help clarify boundaries, but the overlap is not fully eliminated.
All tool names use snake_case with a consistent verb_noun pattern (get_, list_, search_, find_). The verbs are semantically appropriate and predictable, with no mixing of conventions.
15 tools is at the upper end of the typical 3-15 range and covers most entities in the clinic domain. Each tool earns its place, though some list/get pairs could potentially be consolidated without losing functionality.
The surface is almost entirely read-only and misses key lifecycle operations: no create_booking despite being referenced by find_availability and list_services, no update or cancel booking, no patient creation, and no invoice or payment write actions. These gaps would block common clinic workflows and cause agent failures.