← Back to all docs
buildertrend

Buildertrend MCP Server

The Buildertrend MCP server lets AI agents read and write project, schedule, financial, and field data in Buildertrend. Connect Buildertrend to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Buildertrend doesn't ship an MCP server.

By Alex KlarfeldMay 12, 2026
Buildertrend MCP Server

What is the Buildertrend MCP server?

The Buildertrend MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write project, schedule, financial, and field data in Buildertrend through a standard protocol.

In short: Buildertrend is a cloud platform for residential construction management: project execution, customer communication, job financials, and field operations, with a client portal and a subcontractor portal.

Buildertrend doesn't ship an official MCP server, and Buildertrend's data lives behind role-aware portals (builders, clients, and trade partners each see a different slice), with several features (selections, warranty, messaging) being portal-first. Supergood builds and maintains the connector by reverse-engineering Buildertrend's authenticated web and portal flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with Buildertrend via MCP

Once connected, an agent can:

  • List projects with metadata, addresses, job numbers, phases, and status.
  • Pull schedules and tasks: dates, dependencies, assignments.
  • Retrieve selections (categories, options, pricing, approvals).
  • Create and update change orders with line items, taxes, and signatures.
  • Pull budgets and cost codes for job costing and variance.
  • Get purchase orders and vendor invoices.
  • Retrieve daily logs (notes, weather, labor, photos) and time entries.

How to connect Buildertrend to Claude, ChatGPT & Cursor

Connecting works like any other MCP server. The short version:

  • Claude (Desktop or claude.ai): add the Buildertrend MCP server under Settings → Connectors (or your MCP config), authorize the Buildertrend account Supergood provisions, and the tools show up in any chat, including agent runs.
  • ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the Buildertrend tools in conversations and in agent mode.
  • Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.

Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.

How Supergood builds the Buildertrend MCP server

Supergood doesn't wait for Buildertrend to ship an API. We reverse-engineer the authenticated web and portal flows behind Buildertrend, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.

  • Auth and MFA, handled. Supergood provisions a dedicated Buildertrend account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
  • Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape Buildertrend's front-end happens to return.
  • Monitored and adapted. When Buildertrend changes its web and portal UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • Role-aware access. Builders, clients, and trade partners see different data and approval states in Buildertrend; Supergood authenticates with the right role so the agent gets the slice it needs.

Getting Started

  • Schedule Integration Assessment

Book a 30-minute call to confirm which Buildertrend modules and workflows you need and how authentication should work.

  • Supergood Builds and Validates Your MCP Server

We deliver a hardened Buildertrend connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Buildertrend changes.

Use Cases

Project status agent

- Answer "where is the Smith remodel" with live schedule and task state - Surface late tasks and blocked dependencies - Draft the weekly client update from daily logs

Change-order handling

- Build the change order from the requested scope - Apply taxes and route for signature - Track approval and update the budget

Job costing

- Pull budget vs. actual by cost code - Flag overruns and unbilled POs - Reconcile vendor invoices against POs

Field operations

- Pull daily logs and photos for a date or project - Surface time entries for payroll review - Cross-check selections that still need a client decision

Technical Specifications

MCP transport

Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.

Authentication

Supergood provisions a dedicated Buildertrend account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.

Supported clients

Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.

Tools exposed

8 tools covering the workflows listed above; the set is scoped to the modules you license.

Data freshness

Near real-time reads and writes against Buildertrend's live web app.

Rate limits

Tuned to Buildertrend's tolerances; Supergood paces requests to avoid tripping security throttles.

Latency

Sub-second for most reads under normal load; writes reflect the underlying platform timing.

Session management

Automatic re-auth plus cookie/token rotation, with health checks.

Security

Encrypted transport, scoped access, and audit logging; respects Buildertrend role-based permissions.

Webhooks

Optional asynchronous delivery for long-running operations; polling otherwise.

Reliability

Retry logic, backoff, and idempotency keys to avoid duplicates.

Adaptation

Continuous monitoring for Buildertrend web and portal surfaces changes, with rapid connector updates.

Frequently asked questions

No. Buildertrend doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Buildertrend's authenticated flows and exposing them as MCP tools, plus the underlying REST API.

All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.

Supergood provisions a dedicated Buildertrend account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.

Yes. Reads and writes hit Buildertrend's live system, not a nightly export. Buildertrend's data lives behind role-aware portals (builders, clients, and trade partners each see a different slice), and several features (selections, warranty, messaging) are portal-first.

Both. The MCP tools are a layer on top of a normalized REST API for Buildertrend; you can call either, from an agent or from your own code.

Ready to get a real API?