Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

Related Servers

Alternatives to Bookipi 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
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT, Claude and other AI agents to work with clients, draft quotes, manage invoices and unpaid balances in a signed-in Batappli en ligne account via Cotlet.dev, with approval required for sharing, payments, conversions and reminders.
      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 has a clearly distinct role: guide for instructions, status for readiness checks, open/close for session lifecycle, and read/click/type for page interaction. There is no meaningful overlap between tools, so an agent can select the right one from the name and description alone.

    Naming Consistency5/5

    All tools use the consistent `bookipi_` prefix followed by a short, lowercase verb or noun (`guide`, `status`, `open`, `read`, `click`, `type`, `close`). The pattern is predictable and easy to scan.

    Tool Count5/5

    Seven tools is a well-scoped set for a browser-automation workflow: one guide, one status check, session open/close, and the essential read/click/type interaction primitives. No tool appears redundant or missing for the stated purpose.

    Completeness4/5

    The core lifecycle and interaction loop is covered: open a session, read the page, click and type, then close to stop credits. Minor gaps exist for common browser automation needs such as waiting for page loads, scrolling, or taking screenshots, but the main invoice/customer/proposal workflows are supported.