A
licenseA
qualityA
maintenanceEnables read-only access to SimplePractice Client Portal data — appointments, billing, documents, and announcements — via the portal's JSON:API, using passwordless portal sign-in.
15
235 npm
MIT
TherapyPortal MCP Server
by chrischall
Related Servers
Alternatives to TherapyPortal MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityAmaintenanceEnables 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.23118 npm1MIT
- AlicenseAqualityAmaintenanceConnects an AI assistant to an InSync Healthcare (Qualifacts) patient portal, letting the signed-in user read their appointments, medications, allergies, messages, forms, surveys, documents, profile and balance, and download portal files. It also sends confirm-gated secure messages, refill and appointment requests, cancellation requests, and uploads an insurance card to their own profile.26908 npmMIT
- AlicenseAqualityCmaintenanceGives AI agents read-only access to patient context on any FHIR R4 server, including journey timelines of encounters and appointments, open booking slots, and discharged patients whose follow-ups were never booked. Search, appointment, and follow-up tools return compact summaries, so agents can answer front-desk and outreach questions without write access.5MIT
- 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.70MIT
TDQS
A3.9/5.0
Scored across 16 tools
Disambiguation4/5
Most tools have clearly distinct resource+action targets (list_message_threads vs get_thread_messages vs reply_message, download_document vs download_receipt). The main friction is the cluster of list_documents / list_forms / get_document_counts, which all concern paperwork and require reading descriptions carefully to separate 'practice-sent requests', 'standing library forms', and 'aggregate counts'. send_message vs reply_message is well delineated by explicit cross-references.
Naming Consistency4/5
Nearly all tools follow a consistent therapyportal_verb_noun pattern with predictable verbs (list_, get_, download_, upload_, send_, reply_). The only deviations are therapyportal_healthcheck (noun, no verb) and get_document_counts vs list_documents being distinguished only by verb choice, but overall the convention is readable and stable.
Tool Count4/5
16 tools is slightly above the comfortable 3-15 band but each covers a distinct portal surface (clients, messages, documents, forms, balances, appointments, receipts) and seems to earn its place. No obviously redundant or filler tools beyond possibly the diagnostics healthcheck.
Completeness3/5
Read and write coverage for messaging and document upload/download is solid, and billing/balance/appointment listing exist. However there are notable lifecycle gaps: no tool to sign a document requiring a signature (upload_document explicitly refuses signatures), no way to book or cancel an appointment request, and no payment capability despite balances being listed. The server also lacks any mark-read operation even though reply_message references read state.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive