Skip to main content
Glama
oktopeak

filevine-mcp

by oktopeak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to filevine-mcp

No user-submitted related servers found.

    Related Servers

    • filevine-mcp

      Advocate-Cloud-Solutions
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Filevine matter management and Lead Docket intake APIs as natural-language-callable tools, enabling legal teams to query, update, and create projects and leads directly from Claude.
      Apache 2.0

    • clio-mcp

      ToddHebebrand
      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
      -

    • clio-mcp

      evanwillistech
      F
      license
      Not graded
      quality
      C
      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.
      -

    • Clio Manage MCP

      patrickking67
      A
      license
      A
      quality
      C
      maintenance
      MCP server that connects Clio Manage to Claude via OAuth, enabling law firm management tasks like matter lookup, time tracking, billing, calendar, and document retrieval through natural language.
      41
      MIT

    • clio-mcp

      lawyered0
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Clio Manage legal practice management software that enables Claude and other MCP clients to read and write Clio data including contacts, matters, and activities directly from chat.
      8
      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

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (cases, notes, contacts, documents, tasks, collections, auth). The few overlapping areas like list-case-contacts and search-contacts are clearly differentiated by scope, and descriptions leave no ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with hyphens (list-*, get-*, create-*), which is consistent and predictable. However, authenticate, logout, and auth-status deviate from this pattern, breaking the uniformity slightly.

    Tool Count5/5

    With 15 tools, the server is well-scoped for its purpose. Each tool addresses a distinct need, and the count is within the ideal range, not feeling excessive or sparse.

    Completeness3/5

    The tool surface covers core read workflows for cases, contacts, documents, notes, tasks, and custom data, plus note and task creation. However, there are notable gaps: no update/delete for cases, notes, or tasks, no document content retrieval, and no contact creation/update. These omissions create dead ends for workflows requiring full CRUD.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources