simplepractice-mcp
Related Servers
Alternatives to simplepractice-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables reading a patient's own Epic MyChart portal data — test results, medications, allergies, immunizations, health issues, goals, visits, messages, insurance, care team and billing — by relaying requests through the signed-in browser tab or signing in server-side with human-in-the-loop MFA. It also lets the active patient reply to Message Center conversations after an explicit confirmation step.24589 npm1MIT
- AlicenseAqualityCmaintenanceLets AI assistants connect securely to a professional-services client portal to review workspaces, outstanding document requests, tasks, file and folder metadata, members, and calendar events, plus optionally create tasks and update their states when writes are allowed.11MIT
- AlicenseAqualityAmaintenanceEnables Claude to read appointments, invoices, quotes, and work requests from a Jobber Client Hub. Read-only, uses a local browser bridge to access the customer portal.7537 npmMIT
- AlicenseAqualityAmaintenanceEnables read-only FHIR access to Practice Fusion EHR to search patients, appointments, conditions, medications, and lab results.1311 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables clinical teams to list patients with active sharing and read glucose, graph, logbook, and statistics from LibreLink Up, with secure magic-link login and encrypted credentials.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude to securely read your own Cronometer nutrition and biometric data using your account credentials, with read-only access and optional human-readable output.MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions, but list_documents vs list_document_requests could be confused by name, and healthcheck vs session_status both feel like status checks. Descriptions are strong enough to resolve these in practice.
All tools share the simplepractice_ prefix and mostly follow a verb_noun pattern like list_*, get_*, and verify_sign_in_*. healthcheck and session_status break the pattern slightly, but overall naming is readable and predictable.
15 tools is at the upper edge of the ideal range, but each tool covers a meaningful portal area: authentication, account, appointments, billing, documents, document requests, and announcements. There is no obvious redundancy.
The toolset provides solid read-only coverage of Client Portal workflows, including auth lifecycle, account details, and list/get operations across major data categories. It lacks write/submit actions like completing a document request or paying an invoice, and some lists have no detail getter, but those are workable gaps rather than fatal ones.