Skip to main content
Glama
sanjibani

practicepanther-mcp

by sanjibani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to practicepanther-mcp

No user-submitted related servers found.

    Related Servers

    • clio-mcp

      WYRE-AI
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Clio Manage that enables interaction with legal practice data including matters, contacts, activities, communications, tasks, documents, calendar entries, and bills via natural language.
      -

    • moxie-mcp

      SabryParra
      F
      license
      B
      quality
      C
      maintenance
      MCP server for Moxie CRM that enables managing clients, projects, invoices, tasks, time tracking, expenses, and more through natural language.
      30
      -

    • bill4time-mcp

      RosenAdvertising
      A
      license
      C
      quality
      A
      maintenance
      MCP server for Bill4Time providing API coverage for legal billing and time tracking, enabling natural language interaction with clients, projects, time entries, invoices, payments, and more from Claude Desktop.
      59
      1
      MIT

    • LawPracticeZA MCP

      nate-raubenheimer
      A
      license
      A
      quality
      B
      maintenance
      MCP server for LawPracticeZA, South African legal practice software, providing tools to manage clients, matters, work-in-progress fees, billing, and accounting via the LawPracticeZA API.
      8
      GPL 3.0

    • ghl-mcp

      craig248
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.
      -
    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

    B3.3/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action (e.g., create_account vs create_contact, find_matters vs find_tasks). Verbs (create, find, get, list, update) clearly separate creation, search, retrieval, and modification. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: verbs are imperative (create, find, get, list, update, health_check) and nouns are plural for list/find operations (e.g., find_accounts, list_users) and singular for create/get/update (e.g., get_matter, create_invoice). No mixing of styles or unexpected abbreviations.

    Tool Count4/5

    With 26 tools, the count is on the high end but justified for a comprehensive legal practice management system covering accounts, matters, contacts, activities, invoices, time entries, tasks, events, and reference lists. The scope is broad, and each tool serves a distinct purpose, making the count reasonable.

    Completeness3/5

    The server provides create, get/list/search for most entities but is missing update operations for accounts, contacts, activities, tasks, and events (only matter and time entry have update). There are no delete or archive tools, which are notable gaps for a CRUD-like lifecycle. Reference lists (expense categories, practice areas, users) are present but not modifiable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources