Bolster API and MCP server Let your AI agent quote, schedule and bill the job.

ToolWhat it doesAccess

• manage_crm_pipeline Read the Bolster pipeline: every lead, estimate, booked job and payment by stage. read

  Bolster moves each client and job through the Pipeline stages by itself, from lead to estimate, booking, progress and payment. This tool reads that board and, for one job, the proposal interactions Bolster tracks, such as when the client opened or changed the quote. It changes nothing and runs without asking.

  MCP callbolster_read → manage_crm_pipeline

  REST endpointGET https://cotlet.dev/api/v1/bolster/crm-pipelines/manage

  Parameters

  Parameters: manage_crm_pipeline

  Name	Type	Description
  stage string	string	Pipeline stage to read, in Bolster's words: lead, estimate sent, booked, in progress or payment. Leave empty for all.
  job string	string	One client or job to open, with its interactions. Leave empty for the list.

  Example response

  {
    "stage": "estimate sent",
    "jobs": [
      {
        "job": "Maple Street deck",
        "client": "Example Homeowner",
        "estimate": 10590,
        "proposal_opened": "2026-11-12"
      },
      {
        "job": "Hill Road basement",
        "client": "Sample Client",
        "estimate": 38200,
        "proposal_opened": null
      }
    ]
  }

ToolWhat it doesAccess

• generate_ai_estimates Ask Bolster AI to draft an estimate from a plain-words job description or a past estimate. writeAsks first

  Bolster describes this on its Construction Intelligence and estimating pages: describe the job or upload a past estimate, and Bolster builds quantities and costs. The agent returns the draft lines for you to check and saves nothing past what Bolster AI creates. Read the result with create_estimates before it goes into a proposal. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → generate_ai_estimates

  REST endpointPOST https://cotlet.dev/api/v1/bolster/ai-estimates/generate

  Parameters

  Parameters: generate_ai_estimates

  Name	Type	Description
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  prompt string	string	The job in plain words, for example "Composite deck, 20 x 16, with stairs and railing".
  past_estimate_url string	string	Optional: a link to an old estimate file the Cloud Browser can download, to start from instead of the prompt.

  Example input

  {
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "prompt": "Composite deck, 20 x 16, with stairs and railing",
    "draft": [
      {
        "item": "Composite decking",
        "quantity": 320,
        "unit": "sq ft"
      },
      {
        "item": "Aluminum railing",
        "quantity": 52,
        "unit": "lf"
      },
      {
        "item": "Stairs, 4 steps",
        "quantity": 1,
        "unit": "each"
      }
    ]
  }

• measure_takeoffs Read a job's takeoff, or enter areas, lengths and counts and link them to estimate items. writeAsks first

  Bolster's takeoff measures areas, lengths and counts on plans, satellite images or a drawing, and links them to items, assemblies or calculations. The agent enters the measurements you give it; it does not measure drawings by itself. Takeoff is on Bolster's Pro plan and up. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → measure_takeoffs

  REST endpointPOST https://cotlet.dev/api/v1/bolster/takeoffs/measure

  Parameters

  Parameters: measure_takeoffs

  Name	Type	Description
  action string required	string	One of `get`, `create`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  measurements array	array	For `create`: label, type (`area`, `length` or `count`), value and unit, plus the estimate item each one feeds.

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "measurements": [
      {
        "label": "Deck surface",
        "type": "area",
        "value": 320,
        "unit": "sq ft",
        "item": "Composite decking"
      },
      {
        "label": "Railing run",
        "type": "length",
        "value": 52,
        "unit": "lf",
        "item": "Aluminum railing"
      }
    ],
    "saved": true
  }

• create_estimates List or read a job's estimates, or build one from assemblies and items. writeAsks first

  Bolster estimates are built from items and pre-built assemblies with costs and profit; items can carry formulas tied to dimensions or a takeoff, and AutoCost can fill live material and labor prices on plans that include it. The agent shows you the lines and total before it saves. A revision to an estimate the client has seen triggers a new approval in Bolster. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → create_estimates

  REST endpointPOST https://cotlet.dev/api/v1/bolster/estimates

  Parameters

  Parameters: create_estimates

  Name	Type	Description
  action string required	string	One of `list`, `get`, `create`, `update`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  estimate string	string	Estimate name, for `get` and `update`.
  lines array	array	For `create` and `update`: item or assembly, quantity, unit and unit cost per line. Leave unit cost empty to keep the price Bolster fills in.

  Example input

  {
    "action": "create",
    "job": "Maple Street deck",
    "lines": [
      {
        "item": "Composite decking",
        "quantity": 320,
        "unit": "sq ft",
        "unit_cost": 18
      },
      {
        "item": "Aluminum railing",
        "quantity": 52,
        "unit": "lf",
        "unit_cost": 65
      },
      {
        "item": "Stairs, 4 steps",
        "quantity": 1,
        "unit": "each",
        "unit_cost": 1450
      }
    ]
  }

  Example response

  {
    "job": "Maple Street deck",
    "estimate": "Composite deck, 20 x 16",
    "lines": 3,
    "total": 10590,
    "saved": true
  }

• manage_selections Make an estimate item optional, add costed upgrades, or turn it into a selection. writeAsks first

  An optional item can be added or removed by the client in the presentation; upgrades give "good, better, best" alternatives priced to the estimate dimensions; a selection combines style, color and finish choices. These change what the client can choose and pay, so the agent shows the choices before saving. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → manage_selections

  REST endpointPOST https://cotlet.dev/api/v1/bolster/selections/manage

  Parameters

  Parameters: manage_selections

  Name	Type	Description
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  item string required	string	Estimate item or assembly, for example Composite decking.
  kind string required	string	One of `optional`, `upgrade`, `selection`.
  choices array	array	For `upgrade` and `selection`: the alternatives, each with a name and its cost.

  Example input

  {
    "job": "job",
    "item": "item",
    "kind": "kind"
  }

  Example response

  {
    "job": "Maple Street deck",
    "item": "Composite decking",
    "kind": "upgrade",
    "choices": [
      {
        "name": "Standard composite",
        "cost": 5760
      },
      {
        "name": "Capped composite",
        "cost": 7040
      }
    ],
    "saved": true
  }

• create_presentations Read a job's proposal presentation, or send it to the client by email or SMS. writeAsks first

  Bolster builds the presentation from the finished estimate. The client picks options, signs the embedded contract, pays the deposit and picks a start date on the same page. A sent proposal reaches your client and cannot be pulled back by the agent. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → create_presentations

  REST endpointPOST https://cotlet.dev/api/v1/bolster/presentations

  Parameters

  Parameters: create_presentations

  Name	Type	Description
  action string required	string	One of `get`, `send`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  channel string	string	For `send`: `email` or `sms`.
  message string	string	For `send`: a short note to the client.

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "proposal": "Composite deck, 20 x 16",
    "total": 10590,
    "channel": "email",
    "sent": true
  }

ToolWhat it doesAccess

• schedule_jobs Read a booked job's schedule, move a task, assign it, or approve a finished task. writeAsks first

  Bolster creates the schedule from the estimate items when a job is booked, grouped into project stages your client can see. Assigning notifies the crew or sub. Approving a task the team marked complete makes Bolster send the client a payment request through the client portal, so `approve` is money as well as scheduling. Job scheduling is on the Pro plan and up. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → schedule_jobs

  REST endpointPOST https://cotlet.dev/api/v1/bolster/jobs/schedule

  Parameters

  Parameters: schedule_jobs

  Name	Type	Description
  action string required	string	One of `list`, `update`, `assign`, `approve`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  task string	string	Schedule task, for `update`, `assign` and `approve`.
  start_date string	string	For `update`: ISO date.
  assignee string	string	For `assign`: an employee or a subcontractor.
  notify string	string	For `assign`: `email`, `sms` or `chat` (Bolster Chat).

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "task": "Footings and posts",
    "assignee": "Example Concrete",
    "notify": "sms",
    "start_date": "2026-11-18",
    "saved": true
  }

• manage_job_budget Read a job's budget and material list, or enter an actual cost against a budget line. writeAsks first

  Bolster builds the material list and the budget from the estimate when the job is booked, laid out to your dimensions. When a cost differs, you update the actuals column in the job's budget tab; this tool does that line by line after your OK. `get` reads and changes nothing. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → manage_job_budget

  REST endpointPOST https://cotlet.dev/api/v1/bolster/job-budget/manage

  Parameters

  Parameters: manage_job_budget

  Name	Type	Description
  action string required	string	One of `get`, `update`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  view string	string	For `get`: `budget` or `materials`.
  line string	string	For `update`: the budget line.
  actual number	number	For `update`: the actual cost to enter.

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "view": "budget",
    "lines": [
      {
        "line": "Composite decking",
        "budget": 5760,
        "actual": 5615
      },
      {
        "line": "Aluminum railing",
        "budget": 3380,
        "actual": null
      },
      {
        "line": "Stairs",
        "budget": 1450,
        "actual": null
      }
    ]
  }

• send_rfq_requests Send a bid request from estimate items to vendors, compare the bids, or award one. writeAsks first

  Bids come back into Bolster lined up against the budget, so `list` shows who is under or over. An awarded bid becomes a vendor order in Bolster. Sending and awarding reach vendors outside your company, so the agent names them before it acts. RFQ management is on the Premium plan and up. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → send_rfq_requests

  REST endpointPOST https://cotlet.dev/api/v1/bolster/rfq-requests

  Parameters

  Parameters: send_rfq_requests

  Name	Type	Description
  action string required	string	One of `list`, `send`, `award`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  items array	array	For `send`: the estimate items to price.
  vendors array	array	For `send`: suppliers or subcontractors who should bid.
  due_date string	string	For `send`: ISO date the bids are due.
  vendor string	string	For `award`: the vendor whose bid wins.

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "items": [
      "Aluminum railing"
    ],
    "bids": [
      {
        "vendor": "Example Rail Supply",
        "amount": 3290,
        "versus_budget": -90
      },
      {
        "vendor": "Sample Fabrication",
        "amount": 3510,
        "versus_budget": 130
      }
    ]
  }

ToolWhat it doesAccess

• collect_customer_payments List a job's payment requests and payments, or send the client the next payment request. writeAsks first

  Bolster bills from finished work: the client pays online through the client portal, by card or bank transfer, and the money lands in Bolster Wallet (US and Canada). On Pro and up payments sync to QuickBooks Online. A payment request reaches your client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callbolster_write → collect_customer_payments

  REST endpointPOST https://cotlet.dev/api/v1/bolster/customer-payments/collect

  Parameters

  Parameters: collect_customer_payments

  Name	Type	Description
  action string required	string	One of `list`, `request`. `list` and `get` only read.
  job string required	string	Job or client name, as list in manage_crm_pipeline returns it.
  milestone string	string	For `request`: the stage or finished work being billed.
  amount number	number	For `request`: the amount, when it is not set by the payment schedule.

  Example input

  {
    "action": "action",
    "job": "job"
  }

  Example response

  {
    "job": "Maple Street deck",
    "payments": [
      {
        "milestone": "Deposit",
        "amount": 3177,
        "status": "paid"
      },
      {
        "milestone": "Framing complete",
        "amount": 4236,
        "status": "requested"
      },
      {
        "milestone": "Final",
        "amount": 3177,
        "status": "scheduled"
      }
    ]
  }