Local services & SaaS
LawnBoss
Customers, jobs, estimates and invoices in LawnBoss, the free lawn care CRM.
8 endpoints
Lawn Service IQ publishes no public API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted Lawn Service IQ MCP server with 6 tools that ChatGPT and Claude use in your own Lawn Service IQ Cloud account. Moving a day, changing routes, sending estimates and emailing proof wait for your OK.
6 tools Read and write
Lawn Service IQ publishes no public API, no developer documentation and no API keys. No Lawn Service IQ MCP server and no official ChatGPT or Claude connector was found.
| What you need | Lawn Service IQ API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to run dispatch | No API or MCP server | Copy and paste | Hosted MCP server |
| Rain days, routes, estimates, proof | Not available | Screen by screen | 6 tools, writes after your OK |
| A four o'clock check from n8n | Not available | When you look at the board | REST, same key |
Checked 15 Nov 2026. Sources: Lawn Service IQ home and pricing · Lawn Service IQ FAQ · Lawn Service IQ sign-in
Once, in a browser we host for you.
One address in its settings.
Rain days, routes, proof requests.
Your agent works in your own signed-in Cloud Browser. Anything your crews or customers would see waits for your OK. Who can see your session
Sign in to Lawn Service IQ in a Cloud Browser. Open lawnserviceiq.com/login in your Cotlet Cloud Browser and sign in with your Lawn Service IQ Cloud office login.
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.
Lawn Service IQ sits behind the shared address https://cotlet.dev/mcp/v1 with the other apps you turn on, so one connector reaches them all. Added Lawn Service IQ later? Refresh the connector for its 6 tools.
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: lawn_service_iq_read One tool per Lawn Service IQ feature, named after the screens in its FAQ. Write tools take an `action`; the reading actions run at once and the rest ask first.
Crew progress, the Map view's dollars per mile, drive order and Move day. The trucks see the same schedule.
Every stop a crew completes in the crew app flows into billing, payroll hours and the customer record, and the dispatch board shows each crew's last-seen location during the workday. This tool reads that state. Read only.
MCP calllawn_service_iq_read → view_crew_work
REST endpointGET https://cotlet.dev/api/v1/lawn-service-iq/crew-works/view
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
| crew string | string | One crew. Leave empty for every crew. |
{
"date": "2026-11-16",
"crews": [
{
"crew": "Crew North",
"stops": 14,
"done": 9,
"last_seen": "13:42"
},
{
"crew": "Crew South",
"stops": 12,
"done": 12,
"last_seen": "14:05"
}
]
} `list` returns what the dispatch Map view shows per crew: stops, stops per mile and dollars per mile. Sort by drive order puts a crew's stops shortest drive first. The trucks see the same schedule, so a change waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calllawn_service_iq_write → build_crew_routes
REST endpointPOST https://cotlet.dev/api/v1/lawn-service-iq/crew-routes/build
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `move_stop`, `sort_drive_order`. `list` only reads. |
| date string | string | ISO date. Defaults to today. |
| stop string | string | For `move_stop`: the client or address of the stop. |
| to_crew string | string | For `move_stop`: the crew that takes it. |
| crew string | string | For `sort_drive_order`: the crew whose stops to reorder. |
{
"action": "action"
} {
"date": "2026-11-17",
"crews": [
{
"crew": "Crew North",
"stops": 14,
"stops_per_mile": 0.9,
"dollars_per_mile": 4.25
},
{
"crew": "Crew South",
"stops": 12,
"stops_per_mile": 0.7,
"dollars_per_mile": 3.8
}
]
} This is Dispatch, Move day: one call moves every unworked stop of the day, can shift the customers' future visits too, and can email every affected customer. The board also shows a rain-risk banner before the day arrives. Moving a day reaches crews and customers, so the agent names the dates and the number of stops first. By default you confirm each call; you can switch that off for this tool.
MCP calllawn_service_iq_write → move_dispatch_day
REST endpointPOST https://cotlet.dev/api/v1/lawn-service-iq/dispatch-day/move
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `forecast`, `move_day`. `forecast` only reads. |
| date string | string | ISO date of the day to move, for `move_day`. |
| to_date string | string | ISO date to move the unworked stops to. |
| shift_future_visits boolean | boolean | Also shift the customers' later visits. |
| email_customers boolean | boolean | Email every affected customer about the new date. |
{
"action": "move_day",
"date": "2026-11-18",
"to_date": "2026-11-19",
"shift_future_visits": true,
"email_customers": true
} {
"date": "2026-11-18",
"to_date": "2026-11-19",
"stops_moved": 26,
"future_visits_shifted": true,
"customers_emailed": 24
} Measure a lot on the satellite map, then let your rate tiers price the estimate the customer signs in the portal.
The saved square footage feeds the rate matrix on the Services screen, so the next estimate prices itself, for example by lot-size band. The agent shows you the area before it saves. By default you confirm each call; you can switch that off for this tool.
MCP calllawn_service_iq_write → measure_lot
REST endpointPOST https://cotlet.dev/api/v1/lawn-service-iq/lot/measure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `measure`. `get` only reads. |
| client string required | string | Client name or property address. |
| area_sq_ft number | number | For `measure`: the lawn area to save, when you already know it. Otherwise the agent traces the lawn on the satellite map from the client page, Measure lot. |
{
"action": "action",
"client": "client"
} {
"client": "Example Homeowner",
"address": "42 Example Lane",
"area_sq_ft": 7800,
"rate_tier": "5-10k sq ft",
"saved": true
} Prices fill in from your rate tiers and the measured lot. A saved estimate goes to the customer's portal, where they sign and approve it online, so the agent shows the lines and total first. By default you confirm each call; you can switch that off for this tool.
MCP calllawn_service_iq_write → create_estimate
REST endpointPOST https://cotlet.dev/api/v1/lawn-service-iq/estimates
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only reads. |
| client string | string | For `create`: client name. |
| services array | array | For `create`: services from your Services screen, for example weekly mowing. |
{
"action": "action"
} {
"client": "Example Homeowner",
"estimate": "EST-1187",
"lines": [
{
"service": "Weekly mowing",
"price": 55
},
{
"service": "Spring cleanup",
"price": 180
}
],
"status": "sent to portal",
"saved": true
} Timestamps, GPS, site weather and photos of a completed stop, as a branded customer link.
Your signed-in Lawn Service IQ browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 6 Lawn Service IQ tools. The session cookie stays in the Cloud Browser.
The office screens your login opens: dispatch, clients, estimates and the records crews send in.
Payments and saved cards, QuickBooks, payroll, employee logins, the yard geofence and other Settings.
You sign in again yourself, in the same Cloud Browser.
Disable Lawn Service IQ for agents, reset the browser, or change your office password.
Cotlet never sees or stores your password. You type it yourself, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the Lawn Service IQ server when Lawn Service IQ changes its screens, so your agent keeps working without a change on your side.
Lawn and snow run in one Lawn Service IQ system, so the same tools serve the mowing season and the storm season.
If Lawn Service IQ signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Stop on the wrong crew, wrong order | Call build_crew_routes again; tell the crew if they already left |
| Lot area saved wrong | Measure again with measure_lot before the next estimate |
| Day moved, emails sent | Move it back; the customers already have the first email |
| Estimate or proof sent | Already with the customer: follow up with them directly |
All 5 write tools ask first: by default you confirm each call, and you can switch that off per tool. view_crew_work runs at once, and so do the reading actions of the other tools.
{
"name": "move_dispatch_day",
"arguments": {
"action": "move_day",
"date": "2026-11-18",
"to_date": "2026-11-19",
"shift_future_visits": true,
"email_customers": true
}
} curl -X POST https://cotlet.dev/api/v1/lawn-service-iq/dispatch-day/move \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"move_day","date":"2026-11-18","to_date":"2026-11-19","shift_future_visits":true,"email_customers":true}' {
"date": "2026-11-18",
"to_date": "2026-11-19",
"stops_moved": 26,
"future_visits_shifted": true,
"customers_emailed": 24
} The example moves 26 unworked stops from 18 to 19 November and emails the 24 customers with an address on file. A script or n8n flow can make the same call over REST at /api/v1/lawn-service-iq with the same key and price, in JSON. Failed calls are free.
About $18 a monthfor three crews in mowing season, 3,060 credits. Your Lawn Service IQ plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Tomorrow's routes, moves and drive order | 3 × 26 | 780 |
| Four o'clock check on unfinished stops | 1 × 26 | 260 |
| Lot measured and estimate drafted | 2 × 15 | 300 |
| Proof of service for a customer call | 2 × 8 | 160 |
| Rained-out days moved | 2 × 3 | 60 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 156 calls | 3,060 |
The smallest pack, 5,000 credits for $29, covers this month. A wet month with more moved days adds a few calls.
Credit packs are one-time purchases, not a subscription. The month above is an example 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 |
|---|---|---|
| Office screens | Dispatch, Move day, Map view, estimates and proof, in the browser. | Your dispatcher clicks through each one. |
| Print route sheet | Every crew's stops in order, with addresses and notes, on paper. | A printout; it does not change when the day does. |
| QuickBooks Online link | Connects Lawn Service IQ to your accounting. | Accounting only, not dispatch or estimates. |
| CSV import | Brings clients, properties and price lists in. | One way in, at setup. |
If Lawn Service IQ publishes an API that covers your job, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script working in Lawn Service IQ Cloud today, from your own sign-in, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Lawn Service IQ tools.
Sign up free at https://cotlet.dev/signup?app=lawn-service-iq, turn on Lawn Service IQ under Integrations in the console and sign in at https://lawnserviceiq.com/login in your Cloud Browser. Then connect your AI agent and ask it for tomorrow's routes. The trial needs no card.
Lawn Service IQ publishes no public API, developer documentation or API keys (checked 15 Nov 2026). No Lawn Service IQ MCP server and no official ChatGPT or Claude connector was found; QuickBooks Online is its built-in accounting connection. Cotlet does not need one: it works in your own signed-in Lawn Service IQ account.
No. Lawn Service IQ Standalone is a Windows app that keeps your data on your office computer, so a Cloud Browser cannot reach it. The tools work with Lawn Service IQ Cloud, which you sign in to from any device ($99 a month or $990 a year, checked 15 Nov 2026).
The agent signs in as the office, not as a crew member: Lawn Service IQ crew logins open only the field app. What crews record there, stops done, photos and times, reaches the office screens, and that is what the tools read.
Lawn Service IQ has a public office demo with a pretend company, Evergreen Lawn & Snow Care, loaded with routes, customers and invoices. It is the vendor's demo, so try the screens there; connect Cotlet to your own Cloud account for real work.
Only in how it is called. Both carry the same 6 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 Lawn Service IQ.
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