BuildRocket for Claude

A BuildRocket account and a Claude account (claude.ai). Free Claude plans can add one custom connector; paid plans can add more.

1. In BuildRocket, open Your AI → Connect on the top bar and copy the address. It is https://www.buildrocket.ai/api/mcp — paste it exactly, with the www. The short address without www won’t connect.
2. In Claude, open Customize → Connectors → + Add → Add custom connector. Name it BuildRocket, paste the address and press Add.
3. Press Connect. Log in to BuildRocket if asked, read what Claude will and won’t be able to do, and press Let Claude in.

A connector added on claude.ai or the desktop app also appears in the Claude phone app.

The same address works in ChatGPT. Everything on this page holds for ChatGPT too: the same reads, the same suggestions waiting for your tick, and the same Disconnect.

1. In the ChatGPT desktop app, switch to the account you want it in, then open Settings → MCP servers and press + Add server.
2. Name it BuildRocket, choose Streamable HTTP, paste the address above into URL (with the www), and press Save.
3. Log in to BuildRocket if asked, and press Let ChatGPT in. Then ChatGPT asks you to install the BuildRocket plugin: install it.

Which ChatGPT plans can add a custom server, and whether a plan lets ChatGPT suggest as well as read, is set by OpenAI and changes from time to time. If ChatGPT only offers to read, the suggestions are switched off on its side, not BuildRocket’s.

The plugin is the same connector plus BuildRocket’s own instructions for Claude: six market checks (materials and supply, the market and insolvencies, tax and compliance, a monthly briefing, a quarterly costs review, and a regulatory watch), each saved to BuildRocket as a dated report with its sources.

1. Download the BuildRocket plugin (a zip file).
2. In Claude, open Customize → Plugins → Add → Upload plugin, and choose the zip.
3. Open the plugin’s Connectors tab, press Connect, and let Claude in as above.
4. Ask Claude for a BuildRocket market check, or in Claude Cowork type /buildrocket:market-check.

To run them on a schedule, use Your AI → Set-up → Market checks → Set up my research in BuildRocket: it makes a setup file for a Claude project, and on a paid Claude plan Claude makes each scheduled task for you to confirm. Each run lands in Your AI → Updates as a dated report. The searching runs on your own Claude plan; BuildRocket runs no AI for it.

• Read the business profile. Your business names, registration, contact details, licences and insurances, the country you work in and your currency.
• Read the set-up answers. The set-up answers saved on your profile, such as your brand voice and how each trade is set up.
• Read the standard inclusions. Your standard inclusions by category and tier, with products, brands, suppliers and your cost.
• Read the trades list. The trades you work with, with their default rates.
• Read the supplier list. Your suppliers, what they supply and how far ahead to order.
• Read the rates. Your labour and plant rates (what you charge out, before tax), your team’s charge-out and breakeven, your tax setting and on-costs.
• Read the Numbers Workshop. Your Numbers Workshop’s business numbers: set-up and on-costs, your team’s cost and charge-out, your overheads, your pricing targets, how the year is going, and your job planner. Your personal living costs are never in it.
• Read the window price list. Your window prices by supplier and line, per m² of window, and your one install rate per m² (your cost). A figure you have not filled in is never guessed.
• Read the styles. Your house styles (style packs): each one’s finishes, look words and the tier it picks first.
• Read the standard build sequence. Your standard build sequence: each stage in order, its trades, what has to be done before it starts, roughly how long it takes, and whether you have confirmed it.
• Read the jobs list. Your current jobs, each named by its job number and street name, with its stage. Never the client or the house number.
• Read the scope of a job. One job’s scope rows: room, quantity, rate, whether it is in the job, and which document each came from.
• Read the Costing table of a job. One job’s Costing table, the same figures you see, and every row or line with no price yet.
• Read the plan digest of a job. BuildRocket’s written read of one job’s plans, with client details taken out.
• Read the site notes of a job. The notes written up from one job’s site walk, and which ones you kept or corrected.
• Read the open questions on a job. One job’s unanswered questions, and where two documents say different things.
• Read the Viability overhead of a job. The overhead your Viability page suggests for one job, the days it is charged over, your own-days part and any split with your other jobs, and the figure you saved.
• Read the Schedule of a job. One job’s Schedule: each task, its trade, its dates and working days, and whether you or your crew are on it.
• Read the review notes of a job. One job’s Review page: who said each part was right and when, every review note and whether it is done, and who it was sent to.
• Read what is confirmed on a job. Which of one job’s packages you have confirmed on the scope page, and whether the scope is signed.
• Read the variations on a job. A job’s variations — draft, sent or signed, and what each is priced from — with each one’s own lines and total, so your AI can change the right line on a draft. A sent or signed variation is never changed by your AI.
• Read the client pack of a job. The client pack as you built it for the client — every package’s scope, the terms, the questions and their answers — and whether it is sent or signed, so your AI can check it before it goes out.
• Read the wet rooms of a job. Each wet room’s parts — the door and doorway waterstop, the shower’s set-out and how you step in, niches, shelves and hobs — and BuildRocket’s fixed list of what gets forgotten in a wet room (exhaust fan, a recessed cabinet’s reframing, the vanity splashback), so your AI asks only what you have not said.
• Read the back-costing of the jobs. Every job you have booked costs or hours to, with what it was estimated at against what it has actually cost so far, and the difference.
• Read the back-costing of a job. One job’s estimated against actual, group by group and line by line, with the invoices, receipts and hours behind each line, so your AI can tell you where a job ran over and check the figure against its source.
• Read the catalogue items. Your supplier price lists: each item with its price, its product link and the day that price was read, and whether the prices include GST.

• Suggest a supplier. A new supplier, or changes to one you already have, including its lead time. You see each box old → new before you accept, and nothing is ever cleared.
• Suggest a trade. A trade you work with.
• Draft a trade’s quote for a job. A quote a trade sent you by email or PDF, read by your AI: who, the quote number and date, the total before tax and how it splits across that job’s Costing rows. Accept files it on the job’s Quotes in. The split must add up to the total, or nothing is saved.
• Draft the tasks for one job’s Schedule. The tasks for one job, with their days and start dates, separate from your standard build sequence. You tick the ones you want, and Accept adds them to that job’s Schedule. Nothing the job already holds is changed or removed.
• Draft quantities for one job’s Costing rows. A first pass of quantities for one job, each with its working and source. You tick the ones you want, and a row that already holds a quantity shows old → new. Accept puts them on the Costing rows. A row you changed since is left as you have it.
• Suggest a business profile change. A value for one field of your business profile. Where the field already holds something, you see both side by side.
• Suggest a standard inclusion. A product for one category and tier, with your cost if Claude found one. It is added beside the inclusions you already have.
• Suggest a rate. A labour or plant hire rate: what you pay, before tax. Where you already have a rate for it, you see both before you choose.
• Save a market report. A structured report from one of your research checks: its findings, each with its sources and dates, and what it suggests you do. BuildRocket shows a finding grey when it has no source or date, or is too old. You keep it or dismiss it; it never changes a price, rate or quote.
• Save a market note. A dated note from the market check: what material prices, lead times and trade rates near you did, in words, with its sources. You keep it or dismiss it; it never changes a price or a rate.
• Suggest a style. One house style, researched: its finishes and a good / better / best product per category, with links. Accepting makes a style pack and adds the products you leave ticked to your inclusions.
• Suggest a standard build sequence. Every stage of how you build, in order, as one suggestion. Stages you already confirmed stay as they are; each new stage waits for your confirm.
• Send catalogue items. One batch of a supplier’s items, each with its price exactly as the page showed it and the day it was read. You see every item before you accept; accepting adds them to that supplier’s price list and keeps the version before.
• Send price changes. A re-check of one price list: each price that changed (old → new) and each line no longer on the site, or a note that nothing changed. Nothing changes until you accept.
• Suggest a set-up answer. Your Brand Profile, written after Claude runs BuildRocket’s brand interview with you. If you already have one, accepting adds this one under it, dated; nothing is replaced.

Suggestions land in Your AI → Updates, on the top bar, each marked with the AI that made it. Accept saves one the same way its own screen does, and Decline throws it away. A market note has Keep and Dismiss instead, because it saves nothing but itself.

This is off until you turn it on, for each connection: Your AI → Connect → Let my Claude change job tables. It is made for talking to your Claude while you drive or walk a site.

• Read a job change back. Before anything changes, BuildRocket writes the change out in words from the row as it is now — "Slab: 12 → 14.5 m², $816 → $986" — for Claude to read to you. This step changes nothing.
• Make a job change. Once you say yes, the change is made: a quantity, a unit, a rate (your cost, on that job only — never into your rates), in or out of the job, a note, a trade, a name, a Stage, a kind, a new row (in its area) or line, or a row moved to another package or area, or a line moved under another row — the row itself moves, nothing is copied. "Take it out" ticks it out. The one thing it can delete is an area with nothing in it, and Undo puts that back.
• Undo a job change. Puts the row back as it was — only a change that same Claude made. If you changed the row since, Claude puts nothing back: you do that with Undo on the screen, which asks you first.

BuildRocket cannot hear you say yes — it only sees Claude ask. So once it is on, Claude can change a job without asking you again, and these are the guardrails: only the account owner can turn it on; the read-back is written by BuildRocket, never by Claude; a read-back lasts 10 minutes (a list, 60) and works once; a row changed since the read-back is not touched; one job takes at most 500 voice changes in a day; every change is recorded before it is made, and one that cannot be recorded is not made; and every change is listed under Changed by your AI on the scope page and the Costing tab, with the words given for it and Undo, and the row is marked by your AI. A quote you have locked stays locked.

• See your clients’ names, phone numbers, emails or house numbers. They are never sent; a job is named by its street.
• Change anything without your tick — apart from job tables, if you switch that on.
• Send an email, use the client portal, sign a document, take a payment, or delete anything but an empty area.

In BuildRocket, open Your AI → Connect on the top bar and press Disconnect Claude (or Disconnect ChatGPT). Claude’s key stops working on its next call. You can also remove the connector in Claude.

What Claude reads goes to your own Claude account, under the terms of that account. BuildRocket keeps a record of every suggestion Claude makes and every one you accept or decline. To keep things steady, each account is limited to 60 calls a minute and 200 suggestions a day.

Read the privacy policy, or get help.