Skip to main content
Glama

Related Servers

Alternatives to clio-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      141 npm
      26
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure access to legal documents from Clio via Claude Desktop, with local processing and semantic search to ground AI responses in actual documents.
      0
      29
      Mozilla Public 2.0
    • F
      license
      B
      quality
      C
      maintenance
      A standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.
      46
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude (or any MCP client) to read and write Clio Manage data—contacts, matters, activities—directly from chat, with flat-fee billing support in one call.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and, on explicit request, create or update legal practice management data through the Clio Manage API, covering matters, contacts, time and expense entries, tasks, communications, document metadata, calendar entries, and bills.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude Desktop to a running AutoCAD instance over local Windows COM, letting users query, draw, edit, organize layers, measure areas, take off quantities, and export sheets to PDF using plain language. Every action is undoable, logged, and optionally restricted to read-only mode with no network exposure.
      MIT

    TDQS

    B3.2/5.0

    Scored across 55 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear separation between matter, contact, document, billing, time, task, and calendar operations. A few areas overlap (document creation/upload/write variants, time entry vs. timer vs. activity update), but descriptions provide enough detail to choose correctly.

    Naming Consistency4/5

    The dominant pattern is clio_<resource>_<action> in snake_case (e.g., clio_matter_get, clio_task_create), applied consistently across most domains. Minor deviations exist, such as clio_activity_update for time entries, clio_who_am_i, clio_describe_api, and clio_outstanding_balances.

    Tool Count2/5

    55 tools is heavy and well above the ideal 3–15 range, risking agent overload and selection difficulty. The breadth of Clio Manage justifies many tools, but the set could likely be consolidated (especially document and lookup tools).

    Completeness3/5

    Core create/read/update coverage is strong across matters, contacts, documents, time, tasks, calendars, notes, and billing. However, delete/removal operations are absent for nearly every resource and DELETE is explicitly disallowed, leaving lifecycle gaps that agents cannot work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues