Skip to main content
Glama
chad-hohn-radai

spotdraft-mcp

Related Servers

Alternatives to spotdraft-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A single-auth MCP server that gives Claude unified access to deal intelligence from Salesforce, Slack, and Gong, enabling natural-language queries about deal status, activity, and pipeline health.
      -
    • 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
    • A
      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
      Academic Free v1.1

    TDQS

    A4.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with detailed descriptions that minimize ambiguity. For example, get_contract_content and get_contract_download_link are explicitly differentiated by output format and use case.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern with underscores (e.g., list_contracts, get_contract_content, run_analytics_query). No mixing of conventions, making it easy for an agent to predict naming.

    Tool Count4/5

    With 19 tools, the server is slightly over the typical well-scoped range of 3-15, but each tool serves a distinct read operation for a comprehensive API. The count is justified by the breadth of the domain.

    Completeness5/5

    The tool surface covers a wide range of read operations including contracts, counterparties, templates, analytics, and API catalog search. There are no obvious gaps for the stated read-only scope, and the inclusion of search_actions allows agents to discover additional endpoints.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues