Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Buildertrend to Claude Code

Have Claude update schedule tasks and create change orders in Buildertrend. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Buildertrend to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Buildertrend, you add a Buildertrend MCP server: a small hosted service that exposes Buildertrend's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Buildertrend account. No API keys pasted into config files.

claude mcp add --transport http buildertrend https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Buildertrend once connected?

Full read-write Buildertrend access lets Claude add or shift a schedule task, assign it to a subcontractor, and draft a change order or selection once you approve. The job coordination that used to mean re-keying between the field and the office happens inside the job where the work already lives.

  • Create or reschedule a schedule task and assign it to a subcontractor
  • Update a schedule task and its dates as the job moves
  • Draft a change order line for your review before it goes to the client
  • Create or update a selection for a client to approve
  • Read jobs, schedules, and daily logs to summarize project status
  • Pull task lists and to-dos out of a job for a field briefing

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Buildertrend access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Buildertrend API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Buildertrend changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Buildertrend connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Buildertrend connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Buildertrend account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Buildertrend's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Buildertrend?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Buildertrend account it signs in with. Revoking access is one click in Buildertrend.

More on the Buildertrend connector

Buildertrend connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us