simplepractice-mcp
Related Servers
Alternatives to simplepractice-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides read-only access to a therapy practice's client portal, letting users view upcoming appointments, paperwork requests, standing forms, balances, receipts and secure message threads, and download completed documents and payment receipts as PDFs. It authenticates either with server-side credentials or by relaying requests through the user's already signed-in browser tab, and never sends messages, signs forms, uploads files, or makes payments.17821 npmMIT
- 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.24640 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read a service business's client portal data — clients, projects, tasks, and invoices — for one organization via OAuth sign-in. All six tools are read-only, so assistants can answer questions about overdue invoices, project status, and outstanding balances without changing anything.MIT
- 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.7374 npmMIT
- AlicenseAqualityBmaintenanceEnables read-only FHIR access to Practice Fusion EHR to search patients, appointments, conditions, medications, and lab results.1311 npm4MIT
TDQS
Scored across 15 tools
Each tool has a distinct resource/action target: account, documents, document requests, announcements, appointments, billing items, billing overview, payment methods, and auth/session operations. The two verify tools are clearly split by PIN versus emailed link, and list-vs-get distinctions are well explained.
All tools use the consistent simplepractice_ prefix and snake_case, with mostly predictable verb_noun names such as list_documents and get_account. Minor deviations like session_status and healthcheck are noun-style rather than verb-led, but remain readable and predictable.
Fifteen tools is well within a reasonable range for a client portal server and each tool maps to a meaningful resource or auth step. The set does not feel padded or artificially sparse.
The surface covers authentication, account context, and read-only access to documents, requests, appointments, announcements, and billing. However, it lacks action tools for completing/submitting document requests, requesting appointments, messaging the practice, paying bills, or downloading shared document content, which are notable gaps for a client portal.