Skip to main content
Glama
oktopeak

intakeq-mcp

by oktopeak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to intakeq-mcp

No user-submitted related servers found.

    Related Servers

    • clio-mcp

      oktopeak
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to Clio practice management, enabling AI-assisted access to matters, contacts, documents, tasks, and billing with audit logging and encryption for law firm compliance.
      88 npm
      24
      MIT

    • clinic-mcp-server

      leomengineer
      F
      license
      A
      quality
      C
      maintenance
      Exposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.
      4
      -

    • PodQuery

      rilhia
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop to query and analyze diabetes data from Omnipod 5 and Glooko through natural language, providing clinical audit and triage insights such as time in range, trends, and bolus analysis.
      12
      MIT

    • careops-mcp

      ZGhey
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude to query and manage home-care operations including clients, visits, and compliance, with schema-validated write tools and a tamper-evident audit log.
      5
      -

    • mycase-mcp

      RosenAdvertising
      A
      license
      C
      quality
      A
      maintenance
      Enables Claude to access and manage your law firm's MyCase account, including cases, clients, tasks, invoices, and more.
      100
      1
      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.7/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: clients, appointments, forms, notes, invoices, files, auth, and audit. The list/get pairs are clearly separate from mutation tools, and no two tools overlap in purpose.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_clients, get_appointment, create_appointment). The only noticeable deviation is 'auth_status' instead of 'get_auth_status', which breaks the pattern slightly.

    Tool Count3/5

    With 22 tools, the server sits in the 16-25 range which is considered heavy. The breadth of IntakeQ's domain (clients, appointments, forms, notes, invoices, files, auth, audit) justifies the count, but it is on the upper edge of what feels appropriate.

    Completeness3/5

    The set covers many resources with list/get operations, and appointments have create/update. However, there are notable gaps: no client creation/update/deletion, no appointment cancellation, and files only expose metadata. These are significant for a practice management workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources