Skip to main content
Glama
Sign In
LexPact MCP Server

LexPact MCP Server

by Idadabhai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to LexPact MCP Server

No user-submitted related servers found.

    Related Servers

    • Common Paper MCP server

      Common Paper MCP serverofficial

      CommonPaper
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to query, create, and manage contracts in plain English from any MCP client, including drafting and sending agreements, tracking renewals and signers, and building templates. It supports OAuth-authenticated workflows with safe defaults such as creating drafts and confirming before sending or changing live agreements.
      MIT

    • cfr-compliance-mcp

      vvXranjan
      F
      license
      A
      quality
      B
      maintenance
      A production-quality MCP server that exposes the official eCFR API as structured tools for AI-driven contract compliance, enabling retrieval of relevant Code of Federal Regulations by clauses extracted from contracts.
      8
      -

    • APISign MCP Server

      wes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create and manage contract templates, draft agreements by filling in template variables and signers, send documents out for legally binding e-signature, and track signer status as signatures come in. It runs as a hosted remote server, so there is nothing to install or self-host.
      MIT

    • Precedent

      insha-parveen
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search and retrieve contract intelligence over public contract data, with agent skills for precedent lookup, negotiation checks, and risk flagging, all with verification and citations.
      -
    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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the lifecycle: discovery (list_contract_templates), creation (generate_contract), and retrieval (get_contract). The descriptions explicitly sequence them ('call this first', 'retrieve by id'), leaving no plausible misselection.

    Naming Consistency5/5

    All three tools follow a strict verb_noun snake_case pattern (list_/generate_/get_ + contract object). Terminology is stable across names and descriptions.

    Tool Count4/5

    Three tools is on the lean side, but each covers a necessary step and the server's scope is deliberately narrow (contract generation only). No tool feels redundant or padded.

    Completeness3/5

    The create-and-poll workflow is covered, but there is no way to list existing contracts, re-fetch a PDF URL after the initial generate response, or update/cancel a contract. Agents that lose the generate response or need an inventory are left with dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources