Skip to main content
Glama
RosenAdvertising

rocketmatter-mcp

by RosenAdvertising
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rocketmatter-mcp

No user-submitted related servers found.

    Related Servers

    • MyCase MCP Server

      oktopeak
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects Claude to MyCase legal practice management, enabling natural language queries for cases, contacts, calendar, billing, and more.
      55 npm
      3
      MIT

    • lawmatics-mcp

      oktopeak
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude to Lawmatics legal CRM, enabling natural-language queries and management of matters, contacts, pipeline data, tasks, intake forms, and more without leaving the conversation.
      37
      22 npm
      MIT

    • 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

    • legal-mcp

      jscottym
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables US case law search, citation parsing, practice management via Clio, and federal court filings through PACER.
      -

    • jurisly-mcp

      omnimorphpvtltd
      A
      license
      Not graded
      quality
      C
      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
    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

    C2.3/5.0

    Scored across 86 tools

    Disambiguation2/5

    Many tools are explicitly marked as failing, but they coexist with working counterparts (e.g., create_invoice vs generate_invoice, list_billable_items vs create_invoice). This creates confusion, as an agent cannot easily distinguish functional from non-functional tools without inspecting descriptions. Additionally, several lookups (e.g., get_time_entry_lookups) overlap with get_time_entry.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (snake_case) for most tools, such as create_client, list_clients, delete_client. There are minor deviations like get_document_download_url and get_client_suggestions, but the overall pattern is predictable.

    Tool Count1/5

    With 86 tools, the server is severely bloated. Many are non-functional placeholders (marked '[Not in LCS /v1]'), and the working set is around 30-40 tools, which is still high. The number overwhelms the agent and degrades usability.

    Completeness2/5

    The working tools cover basic CRUD for clients, matters, contacts, time entries, expenses, invoices, payments, and transactions. However, critical operations like document upload/download, AP management, financial summaries, and many lookups are either missing or fail. The surface has significant gaps for a legal practice management domain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources