Local services & SaaS
Clear Estimates
Customers, estimates, proposals and invoices in Clear Estimates remodeling software.
9 endpoints
Estimate Rocket offers its API only through a private Zapier app that creates projects, payments and clients (checked 16 Nov 2026). Cotlet runs a hosted Estimate Rocket MCP server with 31 tools that ChatGPT and Claude use in your own contractor account. Proposals, invoices and texts to clients wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Estimate Rocket. Estimate Rocket is a trademark of its owner. If Estimate Rocket's own integrations cover what you need, use them first.
31 tools Read and write
Estimate Rocket offers its API through a private Zapier integration. The account owner signs in at estimaterocketapi.com, then adds Estimate Rocket in Zapier from an invite link, since the app does not show up in Zapier search. No Estimate Rocket MCP server or ChatGPT or Claude connector was found.
| What you need | Zapier app | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Line items, proposals and change orders | Find Proposal and triggers | One project at a time | Writes after your OK |
| Schedule work and assign crews | Assignment triggers only | Drag and drop | Schedule, planner, crews |
| Invoices, payments and client texts | Create Payment, Find Invoice | One invoice at a time | 31 tools, REST too |
Checked 16 Nov 2026. Sources: Estimate Rocket Integrations (API) · Estimate Rocket API · API: new endpoints via webhook · Estimate Rocket pricing · Help: Adding Clients · Help: Searching For Clients · Help: Editing Client Information · Help: Deleting Clients · Help: Exporting Clients · Help: Client Project History · Help: Managing Leads · Help: Creating a Project · Help: Changing the Stage of a Project · Help: Changing a Project's Client · Help: Project Notes · Help: Project Tags · Help: Uploading Photos · Help: Uploading Files · Help: Deleting and Canceling Projects · Help: Quickly Adding Line Items · Help: Delete a Line Item · Help: Discounts · Help: Bulk Changing a Labor or Material Item · Help: Edit Your Default Labor Rate · Help: Generating Your Proposal · Help: Creating Change Orders · Help: Request Changes Notes · Help: Never Viewed Proposals Report · Help: Deposit and Progress Invoices · Help: Crediting a Customer · Help: Applying Payments · Help: Tracking Expenses · Help: Customer Open Invoices Report · Help: Schedule Filters · Help: Employee Planner · Help: Scheduling Appointments · Help: Scheduling Project Tasks · Help: Rescheduling Appointments · Help: Crew Assignment · Help: Texting Documents to Your Clients · Help: Using SMS Templates · Help: Email Templates · Help: Automated Email Follow Ups
Once, in a browser we host for you.
One address in its settings.
Price the estimate, then approve the proposal.
Your agent works in your own signed-in Cloud Browser. Proposals, invoices, texts and anything else that reaches a client wait for your OK. Who can see your session
Sign in to Estimate Rocket in a Cloud Browser. Open login.estimaterocket.com in your Cotlet Cloud Browser and log in with your own Estimate Rocket user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Estimate Rocket shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector covers them all. Added Estimate Rocket after connecting? Refresh the connector and its 31 tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: estimate_rocket_read One tool per owner workflow in the Estimate Rocket knowledge base. Reports, the schedule and client history only read; everything that changes a project asks first.
Search before you add: the client search covers name, phone, address and company. A client profile carries its project history and totals.
Returns the matching clients as the Clients page lists them. Run it before adding a client or a lead so the same homeowner is not added twice. It changes nothing and runs without asking.
MCP callestimate_rocket_read → search_clients
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/clients/search
| Name | Type | Description |
|---|---|---|
| query string required | string | Name, phone number, address or company name. |
{
"query": "query"
} {
"clients": [
{
"name": "Example Homeowner",
"company": "",
"phone": "+1 555 0100",
"address": "14 Maple Street, Springfield"
}
]
} Returns the projects listed under the client information, with the Total Projects Value (the sum of all projects) and the Accepted Proposals Value (the sum of all accepted proposals). Read only.
MCP callestimate_rocket_read → get_client_project_history
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/client-project-history
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as search_clients returns it. |
{
"client": "client"
} {
"client": "Example Homeowner",
"projects": [
{
"name": "Maple Street exterior repaint",
"stage": "Work in progress",
"value": 7760
},
{
"name": "Maple Street interior, two rooms",
"stage": "Completed",
"value": 2950
}
],
"total_projects_value": 10710,
"accepted_proposals_value": 10710
} Returns the file Estimate Rocket builds when you select Download (.CSV) under Settings > Client Export. Read only.
MCP callestimate_rocket_read → export_clients
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/clients/export
No parameters.
{
"file": "clients.csv",
"rows": 412
} Uses the + Client button on the Clients page and the edit button on the client profile. The SMS preferences decide whether a client can receive texts, so text_document depends on them. Delete is the button at the bottom of the edit dialog. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `delete`. |
| client string | string | Client name, for `update` and `delete`. |
| fields object | object | For `create` and `update`: contact information, billing information, custom tax rate, notes, SMS preferences, potential value (a number) and client stage. |
{
"action": "action"
} {
"client": "Example Homeowner",
"client_stage": "Prospect",
"potential_value": 8000,
"sms_for_documents": true,
"saved": true
} A lead looks like a project but has its own buttons (Create Estimate, Create Invoice, Create Work Order) and its own follow-up campaigns. `list` reads the Projects page with the Lead filter on. Search the client first so the lead does not duplicate one. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → manage_leads
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/leads/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. |
| client string | string | For `create`: an existing client, or the details of a new one. |
| scope string | string | Scope of work or notes from the call or web form. |
{
"action": "action"
} {
"lead": "Oak Court deck stain",
"client": "Sample Homes LLC",
"scope": "Stain the rear deck and railings, about 400 sq ft",
"saved": true
} Create the project, move its stage, fix the client, keep notes and #tags, add photos and files. Deleting a project cannot be undone; archiving can.
Creating a project for a new client also stores that client. Most tools take a project, so this is often the first write. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → create_project
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/projects
| Name | Type | Description |
|---|---|---|
| client string required | string | An existing client, or the details of a new client. |
| name string | string | Project name. |
| stage string | string | Stage to start at. Leave empty for Estimate, the green + Estimate button. |
{
"client": "client"
} {
"project": "Maple Street exterior repaint",
"number": 1047,
"client": "Example Homeowner",
"stage": "Estimate",
"saved": true
} Uses Manage Assignment and Override on the project. The stage decides which follow-up campaign starts, so the agent names the old and new stage before saving. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → change_project_stage
REST endpointPATCH https://cotlet.dev/api/v1/estimate-rocket/project-stage
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| stage string required | string | The stage to move to, from the Who Will list. |
{
"project": "project",
"stage": "stage"
} {
"project": "Maple Street exterior repaint",
"from": "Pending Acceptance",
"to": "Schedule Work",
"saved": true
} Uses Change Client on Project from the project gear menu. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → change_project_client
REST endpointPATCH https://cotlet.dev/api/v1/estimate-rocket/project-client
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| client string required | string | The client to move the project to. |
{
"project": "project",
"client": "client"
} {
"project": "Oak Court deck stain",
"client": "Sample Homes LLC",
"saved": true
} Customer notes appear below the line items on documents the client sees; internal notes and their #tags stay inside Estimate Rocket and can be searched in any search bar. The agent writes your words and adds nothing you did not say. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → update_project_notes
REST endpointPATCH https://cotlet.dev/api/v1/estimate-rocket/project-notes
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| type string required | string | `customer` (shown on your documents) or `internal` (only your users see it). |
| notes string required | string | The note. Tags start with # and are one word, for example #exterior or #zone1. |
{
"project": "project",
"type": "type",
"notes": "notes"
} {
"project": "Maple Street exterior repaint",
"type": "internal",
"notes": "Gate code 4411. #exterior #zone1",
"tags": [
"#exterior",
"#zone1"
],
"saved": true
} Photos can go on documents for the client or stay internal. Files are stored on the project and can be attached to emails from there. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → upload_project_file
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/project-files
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| file_url string required | string | A link the Cloud Browser can download the file from. |
| kind string required | string | `photo` for the Photos section, `file` for the Files section. |
| include_in_document boolean | boolean | Photos only: show it on the project document the client sees. |
{
"project": "project",
"file_url": "https://example.com",
"kind": "kind"
} {
"project": "Maple Street exterior repaint",
"kind": "photo",
"name": "north-wall-before.jpg",
"include_in_document": true,
"uploaded": true
} Archived projects stay in the system as inactive and can be reactivated. Delete removes the project with all its proposals, invoices, payments, photos and notes and cannot be undone. A project past the Mark Invoice as Sent stage cannot be canceled. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → archive_or_delete_project
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/or-delete-project/archive
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| action string required | string | One of `archive`, `delete`. |
{
"project": "project",
"action": "action"
} {
"project": "Oak Court deck stain",
"archived": true
} Line items from item templates or your library, discounts as negative lines, bulk swaps of labor or material, and the default labor rate.
Uses the Universal + button on the project. Estimate Rocket has no discount field: a discount is a line item with a negative unit price, and a percent is a generic line item with unit $, unit price -0.03 for 3% and the project total as quantity. The agent shows the lines and the new total before saving. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → manage_line_items
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/line-items/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `delete`, `discount`. |
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| template string | string | For `add`: an item template (estimate builder), for example Painting - Interior 2 coats. |
| items array | array | For `add`: items from your library, each with quantity and unit price. |
| item string | string | For `delete`: the line item to remove. |
| discount object | object | For `discount`: an `amount` in dollars or a `percent`. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street exterior repaint",
"added": [
{
"item": "Discount 3%",
"quantity": 8000,
"unit": "$",
"unit_price": -0.03,
"total": -240
}
],
"project_total": 7760,
"saved": true
} Meant for jobs where the same labor differs only in tax or rate, such as residential against commercial work. Run it after all areas are added: areas added later keep the default item. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → bulk_change_line_items
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/change-line-items/bulk
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| from_item string required | string | The labor or material item in the project now. |
| to_item string required | string | The library item to use instead, for example the taxable version of the same labor. |
{
"project": "project",
"from_item": "from item",
"to_item": "to item"
} {
"project": "Riverside office repaint",
"from_item": "Painting labor, non-taxable",
"to_item": "Painting labor, taxable",
"changed": 6,
"saved": true
} Edits the Labor Cost ($/hr) field in the Defaults row of Settings > Account Settings and saves with Update. It changes pricing on future estimates, so the agent shows the old and new rate first. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → set_default_labor_rate
REST endpointPUT https://cotlet.dev/api/v1/estimate-rocket/default-labor-rate
| Name | Type | Description |
|---|---|---|
| labor_cost number required | number | Dollars per hour. |
{
"labor_cost": 1
} {
"labor_cost_per_hour": {
"from": 55,
"to": 60
},
"saved": true
} A proposal is a snapshot of the project. Change orders cover extra work on a job in progress. Two reads show what clients asked for and what they never opened.
A proposal is a snapshot of the project when it is made: later line item changes need a new proposal. Creating and emailing are separate calls, so you can read the proposal before it reaches the client. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → create_proposal
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/proposals
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `email`. |
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| proposal string | string | For `email`: the proposal to send. Defaults to the newest. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street exterior repaint",
"proposal": "Proposal 2",
"total": 7760,
"status": "Unsigned",
"emailed": false
} Uses the + button in the Proposals row and the Change Order option. The new group is left out of the project until the client approves the change order, then included again. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → create_change_order
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/change-orders
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| group string required | string | The group holding the added line items, for example Change Order. |
| email boolean | boolean | Email the change order to the client after saving. |
{
"project": "project",
"group": "group"
} {
"project": "Maple Street exterior repaint",
"change_order": "Change Order 1",
"group": "Change Order",
"total": 640,
"emailed": false
} Returns the notes behind the blue Note icon in the project's Proposals row. Read only.
MCP callestimate_rocket_read → get_change_request_notes
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/change-request-notes
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
{
"project": "project"
} {
"project": "Oak Court deck stain",
"proposal": "Proposal 1",
"note": "Can you price the front steps as an option?"
} Returns the Never Viewed Proposals report. A proposal drops off when its active period ends. The report cannot be downloaded as CSV in Estimate Rocket, so this is the way to get the list out. Read only.
MCP callestimate_rocket_read → get_never_viewed_proposals
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/never-viewed-proposals
| Name | Type | Description |
|---|---|---|
| search string | string | Optional search, as on the report page. |
{
"proposals": [
{
"project": "Oak Court deck stain",
"client": "Sample Homes LLC",
"sent": "2026-11-09",
"total": 2150
},
{
"project": "Elm Road trim",
"client": "Example Property Co",
"sent": "2026-11-11",
"total": 1380
}
]
} Deposit, progress and credit invoices, payments against them, job expenses and the Open Invoices report.
Uses the + button in the project's Invoices section. A credit also needs a minus line item for the same amount, which the agent adds with manage_line_items. Sending is a separate call, so you can read the invoice first. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → create_invoice
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/invoices
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `send`. |
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| name string | string | Invoice name, for example Deposit. |
| date string | string | ISO date. |
| amount number | number | Dollar amount. Give this or `amount_percent`. |
| amount_percent number | number | Percent of the project total. |
| description string | string | What the invoice is for. |
| type string | string | `invoice` or `credit`. A credit takes a negative amount for money the client will not pay. |
{
"action": "create",
"project": "Maple Street exterior repaint",
"name": "Deposit",
"date": "2026-11-18",
"amount_percent": 30,
"description": "30% deposit to book the start date",
"type": "invoice"
} {
"project": "Maple Street exterior repaint",
"invoice": "Deposit",
"project_total": 7760,
"amount": 2328,
"date": "2026-11-18",
"sent": false
} Uses the + button in the Payments section. A payment for the full amount marks the invoice Paid; partial payments add up until it is paid. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → apply_payment
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/payment/apply
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| invoice string required | string | The invoice the payment is for. |
| amount number | number | Defaults to the invoice amount. Lower it for a partial payment. |
| reference string | string | Check number or other reference. |
| notes string | string | Notes on the payment. |
{
"project": "project",
"invoice": "invoice"
} {
"project": "Maple Street exterior repaint",
"invoice": "Deposit",
"amount": 2328,
"reference": "Check 3318",
"invoice_status": "Paid"
} Uses the + button in the project's Expenses section, where you track actual material, labor, subcontractor and equipment costs against the job. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → add_expense
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/expenses
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| kind string required | string | `material` or `labor`. |
| details object | object | The other expense fields, as you give them. |
{
"project": "project",
"kind": "kind"
} {
"project": "Maple Street exterior repaint",
"kind": "material",
"description": "Exterior paint, 18 gallons",
"amount": 1134,
"saved": true
} Returns the unpaid invoices from Reports > Open Invoices. Read only. To show a client the same list, a portal link in an email template ({customer_portal_url}) does it.
MCP callestimate_rocket_read → get_open_invoices_report
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/open-invoices-report
| Name | Type | Description |
|---|---|---|
| client string | string | Client name, typed into the report search bar. |
| project string | string | Project name or address, to narrow it to one project. |
{
"client": "Sample Homes LLC",
"open_invoices": [
{
"project": "Oak Court deck stain",
"invoice": "Final",
"amount": 1290
}
]
} Read the Schedule page and the Employee Planner, book estimate visits and work, move them and assign crews.
Crews show as one entry, not each member. Read only.
MCP callestimate_rocket_read → view_schedule
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/schedules/view
| Name | Type | Description |
|---|---|---|
| view string | string | `week` or `month`. |
| type string | string | One of `Work Appt`, `Work Appt & To Dos`, `Estimate Appt`, `Estimate Appt & To Dos`, `Project Todo`, `Non-Project To Dos`. |
| employees array | array | Employees or a saved employee filter. |
| show_completed boolean | boolean | Include completed items. |
| pending boolean | boolean | Also return the Pending Schedule list of projects not yet on the calendar. |
{
"week": "2026-11-16",
"items": [
{
"date": "2026-11-17",
"type": "Estimate Appt",
"project": "Elm Road trim",
"assigned": "Estimator"
},
{
"date": "2026-11-18",
"type": "Work Appt",
"project": "Maple Street exterior repaint",
"assigned": "Exterior crew"
}
],
"pending": [
"Oak Court deck stain"
]
} Reads Employee Planner on the Schedule page. Use it before schedule_appointment to find who is not scheduled. Read only.
MCP callestimate_rocket_read → view_employee_planner
REST endpointGET https://cotlet.dev/api/v1/estimate-rocket/employee-planners/view
| Name | Type | Description |
|---|---|---|
| week string | string | ISO date in the week. Defaults to this week. |
{
"week": "2026-11-16",
"employees": [
{
"name": "Estimator",
"scheduled": [
"Mon",
"Tue",
"Thu"
]
},
{
"name": "Painter B",
"scheduled": []
}
]
} Also schedules a project from the Pending Schedule list. Your employees and the client plan around the date, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → schedule_appointment
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/appointment/schedule
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| date string required | string | ISO date. |
| time string | string | Start time. |
| assignee string | string | Employee or crew. |
| notes string | string | Notes for the appointment. |
{
"project": "project",
"date": "date"
} {
"project": "Oak Court deck stain",
"type": "Work Appt",
"date": "2026-11-20",
"time": "08:00",
"assignee": "Exterior crew",
"scheduled": true
} Uses Reschedule in the project Actions row, then Reassign. The agent tells you the old and new date. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → reschedule_appointment
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/appointment/reschedule
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| date string required | string | New ISO date. |
| assignee string | string | Employee or crew, if it changes. |
{
"project": "project",
"date": "date"
} {
"project": "Maple Street exterior repaint",
"from": "2026-11-18",
"to": "2026-11-19",
"assignee": "Exterior crew",
"saved": true
} A crew is the main assignment, and its crew leader marks the work order complete. Estimate Rocket does not let a crew be a helper on a project. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → assign_crew
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/crew/assign
| Name | Type | Description |
|---|---|---|
| crew string required | string | Crew name. |
| project string | string | Project, for a project or to-do assignment. |
| task string | string | A non-project task or a project to-do. |
| date string | string | ISO date, for a task. |
{
"crew": "crew"
} {
"crew": "Exterior crew",
"project": "Maple Street exterior repaint",
"role": "main assignment",
"saved": true
} Texts reach clients who allow SMS. Email templates and follow-up campaigns run under Settings.
Uses Text Document on the project. The client needs "Client will receive SMS for documents" checked on their record. The text links to the customer portal, where the client sees every document on the project and can message you. The text is saved under Communications. It reaches your client and cannot be pulled back. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → text_document
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/document/text
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| document string required | string | The proposal, change order, invoice or receipt to send. |
{
"project": "project",
"document": "document"
} {
"project": "Oak Court deck stain",
"document": "Proposal 1",
"to": "Sample Homes LLC",
"texted": true
} Uses Send Text Message on the project detail. It reaches your client and cannot be pulled back. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → send_text_message
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/text-messages
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as Estimate Rocket shows it. |
| template string required | string | SMS template name. |
{
"project": "project",
"template": "template"
} {
"project": "Oak Court deck stain",
"template": "Friendly invoice reminder",
"to": "Sample Homes LLC",
"sent": true
} Created under Settings > Email Templates with + Template. Tokens fill in the client, employee and company details on each email. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → manage_email_templates
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/email-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. |
| name string | string | Template name, for example Estimate Pending: Customer Follow Up. |
| subject string | string | Subject line. |
| body string | string | Body with tokens such as {client_first_name} or {customer_portal_url}. |
| attachments array | array | Documents to attach, for example Estimate 1. |
{
"action": "action"
} {
"template": "Estimate Pending: Customer Follow Up",
"subject": "Just checking in",
"tokens": [
"{client_first_name}"
],
"saved": true
} Campaigns live under Settings > Follow Up Campaigns, one per project stage; 5 of the 9 are set up by default. An automatic campaign starts when a project reaches its stage. These emails reach your clients over days, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callestimate_rocket_write → manage_follow_up_campaigns
REST endpointPOST https://cotlet.dev/api/v1/estimate-rocket/follow-up-campaigns/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `update`, `start`. |
| campaign string | string | Campaign name, for example Pending Acceptance. |
| mode string | string | For `update`: `manual` or `automatic`. |
| emails array | array | For `update`: each email template with its After # Days. |
| project string | string | For `start`: the project, for a manual campaign. |
{
"action": "action"
} {
"campaign": "Pending Acceptance",
"mode": "automatic",
"emails": [
{
"template": "Estimate follow up 1",
"after_days": 2
},
{
"template": "Estimate follow up 2",
"after_days": 5
}
],
"saved": true
} Your signed-in Estimate Rocket browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 31 Estimate Rocket tools. The session cookie stays in the Cloud Browser.
The clients, projects, schedule and reports your Estimate Rocket user can open, and nothing more.
Your users and employee permissions, payment processing, the QuickBooks Online link and your Zapier connection.
You log in again yourself, in the same Cloud Browser.
Turn Estimate Rocket off for agents, reset the browser, or change your Estimate Rocket password.
Cotlet never sees or stores your password: you type it yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (results).
| Action | How to put it right |
|---|---|
| Line item or discount | Delete the line with manage_line_items, then create a new proposal |
| Stage, client or appointment date | Call change_project_stage, change_project_client or reschedule_appointment again |
| Archived project | Reactivate it in Estimate Rocket |
| Deleted project | Gone with its proposals, invoices and payments: delete always asks first |
| Proposal emailed or document texted | Already with your client: follow up with them directly |
All 23 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 8 read tools, reports, the schedule and client history, run at once.
{
"name": "create_invoice",
"arguments": {
"action": "create",
"project": "Maple Street exterior repaint",
"name": "Deposit",
"date": "2026-11-18",
"amount_percent": 30,
"description": "30% deposit to book the start date",
"type": "invoice"
}
} curl -X POST https://cotlet.dev/api/v1/estimate-rocket/invoices \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","project":"Maple Street exterior repaint","name":"Deposit","date":"2026-11-18","amount_percent":30,"description":"30% deposit to book the start date","type":"invoice"}' {
"project": "Maple Street exterior repaint",
"invoice": "Deposit",
"project_total": 7760,
"amount": 2328,
"date": "2026-11-18",
"sent": false
} The example bills 30% of the $7,760 Maple Street total, after the 3% discount on $8,000: a $2,328 deposit, created but not sent. A cron job or n8n flow can make the same call over REST at /api/v1/estimate-rocket with the same key and price, in JSON. Failed calls are free.
About $26 a monthfor a painting or remodeling contractor with about a dozen new estimates, 4,560 credits. Your Estimate Rocket plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning schedule and planner check | 2 × 22 | 440 |
| New leads and estimate visits | 3 × 15 | 450 |
| Line items, discount and proposal | 4 × 12 | 480 |
| Monday unopened proposal texts | 6 × 4 | 240 |
| Crew bookings and reschedules | 2 × 20 | 400 |
| Deposit and progress invoices | 1 × 20 | 200 |
| Payments applied | 1 × 25 | 250 |
| Expenses and job photos | 1 × 40 | 400 |
| Friday open invoices and reminders | 5 × 4 | 200 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 306 calls | 4,560 |
The smallest pack, 5,000 credits for $29, covers this month. More estimators and more jobs use more calls.
Estimate Rocket plans start at $139 a month with 3 full users (pricing page, 16 Nov 2026); that stays between you and Estimate Rocket. Cotlet credit packs are one-time purchases, not a subscription, and the month above is our own example, not measured usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Estimate Rocket Zapier app | Creates projects, payments and clients, finds records and fires triggers on new records and proposal status. | No line items, proposals, invoices, schedule or texts; new endpoints come from the Estimate Rocket team. |
| Follow-up campaigns and email templates | Estimate Rocket's own emails per project stage, sent after set days. | They run on stage rules, not on a question you ask an agent. |
| QuickBooks Online integration | Estimate Rocket's own link that sends new invoices to QuickBooks Online. | Accounting sync, not a route for an AI agent. |
| By hand | Open each project, the Schedule page and Reports and click through. | One screen at a time, only while you are at the desk. |
If a Zap with the three official actions covers your job, use it: it is the vendor's own route, and Cotlet works beside it. Cotlet fits when you want ChatGPT, Claude or a script to price estimates, book crews and follow up with clients today, from your own login, with nothing to host.
Take Group sp. z o.o. runs Cotlet.dev. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Estimate Rocket tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=estimate-rocket, turn on Estimate Rocket under Integrations in the console and log in at https://login.estimaterocket.com/ in your Cloud Browser. Then connect your AI agent and ask it about a project. The trial needs no card.
Estimate Rocket offers its API through a private Zapier integration: the account owner signs in at estimaterocketapi.com, then adds Estimate Rocket in Zapier from an invite link (checked 16 Nov 2026). It documents three actions (Create Project, Create Payment, Create Client), searches and event triggers. No Estimate Rocket MCP server or ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Estimate Rocket account.
The Zapier integration is Estimate Rocket's own API route. It creates projects, payments and clients and fires triggers when records change, and new endpoints come from the Estimate Rocket team. Cotlet works in your signed-in account, so your agent can also price line items, create proposals, invoices and change orders, schedule crews and text clients. You can use both.
Only clients whose record has "Client will receive SMS for documents" checked receive document texts, as in Estimate Rocket itself. text_document and send_text_message ask for your OK before every text by default.
Use the user whose work the agent should do. Estimate Rocket has full users and field users, and employee permissions decide what each one can open; the agent sees exactly what that user sees. Reports, invoices and settings need a user who can open them.
Only in how it is called. Both carry the same 31 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Estimate Rocket.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy