Skip to main content
Glama

Related Servers

Alternatives to BuildBook MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with a signed-in Buildern contractor account through Cotlet.dev, including estimates, schedules, budgets, bills, client invoices, project to-dos, and site diaries, with review before write operations.
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude, and other AI agents to draft estimates, schedule jobs, assign crew members, and review receivables in a user's signed-in business account, requiring approval before actions reach other people.
      7
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI agents to a signed-in contractor account through Cotlet.dev so they can work with estimates, leads, change orders, and job costs. Supports drafting line items, tracking estimate views, reading margins and recorded costs, and reviewing changes before writes are sent.
      Elastic 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of a browser-automation workflow: guide (instructions), status (account/connection check), open (launch session), read (inspect page), click, type, and close. There is no meaningful overlap between any two tools, and the descriptions reinforce clear boundaries.

    Naming Consistency5/5

    All tools share a uniform buildbook_ prefix followed by a single lowercase verb or noun (guide, status, open, read, click, type, close). The pattern is predictable and readable throughout.

    Tool Count5/5

    Seven tools is well-scoped for a browser-automation server: a guide, a health check, and the five core session primitives (open/read/click/type/close). Nothing feels redundant or missing at the count level.

    Completeness4/5

    The surface covers the full basic browser lifecycle: open a page, read its contents, click, type, and close the session. Minor gaps exist—no explicit navigation to an arbitrary URL, scrolling, or dropdown/select handling—but agents can likely work around these via click/type and the guide.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues