Local services & SaaS
Arborgold
Customers, estimates, jobs and invoices in Arborgold for tree care and landscaping.
6 endpoints
The ArborNote Open API comes only with the Enterprise plan and cannot build a proposal or book a crew, and no ArborNote MCP server was found (checked 16 Nov 2026). Cotlet runs a hosted ArborNote MCP server with 28 tools that ChatGPT and Claude use in your own account. Proposals, invoices and anything else that reaches a client wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by ArborNote. ArborNote is a trademark of its owner. If ArborNote's own integrations cover what you need, use them first.
28 tools Read and write
ArborNote has an Open API, but only on the Enterprise plan ($350 a month for one user, against $240 for Essential). Its documented endpoints read clients, projects, proposals, work orders, appointments and crew hours, and write clients, projects and a proposal's number, status and tax. No ArborNote MCP server and no official ChatGPT or Claude connector was found.
| What you need | ArborNote API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Plan it needs | Enterprise only | Any plan | Any plan |
| Build proposals from mapped trees | No create endpoint | One screen at a time | 28 tools, writes after your OK |
| Book work orders and estimator visits | Reads the calendar only | Drag and drop | After your OK |
| Run from n8n or a script | Your code, Enterprise | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: ArborNote Open API · ArborNote API documentation · ArborNote pricing · ArborNote integrations · Help Center: Create GTC proposals · Help Center: Optional items in proposals · Help Center: Work order scheduler · Help Center: Job requirements · Help Center: Crew hours · Help Center: Proposal reminders · Help Center: Ask ArborNote Sales · Help Center: ArborNote Pay
Once, in a browser we host for you.
One address in its settings.
It prices the trees, you approve.
Your agent works in your own signed-in Cloud Browser. Writes, and anything that reaches a client, wait for your OK. Who can see your session
Sign in to ArborNote in a Cloud Browser. Open app.arbor-note.com in your Cotlet Cloud Browser and log in with your own ArborNote 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.
ArborNote shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector reaches all of them. Turned ArborNote on later? Refresh the connector and the 28 ArborNote tools show up.
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: manage_proposal_reminders One tool per owner workflow in the ArborNote Help Center. Many take an `action`: `list` and `get` only read, the other actions write and ask first.
Projects, tree pins, groups, moves and restores, AI imports of customer tree lists, landscape assets and map links.
Follows Projects > Actions > Add: fill in market type, client, project name and address, then Save. The new project shows in the project list. `get` returns the project with its client and address. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_projects
REST endpointPOST https://cotlet.dev/api/v1/arbornote/projects/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`. `list` and `get` only read. |
| project string | string | Project name or ID, for `get`. |
| fields object | object | For `create`: market type, client name, project name and address, as the Add form asks. |
{
"action": "action"
} {
"project": "Oak Street HOA",
"client": "Oak Street HOA",
"market_type": "Commercial",
"address": "100 Oak Street, Example City",
"saved": true
} Opens the project, picks clone project from the three bar menu and saves the copy under the new name in your project list. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → clone_project
REST endpointPOST https://cotlet.dev/api/v1/arbornote/project/clone
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| new_name string required | string | Name of the copy. ArborNote needs it to differ from the original name. |
{
"project": "project",
"new_name": "new name"
} {
"project": "Oak Street HOA",
"clone": "Oak Street HOA 2027",
"saved": true
} ArborNote never deletes a project for good: archive takes it off your list, and view archived then restore project puts it back. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → archive_projects
REST endpointPOST https://cotlet.dev/api/v1/arbornote/projects/archive
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list_archived`, `archive`, `restore`. `list` and `get` only read. |
| project string | string | Project to archive or restore. |
{
"action": "action"
} {
"project": "Maple Court 2024",
"archived": true
} In the desktop app: open the project, check Add, right-click the spot to drop a tree pin, then open the pin to add details and photos. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → map_trees
REST endpointPOST https://cotlet.dev/api/v1/arbornote/trees/map
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| location object required | object | Where the pin goes: latitude and longitude. |
| attributes object | object | Fields of the tree attribute screen, such as species and notes. |
| photos array | array | Links of photos to attach to the tree. |
{
"project": "project",
"location": "location"
} {
"project": "Oak Street HOA",
"tree_id": 12,
"species": "Red oak",
"photos": 1,
"saved": true
} Groups come from the GTC list or a polygon on the Map. ArborNote has no add or remove inside a group: to add trees you create a group of the extra trees and merge the two, and to drop trees you save the rest as a new group and delete the old one. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_tree_groups
REST endpointPOST https://cotlet.dev/api/v1/arbornote/tree-groups/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `merge`, `copy`, `delete`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| name string | string | Group name, for `create`, `merge` and `copy`. |
| trees array | array | For `create`: the tree ID numbers to group. |
| groups array | array | For `merge`, `copy` and `delete`: the groups to use. |
{
"action": "action",
"project": "project"
} {
"project": "Oak Street HOA",
"group": "Street frontage",
"trees": [
3,
4,
7,
9
],
"saved": true
} Runs Move Tree and confirms. The move is permanent. To combine projects, move all trees, then archive the empty project with archive_projects. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → move_trees
REST endpointPOST https://cotlet.dev/api/v1/arbornote/trees/move
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| trees array required | array | Tree ID numbers to move, or `all` to combine the two projects. |
| destination string required | string | Project the trees move to. |
{
"project": "project",
"trees": "trees",
"destination": "destination"
} {
"project": "Oak Street HOA east",
"destination": "Oak Street HOA",
"moved": 14
} Reads Actions > Archived Tags in the project; Restore Highlighted returns the trees to the inventory on the map and in the list. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → restore_trees
REST endpointPOST https://cotlet.dev/api/v1/arbornote/trees/restore
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `restore`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| trees array | array | For `restore`: the tree ID numbers to bring back. |
{
"action": "action",
"project": "project"
} {
"project": "Oak Street HOA",
"restored": [
5,
8
]
} Uses the Actions download in the desktop app. ArborNote makes this an admin feature, so it needs an admin user. It changes nothing and runs without asking.
MCP callarbornote_read → export_inventory
REST endpointGET https://cotlet.dev/api/v1/arbornote/inventories/export
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| format string required | string | `shapefile` or `excel`. |
{
"project": "project",
"format": "format"
} {
"project": "Oak Street HOA",
"format": "excel",
"file": "oak-street-hoa-inventory.xlsx",
"trees": 42
} ArborNote maps and formats the file in the background, with no template or prompt file needed. You review the cleaned list first; after Import the trees show in the map view and the list view. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → import_inventory_ai
REST endpointPOST https://cotlet.dev/api/v1/arbornote/inventory-ais
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| file_url string required | string | Link to an .xlsx workbook or a .zip Shapefile. |
| refine string | string | Plain-language change for the AI to make to the cleaned list. |
| import boolean | boolean | False to return the cleaned list only; true to import it. |
{
"project": "project",
"file_url": "https://example.com"
} {
"project": "Example Parks District",
"file": "park-trees.xlsx",
"rows": 186,
"imported": false
} Each marker, area or line on the Map tab is its own record with its own services, so the estimate is built asset by asset. Cost, price and gross margin are linked: change one and ArborNote recalculates the other two. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_landscape_inventory
REST endpointPOST https://cotlet.dev/api/v1/arbornote/landscape-inventory/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add_asset`, `add_line_item`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| asset object | object | For `add_asset`: marker, area or line, with points, Name, Color and an optional Note. For `add_line_item`: the asset ID. |
| line_item object | object | Material Type (Plant or Hard), Description, unit material cost and price, labor hours and quantity, typed in or taken from the Part List Library. |
{
"action": "action",
"project": "project"
} {
"project": "Example Office Park",
"asset": "Front entry bed",
"type": "area",
"line_items": [
{
"description": "Seasonal color install",
"price": 640
}
],
"saved": true
} Uses Actions > Map Link, with the group filter first when you give one. You paste the link where you like; the tool sends nothing and runs without asking.
MCP callarbornote_read → get_map_link
REST endpointGET https://cotlet.dev/api/v1/arbornote/map-link
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| group string | string | Tree group to limit the map to. Leave empty for the whole inventory. |
{
"project": "project"
} {
"project": "Oak Street HOA",
"group": "Street frontage",
"map_link": "https://app.arbor-note.com/map/example"
} Objectives, prices and months on each tree, your GTC and PHC lists, and plans that spread work over several years.
Works on the General Tree Care tab of the project: each tree takes an objective, a price and months. These prices carry into the proposals built from the trees. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → set_tree_treatments
REST endpointPUT https://cotlet.dev/api/v1/arbornote/tree-treatments
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| trees array required | array | Tree ID numbers. Several trees use Edit Selection. |
| change string required | string | `add`, `update` or `delete`. |
| objective string | string | Objective from your list, for example Removal or Crown clean. |
| price number | number | Price for the objective. |
| months array | array | Months for the treatment, as the tree screen sets them. |
{
"project": "project",
"trees": "trees",
"change": "change"
} {
"project": "Oak Street HOA",
"trees": [
4
],
"objective": "Removal",
"price": 1800,
"months": [
"March"
],
"saved": true
} PHC treatments live under your name > Manage PHC Treatments. Entries made on the desktop show in the mobile app too, and you can add them to inventories and proposals. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_treatment_catalog
REST endpointPOST https://cotlet.dev/api/v1/arbornote/treatment-catalog/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| type string required | string | `gtc` for General Tree Care objectives or `phc` for Plant Health Care treatments. |
| name string | string | For `create`: the name. |
| description string | string | For `create`: the description. |
{
"action": "action",
"type": "type"
} {
"type": "phc",
"treatment": "Deep root fertilization",
"description": "Slow-release feeding at the drip line",
"saved": true
} Sales > Manage Multi Year Plans, then the pencil. The plan opens with its saved options and the disk icon saves it. ArborNote lists multi-year plans on the Enterprise plan. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_multi_year_plans
REST endpointPOST https://cotlet.dev/api/v1/arbornote/multi-year-plans/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `update`. `list` and `get` only read. |
| plan string | string | Plan name, for `get` and `update`. |
| trees array | array | For `update`: the tree ID numbers to change. |
| changes object | object | Timing, objective, hours and price, and the Select Years of those trees. |
{
"action": "action"
} {
"plan": "Oak Street HOA 2027 to 2029",
"trees": [
3,
9
],
"years": [
2027,
2029
],
"saved": true
} GTC and PHC proposals with optional items and follow-up reminders, Ask ArborNote Sales, the sales dashboard and project map reports. Sending waits for your OK.
Builds the proposal from the trees you pick, then Preview and Save. Optional items need hours or line item pricing, with Group trees and Separate Objectives off; the client picks them on the approval page. `send` uses the plane icon, which emails the proposal link to your client. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_gtc_proposals
REST endpointPOST https://cotlet.dev/api/v1/arbornote/gtc-proposals/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`. `list` and `get` only read. |
| project string | string | For `create`: the project. |
| proposal string | string | Proposal number, for `get` and `send`. |
| status string | string | For `list`: a status such as Draft, Approved, Scheduled or Completed. |
| trees array | array | For `create`: tree ID numbers with any objective or price changes for this proposal. |
| pricing string | string | `hours`, `line_item` or `flat_rate`. |
| separate_objectives boolean | boolean | One line item per objective on a tree, for line item pricing. |
| custom_costs array | array | Custom cost lines with name and price, from the Other Cost Calculator. |
| optional array | array | Trees or line items the client may leave out. |
| update_inventory boolean | boolean | Default true: proposal edits also change the inventory. False keeps them to this proposal. |
| reminder object | object | Follow-up after completion (30 Days to 2 Years), salesperson and note. |
{
"action": "create",
"project": "Oak Street HOA",
"trees": [
{
"tree": 4,
"objectives": [
{
"objective": "Removal",
"price": 1800
},
{
"objective": "Stump grind",
"price": 350
}
]
},
{
"tree": 7,
"objectives": [
{
"objective": "Crown clean",
"price": 650
}
]
}
],
"pricing": "line_item",
"separate_objectives": true,
"update_inventory": false
} {
"proposal": "P-2417",
"project": "Oak Street HOA",
"status": "Draft",
"lines": [
{
"tree": 4,
"objective": "Removal",
"price": 1800
},
{
"tree": 4,
"objective": "Stump grind",
"price": 350
},
{
"tree": 7,
"objective": "Crown clean",
"price": 650
}
],
"total": 2800,
"sent": false
} Starts from the Plant Health Care tab, then Create and a Proposal Preview, then Save. A saved proposal can be saved as PDF or edited. `send` uses the plane icon and reaches your client. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_phc_proposals
REST endpointPOST https://cotlet.dev/api/v1/arbornote/phc-proposals/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`. `list` and `get` only read. |
| project string | string | For `create`: the project. |
| proposal string | string | Proposal number, for `get` and `send`. |
| treatments array | array | For `create`: PHC treatments from the Plant Health Care tab, edits allowed. |
| trees array | array | For `create`: the trees to include. |
| reminder object | object | Follow-up after completion, salesperson and note. |
{
"action": "action"
} {
"proposal": "P-2420",
"project": "Example Residence",
"treatments": [
"Deep root fertilization",
"Dormant oil"
],
"total": 540,
"sent": false
} Sales > Proposal Reminders. A reminder falls due a set time after its proposal is marked Complete. ArborNote sends no email or push for reminders: this dashboard is the only place they show. A deleted reminder cannot be recovered. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_proposal_reminders
REST endpointPOST https://cotlet.dev/api/v1/arbornote/proposal-reminders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `update`, `delete`. `list` and `get` only read. |
| status string | string | For `list`: All, My reminders, Overdue, Due today, This week or Active. |
| type string | string | For `list`: All types, GTC or PHC. |
| reminder string | string | For `update` and `delete`: the reminder's proposal number. |
| changes object | object | For `update`: date, assignee or note. The date cannot move earlier than today. |
{
"action": "action"
} {
"totals": {
"overdue": 2,
"due_today": 1,
"due_this_week": 4,
"active": 31
},
"reminders": [
{
"proposal": "P-2188",
"client": "Example Residence",
"due": "2026-11-18",
"assignee": "Dana",
"note": "Ask about annual pruning"
}
]
} Uses Ask ArborNote Sales on the GTC tab of Manage Proposals. ArborNote counts and sums the real proposal records and lists the statuses and dates it used. Won counts Approved through Paid and Invoiced. No Sales Goal, no forecasts, no PHC proposals. It changes nothing and runs without asking.
MCP callarbornote_read → ask_sales
REST endpointGET https://cotlet.dev/api/v1/arbornote/sales/ask
| Name | Type | Description |
|---|---|---|
| question string required | string | For example: What is our close ratio this year? |
{
"question": "question"
} {
"question": "How much have we sold this month?",
"answer": "$38,400 across 17 proposals",
"filters_used": "Approved to Paid, 1 to 16 Nov 2026"
} The Help Center names the Sales Dashboard Desktop; its article has no text. Per the Ask ArborNote Sales article it holds the close ratio, Key Opportunities and the Sales Goal. It changes nothing and runs without asking.
MCP callarbornote_read → view_sales_dashboard
REST endpointGET https://cotlet.dev/api/v1/arbornote/sales-dashboards/view
No parameters.
{
"close_ratio": 0.41,
"sales_goal": 600000,
"sold_this_year": 412500,
"key_opportunities": [
{
"proposal": "P-2391",
"client": "Riverside Commons",
"total": 4950
}
]
} Reports > Project Map. Each report covers one project and does not add up several. It changes nothing and runs without asking.
MCP callarbornote_read → run_project_reports
REST endpointGET https://cotlet.dev/api/v1/arbornote/project-reports/run
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| report string required | string | `species_by_quantity`, `work_history_by_species`, `work_history_by_objective`, `work_history_by_month`, `age_distribution` or `health_by_quantity`. |
{
"project": "project",
"report": "report"
} {
"project": "Oak Street HOA",
"report": "health_by_quantity",
"rows": [
{
"health": "Good",
"trees": 28
},
{
"health": "Fair",
"trees": 11
},
{
"health": "Poor",
"trees": 3
}
]
} Estimator visits, work orders from approved proposals, permits and other requirements, extra work and crew hours.
Projects > Calendar. The appointment goes to the arborist assigned to the project and shows in their color; they also see it in the mobile app. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → schedule_estimator_appointment
REST endpointPOST https://cotlet.dev/api/v1/arbornote/estimator-appointment/schedule
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `schedule`. `list` and `get` only read. |
| project string | string | For `schedule`: a project in pending status. |
| date string | string | ISO date. |
| time string | string | Appointment time. |
| notes string | string | Notes for the arborist. |
{
"action": "action"
} {
"project": "Example Residence",
"arborist": "Sam",
"date": "2026-11-19",
"time": "10:00",
"saved": true
} Follows Sales > Manage Proposals, the calendar icon, then the scheduler window with Date, Time, Resources and Notes. Returns the work order link and PDF. With incomplete job requirements only an admin can go ahead. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → schedule_work_order
REST endpointPOST https://cotlet.dev/api/v1/arbornote/work-order/schedule
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `schedule`. `list` and `get` only read. |
| proposal string | string | For `schedule`: a proposal with Approved status. |
| date string | string | ISO date. |
| time string | string | Start time. |
| resources array | array | Crews and equipment to book. |
| notes string | string | Work order notes. |
{
"action": "action"
} {
"work_order": "WO-1190",
"proposal": "P-2391",
"date": "2026-11-24",
"time": "07:30",
"resources": [
"Crew 2",
"Bucket truck"
],
"link": "https://app.arbor-note.com/work-order/example"
} Requirements carry from the project and its trees into new proposals, where they become separate copies. They never block a proposal; scheduling warns, and only an admin can override. On the Essential and Enterprise plans, not on Basic. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_job_requirements
REST endpointPOST https://cotlet.dev/api/v1/arbornote/job-requirements/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `set`. `list` and `get` only read. |
| level string required | string | `project`, `tree` or `proposal`. |
| target string required | string | Project, tree ID or proposal number. |
| requirement string | string | From your Settings > Job Requirements list. |
| status string | string | Required - Not Started, In Progress / Pending, Complete / Verified, Not Applicable or Exception / Blocked. |
| notes string | string | Notes. |
{
"action": "action",
"level": "level",
"target": "target"
} {
"level": "project",
"target": "Oak Street HOA",
"requirements": [
{
"requirement": "Street use permit",
"status": "In Progress / Pending"
},
{
"requirement": "No-parking signs",
"status": "Complete / Verified"
}
]
} Crews add extra work in the Works app. On the desktop you edit it with the pencil before the work order is closed; closing creates the Extra Work proposal, whose number and link show in the work order summary. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_extra_work
REST endpointPOST https://cotlet.dev/api/v1/arbornote/extra-work/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `list` and `get` only read. |
| work_order string required | string | The GTC work order. |
| changes object | object | For `update`: the Extra Work fields to change. |
{
"action": "action",
"work_order": "work order"
} {
"work_order": "WO-1183",
"extra_work": [
{
"tree": 9,
"objective": "Deadwood removal",
"price": 300
}
],
"extra_work_proposal": null
} Work order hours feed job costing and the Production Report, so past dates change reported hours. Clock In/Out needs an admin, takes one entry per worker a day, and does not change work order hours. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_crew_hours
REST endpointPOST https://cotlet.dev/api/v1/arbornote/crew-hours/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `update`, `remove`. `list` and `get` only read. |
| record string required | string | `work_order` for work order hours or `clock` for daily Clock In/Out. |
| work_order string | string | For `work_order`: the work order. |
| date string | string | ISO date. |
| crew array | array | Workers with start and end times. |
{
"action": "action",
"record": "record"
} {
"work_order": "WO-1183",
"date": "2026-11-13",
"crew": [
{
"worker": "Luis",
"start": "07:00",
"end": "15:30"
},
{
"worker": "Avery",
"start": "07:00",
"end": "15:30"
}
],
"saved": true
} Your client list and profiles, and invoices made from proposals.
Clients in the navigation bar. `get` opens the client profile: summary, recent activity and the client's projects. Delete removes the client, so the agent names the client first. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/arbornote/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `copy`, `delete`. `list` and `get` only read. |
| client string | string | Client name or ID, for every action but `list` and `create`. |
| fields object | object | For `create` and `update`: the client fields as ArborNote labels them. |
{
"action": "action"
} {
"client": "Oak Street HOA",
"contact": "board@example.com",
"projects": [
"Oak Street HOA"
],
"recent_activity": "Proposal P-2417 created"
} Invoices > Create New Invoice, pick the proposal, review and add notes. Save and Email uses the template under Settings > Email Templates and reaches your customer. By default you confirm each call; you can switch that off for this tool.
MCP callarbornote_write → create_invoice
REST endpointPOST https://cotlet.dev/api/v1/arbornote/invoices
| Name | Type | Description |
|---|---|---|
| proposal string required | string | Proposal number the invoice is for. |
| notes string | string | Customer notes on the invoice. |
| save string | string | `save`, or `save_and_email` to open your invoice email template for the customer. |
{
"proposal": "proposal"
} {
"invoice": "INV-3305",
"proposal": "P-2391",
"client": "Riverside Commons",
"total": 4950,
"emailed": false
} Your signed-in ArborNote browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 28 ArborNote tools. The session cookie stays in the Cloud Browser.
The projects, proposals, work orders and invoices your ArborNote user and plan can open, and nothing more.
Your ArborNote settings and users, the API Access token, ArborNote Pay and Stripe setup, QuickBooks and HubSpot sync, and email templates.
You log in again yourself in the same Cloud Browser, with your password or Log In with Google.
Disable ArborNote for agents, reset the browser, or change your ArborNote 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 (live results).
send call. | Action | How to put it right |
|---|---|
| Client, project, tree or treatment fields | Call the same tool again with the earlier values |
| Project archived or trees deleted | Restore them with archive_projects or restore_trees; ArborNote keeps both |
| Trees moved to the wrong project | Move them back with move_trees |
| Proposal or invoice emailed | Already with your client: talk to them before you change it |
| Proposal reminder deleted | Gone for good; ArborNote cannot recover a deleted reminder |
All 23 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 5 read tools (inventory export, map links, Ask ArborNote Sales, the sales dashboard and project reports) run at once.
{
"name": "manage_gtc_proposals",
"arguments": {
"action": "create",
"project": "Oak Street HOA",
"trees": [
{
"tree": 4,
"objectives": [
{
"objective": "Removal",
"price": 1800
},
{
"objective": "Stump grind",
"price": 350
}
]
},
{
"tree": 7,
"objectives": [
{
"objective": "Crown clean",
"price": 650
}
]
}
],
"pricing": "line_item",
"separate_objectives": true,
"update_inventory": false
}
} curl -X POST https://cotlet.dev/api/v1/arbornote/gtc-proposals/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","project":"Oak Street HOA","trees":[{"tree":4,"objectives":[{"objective":"Removal","price":1800},{"objective":"Stump grind","price":350}]},{"tree":7,"objectives":[{"objective":"Crown clean","price":650}]}],"pricing":"line_item","separate_objectives":true,"update_inventory":false}' {
"proposal": "P-2417",
"project": "Oak Street HOA",
"status": "Draft",
"lines": [
{
"tree": 4,
"objective": "Removal",
"price": 1800
},
{
"tree": 4,
"objective": "Stump grind",
"price": 350
},
{
"tree": 7,
"objective": "Crown clean",
"price": 650
}
],
"total": 2800,
"sent": false
} The example prices tree 4 at $1,800 for removal and $350 for the stump grind, and tree 7 at $650 for a crown clean: $2,800. Inventory stays as it was, and the HOA sees nothing until a send call runs. A cron job or n8n flow makes the same call over REST at /api/v1/arbornote with the same key and price. Failed calls are free.
About $29 a monthfor a tree service writing about twenty estimates a month, 5,000 credits. Your ArborNote plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Site visits priced into GTC proposals | 3 × 20 | 600 |
| Approved work checked and scheduled | 3 × 16 | 480 |
| Estimator visits booked | 2 × 20 | 400 |
| Completed jobs invoiced | 2 × 16 | 320 |
| Crew hour corrections | 1 × 30 | 300 |
| Monday reminders and sales check | 3 × 4 | 120 |
| PHC proposals for spring treatments | 2 × 10 | 200 |
| Client and project lookups | 1 × 108 | 1,080 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 350 calls | 5,000 |
The smallest pack, 5,000 credits for $29, covers this month. Storm season and spring PHC rounds use more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer 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 |
|---|---|---|
| ArborNote Open API | Reads clients, projects, proposals, work orders, appointments and crew hours; writes clients, projects and proposal status. | Enterprise plan only; no proposal creation, scheduling, tree mapping or invoices. |
| Independent MCP servers | Third-party servers that put the Open API in front of ChatGPT and Claude. | Need an Enterprise API key and stop where the API stops. |
| Zapier and HubSpot integrations | Listed by ArborNote on Enterprise: triggers on new clients, projects and proposals, and a HubSpot sync. | Recipes and syncs you set up, not an agent working in ArborNote. |
| Ask ArborNote Sales | ArborNote's own AI answers questions about your GTC proposals. | Reads only; no PHC proposals, forecasts or Sales Goal. |
| By hand | Open each project, proposal and work order in ArborNote. | One screen at a time, only while you are at the desk. |
If you are on Enterprise and the Open API already covers your job, use it: it is the vendor's route. Cotlet fits when you want ChatGPT, Claude or a script to price trees, book crews and invoice in ArborNote today, on the plan you have, with nothing to host.
Cotlet is built by Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273) and in business since 2019, with founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the ArborNote tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=arbornote, turn on ArborNote under Integrations in the console and log in at https://app.arbor-note.com/ in your Cloud Browser. Then connect your AI agent and ask it about your projects or proposals. The trial needs no card.
Yes, but only on the Enterprise plan: the ArborNote Open API reads clients, projects, proposals, work orders, appointments and crew hours, and writes clients, projects and a proposal's number, status and tax (checked 16 Nov 2026). It cannot create proposals, schedule work, map trees or create invoices, and there is no ArborNote MCP server. Cotlet does not use that API: it works in your own signed-in ArborNote account.
Any plan you already have: the tools follow it. The Help Center says job requirements come with Essential and Enterprise but not Basic, and the pricing page lists multi-year plans on Enterprise. Inventory export and Clock In/Out edits need an admin user.
No. ArborNote shows due and overdue reminders only on the Proposal Reminders dashboard, with no email or push. A weekly agent run with manage_proposal_reminders can read that dashboard for you.
The user whose work the agent should do, usually the owner or an office admin. The agent sees only what that user and your plan can see, and a read-only user cannot change anything.
Only in how it is called. Both carry the same 28 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 ArborNote.
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