Skip to main content
Glama
chrischall

simplepractice-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to simplepractice-mcp

No user-submitted related servers found.

    Related Servers

    • jobber-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      7
      252 npm
      MIT

    • cronometer-core

      johnkattenhorn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • librus-mcp

      TechAdrianPro
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only access to a Librus Portal account, letting users list linked Synergia accounts and retrieve grades, attendance, timetable, homework, notices, and school information.
      3
      -

    • benepass-mcp

      brian7989
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Benepass employee-web API, allowing users to view HSA accounts, investments, transactions, documents, and benefits without write operations.
      13
      158 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource or step: collection reads use list_*, single-item reads use get_*, auth tools are separated by link versus PIN, and session_status/healthcheck are clearly local versus network diagnostics. Descriptions draw clear lines between similar-sounding pairs like document_requests versus documents and billing_overview versus billing_items.

    Naming Consistency4/5

    The simplepractice_ prefix and snake_case are used throughout, and most tools follow a verb_noun pattern such as list_appointments, get_account, or verify_sign_in_token. Minor deviations are session_status and healthcheck, which are noun-style names rather than verb-first actions.

    Tool Count5/5

    Fifteen tools sits at the upper end of the well-scoped range, but every tool has a distinct job: three auth tools, three session/diagnostic helpers, and focused list/get tools for each Client Portal resource. No tool appears redundant or purely decorative.

    Completeness3/5

    The read-side is broad: account, appointments, billing, payment methods, document requests, documents, and announcements are all represented. However, the server is almost entirely read-only; there is no way to submit answers to a document request, make a payment, add a payment method, or otherwise complete a client action, leaving important portal workflows as dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources