ClinicFlow AI
Related Servers
Alternatives to ClinicFlow AI
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides tools to check appointment availability and format call summaries via stdio MCP transport.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to check clinic hours, list open slots, find the next available slot, and create idempotent appointment bookings at HeyDenta clinics through natural language tool calls. Runs over stdio or Streamable HTTP with built-in auth, retries, and a duplicate-booking guard.MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools to list valid appointment slots, schedule, reschedule, and cancel appointments under a clinic's business policy (hours, buffers, minimum notice, practitioner availability).1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to read bookings, check availability and session conditions, and prepare unsaved booking, cancellation or waitlist previews for a TheirCare / FullyBooked account through a local stdio MCP connection. Final saving and terms acceptance are deliberately left to the user, who confirms them personally in the bundled local companion web interface.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts that require a local stdio process to connect to the hosted public demo, forwarding tool discovery and calls for fictional scheduling scenarios, product information, draft-sharing preparation, and optional feedback.MIT

Daykeeper MCPofficial
AlicenseAqualityAmaintenanceA local stdio MCP adapter for the Daykeeper management API. It uses separately issued scoped credentials and exposes read-only tools by default; planning and mutations require explicit opt-in.826 npmApache 2.0
TDQS
Scored across 2 tools
The two tools are clearly separable: one is a read-only listing of slots, the other a validation/proposal action that produces a human-confirmation artifact. There is mild overlap since both operate on appointment slots, but a caller can reliably pick the right one.
Naming styles are mixed: 'available_appointments' is an adjective+noun phrase while 'propose_appointment' follows a verb_noun pattern. Both remain readable and snake_case is consistent, but there is no single predictable convention.
Two tools is thin even accounting for the deliberate human-in-the-loop safety constraint. The pair covers discovery and proposal, but the surface feels minimal for a clinic booking domain.
Only listing and proposing exist; there is no way to confirm a proposal, cancel, reschedule, or fetch details of a specific appointment. Some of this is intentionally offloaded to a human, but an agent will hit dead ends for common follow-up operations.