BuildBook MCP server
Related Servers
Alternatives to BuildBook MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to operate a signed-in construction management account, creating estimates, updating projects, sending invoices, and querying budget, project, and invoice data through natural language.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables AI agents to work inside a user's signed-in Buildertrend account, reading job schedules, identifying late tasks, writing daily logs, and producing progress updates without requiring a Buildertrend API key.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables 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.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceConnects 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
- AlicenseAqualityBmaintenanceEnables AI agents to create estimates, schedule jobs, send invoices, and query open estimates and unpaid invoices from a user's signed-in contractor account using natural language.7Elastic 2.0
TDQS
Scored across 7 tools
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.
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.
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.
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.