Text it from the field, or let your AI do it
Your AI does the paperwork. Brikt knows the job.
An AI assistant is only as good as what it can reach. Connect one to Brikt and it works with your real catalog, your estimates and your crew board — not a blank chat window and a guess.
- search_catalog“holland 60mm”
- upsert_jobDelgado · back patio
- create_estimateEST · Delgado back patio
- add_areaBack patio · 280 sf · 68 LF
- add_item_to_areapavers, border, base, bedding sand, fabric, edge restraint, polymeric sand
Draft estimate is in Brikt with seven lines sized from the area. The border colour had two matches in the catalog — I picked charcoal; check it before you send the proposal.
Work gets in however it happens
Four ways in. One record behind all of them.
01
The web app
Estimating, ordering, the Board and receiving — in the browser on a desk or on a phone at the site. Nothing to install.
02
Crew chat
Crew leads text updates and photos to a job’s WhatsApp line or its Slack channel, and Brikt files them to that job.
03
Your AI assistant
Claude and other assistants that speak MCP can read and build in Brikt with a key you issue — estimates, areas, catalog, the Board.
04
The API
Your own tools can read your projects, estimates and catalog, and import customers, projects and items.
What your assistant can do
Real tools, not a chatbot bolted on.
MCP is the open standard assistants like Claude use to work inside other software. Brikt’s MCP server gives yours 20 tools. Keys are read-only unless you create one that can write, and you can revoke any key from Settings.
- Only your company’s data, through a key you control
- Read-only by default; writing needs a read-and-write key
- An estimate your assistant starts is a draft until you send it
| Tool | Does | Key |
|---|---|---|
| Estimating | ||
| create_estimate | Start an estimate | Write |
| add_area | Add an area to an estimate | Write |
| add_item_to_area | Add a catalog product to an area, sized from it | Write |
| Estimating | ||
| list_estimates | List estimates | Read |
| get_estimate | Read an estimate | Read |
| search_catalog | Search the product catalog | Read |
| get_catalog_item | Read a catalog product | Read |
| list_company_items | List your company’s own items | Read |
| Jobs and field | ||
| list_projects | List projects | Read |
| get_project | Read a project | Read |
| get_board | Read the crew board | Read |
| list_daily_logs | Read daily logs | Read |
| list_field_events | Read field updates | Read |
| get_whatsapp_invite | Refresh a job’s WhatsApp invite link | Read |
| list_customers | List customers | Read |
| Jobs and imports | ||
| upsert_job | Create or update a job | Write |
| create_job_feed | Open a job’s WhatsApp or Slack feed | Write |
| upsert_projects | Import projects | Write |
| upsert_customers | Import customers | Write |
| upsert_company_items | Import your company items | Write |
Moving off spreadsheets or another system
Hand your assistant the old spreadsheet.
Export your customers, projects and item lists from wherever they live now. Give the files to an assistant connected with a read-and-write key and ask it to import them. It can preview with a dry run first, records are matched by their id in your old system so re-running an import doesn’t pile up copies, and each item comes back matched to the catalog or flagged for you to review.
Prefer to do it yourself? The API takes the same imports from your own scripts. On Commercial, we’ll walk through setup with you on a call.
Step 1
Create a key
In Brikt, open Settings → Integrations → API & MCP and create a key. Read-only unless you choose read and write.
Step 2
Add Brikt to your assistant
Point your MCP-capable assistant at Brikt’s MCP server and give it the key.
Step 3
Ask for the work
“What’s on the Board tomorrow?” “Start an estimate for the Delgado patio.” Review what it builds before it goes to a customer.
API and MCP are on Pro and Commercial
Give your assistant a real job to work on.
Start on Starter and move to Pro when you want the Board, receiving, crew chat and API and MCP access.