Builddar MCP connector and API Builddar in your assistant, and in your tools.
Ask Claude or ChatGPT about your developments, have changes made after a preview, or connect your own tools through the API.
Example on fictional data.
An MCP connector is an address you add to your assistant, Claude or ChatGPT, so that it reads Builddar with your rights: developments, snags, site meeting reports, handovers and aftercare. It can also prepare a change, which you confirm after a preview. For your own tools, Builddar also offers an API with keys.
What is an MCP connector?
An MCP connector is an address you add to your assistant. It uses it to read Builddar for you, with your rights, like a colleague who has opened your account next to you.
You stay in your tool.
You ask the assistant your team already uses. It fetches the answer in Builddar.
You keep your rights.
The assistant sees what you see in Builddar, no more, no less.
You confirm.
For any change, the assistant shows a preview. Nothing changes before you confirm.
What you can ask Builddar.
Ask your questions as you would ask a colleague. Here are the ones a technical, programme or aftercare manager asks.
Find your developments
“Which developments can I query?”
Compare your developmentsFour views: works, acceptance, handover, aftercare, ranked by delay.
“Which developments are doing badly, in works and in aftercare?”
Get the status of a development
“Where does Quai Ouest stand?”
Compare companies
“How do the plumbing companies compare across all my developments?”
Search snags
“Which plumbing snags are late at Les Tilleuls?”
Open a snagWith its last 20 history events.
“What happened on snag R-047?”
Follow claims
“Where do the aftercare claims stand?”
See the facts behind a delayDelays by company, absences at the last site meetings, bad-weather days.
“What explains the delay at Les Tilleuls?”
Know what has moved
“What has moved since Monday?”
The figures are those of Overview, with its definitions: see the Overview page. Would you rather ask inside Builddar itself? Dar, the Builddar AI agent, does the same.
Have changes made, after a preview.
The assistant prepares the change, Builddar shows it, you confirm. In that order, every time.
Analyse
What is late, what needs attention.
Act
Push back due dates in bulk.
Correct
Fix data: company, status, due date.
Configure
Adjust a development, for example its validation circuit.
Example on fictional data.
A change always goes through the request, the preview of what will change, then your confirmation. You can cancel at the preview step.
Connect it in three steps.
Example on fictional data.
Copy the address.
In your Builddar profile, “Builddar address for your AI”: click Copy.
Add it to your assistant.
In Claude, add a custom connector and paste the address. In ChatGPT, add a custom MCP server with this address.
Sign in.
Builddar asks you to sign in and choose the organisation. You allow, then you ask your first question.
On Claude Team or Enterprise, an owner of the organisation adds the connector first, then each person clicks “Connect”. A Builddar administrator must have opened your developments to the assistant.
Your rights, your control.
A connected assistant does not use a back door: it goes through your rights, and you can disconnect it at any time.
Your rights, no more
A connection stands for one person and one organisation. The assistant sees what that person sees in Builddar.
Developments opened by an administrator
An administrator chooses, development by development, which ones the assistant may read.
Never guests
Guests (design team, companies, buyers) cannot connect an assistant.
Disconnected at any time
Disconnect an application in the settings: access stops at its next request.
Every call is logged
Builddar keeps who asked what, with which tool, from which application, and the result. Not the text of the conversation.
Limits
60 requests per minute and per person; a query that takes longer than 5 seconds is stopped.
A standard connection
OAuth 2.1 with PKCE: you allow or deny on screen, without giving the assistant a password.
The API, for your own tools.
Your team or your integrator connects Builddar to your CRM, your customer service or your ERP, with access keys. Where the connector answers a person, the API serves your systems.
{
"results": [
{
"number": 47,
"title": "Cracked tile joint, bathroom",
"status": { "name": "Closed" },
"zone": { "name": "B12" },
"company": { "name": "Carrelage Vidal" }
}
]
}
Keys per organisation
Each key belongs to one organisation, read-only or read and write.
Your own codes
Designate a project, a snag or a claim by the code you already use (“@code”).
CSV export
Export up to 50,000 lines.
Stable version 1
Version 1 only adds fields. An incompatible change goes to version 2.
Clear limits
600 requests per minute and per key.
Writes are marked
A change made through the API is marked as such.
What the API covers: projects, zones, companies, members, homes (with import), snags (with photos), claims, phases, trades, cases and interventions.
CRM (Salesforce, HubSpot): sold homes and their buyers arrive in Builddar before handover.
Customer service (Zendesk): a request opened on your side becomes an aftercare claim in Builddar.
ERP and business intelligence: snags, closings and aftercare cases read back by your tool since the last synchronisation.
The API documentation can be read without a key. Request API access
Frequently asked questions
Which assistants can connect to Builddar?
Claude and ChatGPT, with the same address.
Do I need a particular Claude or ChatGPT subscription?
It depends on your subscription: not all of them let you add a custom connector. On Claude Team or Enterprise, an owner of the organisation adds it first, then everyone clicks “Connect”.
Can the assistant change everything?
No. It acts with your rights, on the developments an administrator has opened, and only after a preview that you confirm. It can push back due dates in bulk, correct data or configure a development.
Does Builddar keep my conversations with the assistant?
Builddar does not record the text of the conversation, which stays in your assistant. It logs every call: who, which tool, from which application, which result.
How do I cut off access?
In Settings, “AI assistant”, “Connected apps”, click “Disconnect”: access stops at the next request. An administrator can also close a development to the assistant.
Is the API open to my organisation?
Builddar switches it on per organisation. Ask for it during the demonstration: you then receive your keys.
Are the connector and the API paid? Prices are on the Pricing page.
See Builddar on your developments.
Start with a pilot development, free, until its handover and with no commitment.
Thanks for your message.
We'll call you back within one business day.
Your details are used only to answer your request.