Buildertrend MCP Server

Schedules, daily logs, change orders and selections for builders.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/buildertrend'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Buildertrend API and MCP server: Let your AI agent keep your Buildertrend jobs current.

Buildertrend has no official MCP server. A developer portal that went up in October 2026 offers an Open API that reads jobs, job users and tasks and creates a job from a template, and nothing else (checked 27 Oct 2026). Cotlet runs 12 Buildertrend tools hosted, over MCP for agents and REST for scripts.

Read Buildertrend jobs, schedules and daily logs through MCP or REST. Connect your company account to an agent or a construction reporting workflow.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Buildertrend
Page: https://cotlet.dev/integrations/buildertrend-api-mcp-server

What can you automate in Buildertrend?

Write daily logs from your site notes
Read the schedule across every job
Move a slipped item and notify the sub
Draft change orders with cost codes
Chase selections clients have not made
Hand out tasks with a checklist

Does Buildertrend have an MCP server or an API?

The Open API lists 8 operations, keys are approved at once and calls are capped at 20 a minute. On 30 Sep 2026 the developer subdomain did not resolve yet, and we found no announcement.
It has no schedule, daily log, change order or selection endpoint and cannot create a task. Every other connection goes through the Buildertrend Marketplace, which Buildertrend builds with named partners such as QuickBooks and Sage Intacct.
There is no Buildertrend app on Zapier (zapier.com/apps/buildertrend answers 404) and no native Make or n8n node.

What you need	Open API	GitHub server	Cotlet
List jobs and tasks	Yes	Some	Yes
Read and move schedule items	No endpoint	Some	Yes, after your OK
Write daily logs	No endpoint	Some	Yes
Change orders and selections	No endpoint	Some	Yes
Runs with your computer off	Yes	Mostly no	Yes, hosted
Allowed by Buildertrend	Yes, official	Uses the web app	Uses the web app

Checked 27 Oct 2026. Sources: Buildertrend Developers (Open API portal), Buildertrend Marketplace (Buildertrend help), Daily Logs Overview (Buildertrend help), Buildertrend API, Carly blog (30 Sep 2026)

How does Cotlet connect to Buildertrend?

Sign in to Buildertrend. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your Buildertrend password, and a log shared with the client, a schedule move or a change order waits for your OK.

Connect Buildertrend to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Step by step with screenshots for ChatGPT, Claude, Grok and other agents: How to connect Buildertrend to ChatGPT, Claude and any AI agent.

Enable Buildertrend for agents. Create a Cotlet account, sign in to Buildertrend in its Cloud Browser with your own company user, and press Enable for agents.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as a custom MCP server or connector.
Approve the connection. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts use an API key from the console instead.

Buildertrend shares the address https://cotlet.dev/mcp/v1 with every other app you enable. A user who cannot open a job or edit its schedule in Buildertrend cannot do it through the tools either. Turned Buildertrend on after connecting? Refresh the connector so the agent sees the new tools.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-buildertrend \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-buildertrend": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-buildertrend]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: buildertrend_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: buildertrend_write

How to use the Buildertrend REST API

Create your Cotlet API key

Create a Cotlet API key with access to Buildertrend and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Sign in to Buildertrend in its Cotlet Cloud Browser and enable the app for agents. Your company role determines which jobs and records you can access.

Make your first Buildertrend API request

cURL:

curl "https://cotlet.dev/api/v1/buildertrend/jobs?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read jobs within a selected reporting range

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "buildertrend",
  "tool": "list_jobs",
  "result": {
    "jobs": [
      {
        "job_id": "4815162",
        "name": "Maple Street Addition",
        "status": "open",
        "address": "214 Maple St, Austin, TX",
        "project_manager": "Dana Ortiz",
        "start_date": "2026-08-17"
      }
    ]
  }
}

Read result.jobs. Job lists default to 50 records, with a maximum of 100 and no cursor, page or offset input.

Open jobs are the default; request the appropriate status for closed or presale jobs. Use narrower selections rather than assuming a complete export beyond the cap.

Daily logs default to 20 records, with a maximum of 100 and no continuation. Narrow by job and date; other users' private logs are omitted.

Buildertrend workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Read jobs and schedules into a project timeline and dependency briefing without changing dates.
Make	HTTP > Make a request	Read permitted daily logs and open tasks into a site-update and deadline digest.
Python or Node.js	REST API	Read change orders and pending selections into a client-decision review without approving or releasing anything.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Buildertrend; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Buildertrend API endpoints and MCP tools

Jobs and schedule

Reads cover one job or all open jobs. A move notifies assignees only when the job schedule is Online, and linked items follow by the job's predecessor rules.

List jobs (list_jobs, read): Jobs in your company with status, address, project manager and dates.
Get schedule (get_schedule, read): Schedule items with start and end dates, assignees, predecessors and status.
Update schedule item (update_schedule_item, write, asks first): Move or resize a schedule item and optionally notify its assignees.

Daily logs

New logs are internal unless you name subs or the client. Other users' private logs never come back.

List daily logs (list_daily_logs, read): Daily logs, newest first, with notes, author and who they are shared with.
Create daily log (create_daily_log, write, asks first): New daily log with notes for a job. Internal unless you share it.

Change orders and selections

A change order is saved unreleased, so the client sees nothing until the release call. Change orders need Advanced and the Selections portal needs Complete.

List change orders (list_change_orders, read): Change orders with title, amount, line items and approval status.
Create change order (create_change_order, write, asks first): New change order with line items, saved unreleased. The client sees nothing yet.
Release change order (release_change_order, write, asks first): Send a change order to the client to approve or decline in their portal.
List selections (list_selections, read): Selections with options, allowance and approval status.
Approve selection choice (approve_selection_choice, write, asks first): Approve a choice on the client's behalf, with a comment.

Tasks

Tasks for one job or all of them, with checklists. A task with assignees reaches them.

List tasks (list_tasks, read): Tasks with assignees, deadline, checklist and status.
Create task (create_task, write, asks first): New task on a job with assignees, deadline and checklist.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/buildertrend-api-mcp-server#tools

Who can see my Buildertrend session, and how do I revoke it?

What we store. The signed-in Buildertrend browser profile, AES-256-GCM, in Finland. No password.
What your agent gets. The 12 Buildertrend tools. Never the cookie or the login.
What the session sees. The jobs your user role opens: schedules, logs, change order amounts, client selections.
What no tool touches. Bills, payments, invoices, purchase orders, users and company settings.
If Buildertrend asks to verify. The code goes to you and you type it. We never sign in for you.
How to cut access. Disable for agents, reset the browser or delete the API key. The next call fails.

cotlet.dev gets A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.

Is it against Buildertrend's terms? Account safety

Customer shall not ... use any software, devices, scripts, crawlers, robots, or other automated processes to copy, scrape, or systematically acquire any content contained within the Solution without the express written consent of Buildertrend.

Buildertrend Terms and Conditions Agreement, 2.3(i), updated 17 Feb 2026

The same clause covers every unofficial route, GitHub servers and hosted tools that sign in as you included. Section 2.3(g) also says one user login is for one person, so connect the login of the person whose work the agent does. For jobs and tasks, the Open API is the route Buildertrend offers. We found no public case of an account closed for automation (checked 27 Oct 2026).

How we keep your account looking like you:

Your own Buildertrend user, signed in by you
One Cloud Browser with its own IP and cookies, not a new device on each call
Shared logs, schedule moves and change orders wait for your OK
Sign-in and 2FA stay with you; we never bypass MFA
If Buildertrend objects, we pause the Buildertrend tools for everyone within 24 h

Write logs as the day goes, not 60 jobs of backfill in one burst. Bulk copying is what 2.3(i) names.

What happens when Buildertrend changes?

12 h between tests of the Buildertrend tools
24 h between tests of writes a client or sub would see
$0 for a call to a tool paused for repair

Buildertrend screens differ by account and date: accounts made before 17 Dec 2025 still run the legacy Selections, and change order tax works one way only on jobs created from 14 Jan 2026. When a screen moves, we fix the tool and your prompts keep working. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Splits the notes. Each street or client name matched to one job with list_jobs.
Checks for today's log. list_daily_logs finds a log already written, so no duplicate.
Waits for your OK. The draft log shows up in your Cotlet console.
Reports back. Logs saved, who sees them, and notes it could not place.

Action	Undo
Create a daily log	Edit or delete it; a client who opened it has read it
Move a schedule item	Move it back; notified subs already got the message
Create a change order	Delete the draft; the client never saw it
Release a change order	Unrelease it before the client signs
Approve a selection	Not by a tool; the allowance and budget already moved
Create a task	Delete the task in Buildertrend

All 6 write tools ask first: daily logs, tasks, schedule moves, change orders, their release and selection approvals. The 6 reads run at once. Turn the wait off per tool for a scheduled run, such as internal logs at 5 pm.

Released change orders can carry an invoice: with Invoice upon client approval on, Buildertrend bills the client the moment they approve.

MCP call:

{
  "name": "create_daily_log",
  "arguments": {
    "job_id": "4815162",
    "date": "2026-10-09",
    "title": "Framing, second floor",
    "notes": "Second floor walls framed and sheathed. Window rough openings checked against plans.",
    "share_with": [
      "internal"
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/buildertrend/jobs/4815162/daily-logs \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-09","title":"Framing, second floor","notes":"Second floor walls framed and sheathed. Window rough openings checked against plans.","share_with":["internal"]}'

Tool output:

{
  "daily_log_id": "23094417",
  "job_id": "4815162",
  "date": "2026-10-09",
  "title": "Framing, second floor",
  "shared_with": [
    "internal"
  ],
  "url": "https://buildertrend.net/app/DailyLogs/23094417"
}

Scripts reach the same tools over REST at /api/v1/buildertrend with the same key and price. A call your Buildertrend role is not allowed to make fails and costs nothing. Each row in the tools table shows its REST path.

How much does the Buildertrend MCP server cost?

About $20 a month for a remodeler with about 8 open jobs, 3,400 credits. Your Buildertrend plan is billed as before.

Job	Calls	Credits
Daily logs from site notes, 3 jobs	5 × 22	1,100
Two-week look-ahead, all jobs	2 × 4	80
Move a slipped item, notify the sub	3 × 8	240
Draft and send a change order	4 × 6	240
Pending selections by client	1 × 4	40
Task from a site call	2 × 10	200
Cloud Browser, 30 days		1,500
Total		3,400

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
One-time packs, valid 12 months, no subscription

Sales quotes cite builders with 5 to 10 active projects; the month above is our example for 8. Buildertrend does not publish its prices; third-party lists put the plans at $339, $499 and $829 a month billed yearly. Dollars at the $29 pack rate.

Buildertrend MCP server: Open API, GitHub or hosted

Option	What it does	Where it stops
Buildertrend Open API	Official: list jobs, job users and tasks, create a job from a template. Keys approved at once.	No MCP server, no schedule, logs, change orders or selections; 20 calls a minute.
Clickr	Hosted MCP over data synced from your Buildertrend login: jobs, schedules, tasks, leads.	Read-only, about 10 minutes behind; free 3 months, then $80 a month.
Carly	Workflows from Buildertrend email notifications and your accounting app, no Buildertrend login.	Sees only what the emails carry, cannot write; AI agents from $35 a month.
BuildCal/buildertrend-gateway	Community MCP and HTTP gateway on Buildertrend's internal web calls, MIT, last commit 26 Oct 2026.	Runs on your computer on a copied session; 0 stars.
jdcantin/buildertrend-mcp	One company's server: 15 tools through Browserbase, including report export.	Keeps your Buildertrend email and password in env; no license, last commit 26 Apr 2026.
elevateson/buildertrend-openclaw	OpenClaw skill, 43 playbooks that drive your own Chrome tab.	Your Chrome has to stay open; last commit 2 Mar 2026.

If a job list or a task feed in your own system is all you need, the Open API is free and sanctioned. Cotlet is for the work it leaves out: logs, schedule moves, change orders and selections, run by an agent while your computer is off.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Behind Cotlet is Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273), building software since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the Buildertrend tools.

Buildertrend API and MCP: questions

Can I use the Buildertrend API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Sign up free at https://cotlet.dev, open Buildertrend under Integrations in the console and sign in to Buildertrend in its Cloud Browser. The trial begins when you sign up, with no card asked.

How do I connect Buildertrend to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Buildertrend once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Buildertrend account through Cotlet, in their phone apps too.

What can ChatGPT do in Buildertrend?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Buildertrend: write daily logs from site notes; check the schedule across all jobs; reschedule a slipped item and notify the sub. You ask in plain words, and anything that reaches other people waits for your OK first.

Is there an official ChatGPT or Claude app for Buildertrend?

No. Buildertrend has no ChatGPT or Claude connector of its own (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

Can ChatGPT write a daily log in Buildertrend?

Yes, with Cotlet. Paste your site notes and ChatGPT writes the daily log on the right job in your Buildertrend account. Saving it waits for your OK by default, which you can switch off per tool.

Can ChatGPT update the schedule in Buildertrend?

Yes, with Cotlet. ChatGPT moves a slipped schedule item to new dates, notifies the assigned subs if you ask and creates tasks for the crew. Each change waits for your OK by default.

Does my agent need an admin role?

It acts with your own Buildertrend user, so it sees and does what your role allows. If your user cannot open a job or edit its schedule in Buildertrend, the call fails with a permission error.

Can I use the Buildertrend Open API and Cotlet together?

Yes. Sync jobs and tasks into your own system with the Open API, and give the same agent Cotlet for daily logs, the schedule, change orders and selections.

Does Buildertrend have webhooks?

Not for customers (checked 27 Oct 2026). The Open API has no webhook operation, and Marketplace partners sync on their own terms. To react to new logs or approvals, run your agent on a schedule.

Does it work on the Essential plan?

The tools do what your plan and role do in Buildertrend. Daily logs, the schedule and tasks are on every plan; change orders need Advanced and the Selections portal needs Complete, per third-party plan lists.

Is the MCP server different from the REST API?

Only the way in. Both carry the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and cron jobs use REST.

Is Cotlet affiliated with Buildertrend?

No. Cotlet is independent and not affiliated with Buildertrend Solutions, Inc.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.