Skip to main content
Glama

Related Servers

Alternatives to Glasscubes MCP server

No user-submitted related servers found.

    Related Servers

    • 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
      C
      maintenance
      Enables AI assistants to read, search, and create/edit legal practice management data in Projuris ADV, including cases, people, tasks, updates, timesheet, files, contracts, subjects, court notices, service records, finance, and users via REST.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read, create, and update legal practice data—cases with history and movements, clients, tasks, and financial transactions—using the firm's API token.
      MIT
    • 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.
      138 npm
      25
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jurisly workspaces for tasks like drafting invoices, finding hearing dates, and editing documents through natural language.
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, with clean get/list pairs (get_workspace vs list_workspaces, get_task vs list_tasks, get_information_request vs list_information_requests). The only mild overlap is between the singular information-request reader and the workspace-scoped list, but the descriptions distinguish them clearly enough.

    Naming Consistency5/5

    Every tool follows the same snake_case verb_noun pattern (get_* / list_*) throughout. There are no mixed conventions or vague verbs.

    Tool Count5/5

    11 tools is well within the ideal range and each one maps to a distinct resource or view. Nothing feels redundant or padded.

    Completeness4/5

    The read surface is broad, covering workspaces, members, labels, information requests, templates, tasks, files and calendar events. The main gap is the absence of any write/mutation operations (creating tasks, uploading files, commenting), though the server appears intentionally read-only, so agents can work within these bounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues