Skip to main content
Glama
Billdr MCP Server

Billdr MCP Server

Related Servers

Alternatives to Billdr MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with estimates, quotes, job schedules, variations, and progress claims in a user's signed-in Buildxact account, with write actions requiring approval by default.
      Elastic 2.0
    • 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
      Connects ChatGPT, Claude, Codex and Claude Code through Cotlet.dev to a signed-in construction management account, enabling work with projects, estimates, bids, change orders, daily logs, RFIs, invoices and related workflows. It exposes 31 read and write capabilities, most write actions requiring confirmation before anything is sent or changed.
      7
      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
      A
      quality
      B
      maintenance
      Connects a signed-in Bolster contractor account to ChatGPT, Claude, Codex, and Claude Code through Cotlet.dev so users can manage estimates, proposals, schedules, job budgets, bid requests, and customer payment requests, with write actions reviewed before approval.
      7
      Elastic 2.0

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct step in the browser workflow: guidance, readiness check, session opening, reading, clicking, typing, and closing. There is no meaningful overlap between tools, and the descriptions make the intended sequence clear.

    Naming Consistency5/5

    All tools use a consistent billdr_ prefix followed by a short, predictable verb or noun. The pattern is uniform across the entire set.

    Tool Count5/5

    Seven tools is well-scoped for a browser automation server focused on a single application. Each tool corresponds to a necessary lifecycle action without bloat.

    Completeness4/5

    The core browser interaction lifecycle is covered: open, read, click, type, and close, plus onboarding and status helpers. Minor gaps exist around scrolling, waiting for page load, or selecting dropdown values, though these may be workable through links and clicks.