Skip to main content
Glama
nate-raubenheimer

LawPracticeZA MCP

by nate-raubenheimer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to LawPracticeZA MCP

No user-submitted related servers found.

    Related Servers

    • practicepanther-mcp

      sanjibani
      A
      license
      B
      quality
      D
      maintenance
      MCP server for PracticePanther legal practice management software. Enables reading and creating matters, contacts, time entries, invoices, and more via natural language.
      26
      1
      MIT

    • Astrea (Aurum)

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for read-only queries and reports from the Astrea (Aurum) legal software. Enables retrieving case information by client, new cases per month, tags, financials (fees/expenses), schedule (hearings, meetings, deadlines, tasks), and case updates for client reports.
      9
      MIT
    • BillingServ MCP by BillingServ

      BillingServ MCPofficial

      BillingServ
      A
      license
      A
      quality
      C
      maintenance
      This is an MCP server for the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, and reports straight from your BillingServ installation
      3
      35 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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    All eight tools have clearly distinct purposes: health check, client creation, matter creation/update, transfer creation, listing unbilled items, and upsert/delete of draft fees. No two tools could be confused, and the descriptions reinforce their specific roles.

    Naming Consistency5/5

    Every tool follows the consistent pattern 'lpza_' + verb + noun (e.g., create_client, update_matter, list_unbilled, delete_draft_fee). The verb-noun structure is uniform and predictable across the entire set.

    Tool Count5/5

    Eight tools is well within the ideal range for a focused domain server. Each tool covers a distinct operation needed for managing clients, matters, and unbilled fees without unnecessary redundancy or bloat.

    Completeness4/5

    The domain is well covered for core workflows: client creation, matter creation/update, transfer creation, and draft fee lifecycle (upsert/delete/list). Minor gaps include missing client read/update/delete, matter delete/list, and a dedicated matter get, but these can be worked around using existing tools (e.g., update_matter fetches detail).

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources