[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# LawnBoss MCP server: Let your AI agent run the LawnBoss office.

> LawnBoss has no MCP server, no ChatGPT or Claude app, no public API and no Zapier app; it connects only to QuickBooks and Stripe (checked 9 Nov 2026). Cotlet runs 8 LawnBoss tools hosted, over MCP for agents and REST for scripts, in your own LawnBoss login.

Your AI agent moves rain days, books recurring service, drafts estimates and invoices the week. Sign in to LawnBoss once in your own Cloud Browser. No API, no Zapier.

- Free 7-day trial, no card
- Unofficial, not affiliated with LawnBoss
- Page: https://cotlet.dev/integrations/lawnboss-api-mcp-server

## What can your AI agent do in LawnBoss?

- Move rained-out days
- Book recurring service
- Draft estimates
- Invoice the week
- Chase unpaid invoices
- Add customers and properties

## Does LawnBoss have an MCP server or an API?

- LawnBoss has no API, developer or webhook page.
- LawnBoss has no Zapier app.
- LawnBoss has no connector in the ChatGPT apps directory or in Claude.

| What you need | LawnBoss API | By hand | Cotlet |
|---|---|---|---|
| Schedule and move jobs | No API | Yes, one by one | Yes, after your OK |
| Estimates | No API | Yes, one by one | Yes |
| Invoices and what is unpaid | No API | Yes | Yes, after your OK |
| Ask in ChatGPT or Claude | No | No | Yes |
| Zapier app | None | None | Not needed |

Checked 8 Nov 2026. Sources: [LawnBoss features](https://lawnboss.app/free-lawn-care-software), [LawnBoss llms.txt](https://lawnboss.app/llms.txt), [LawnBoss home](https://lawnboss.app/)

## How does the LawnBoss MCP server work?

1. **Sign in to LawnBoss.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the busywork.** It drafts the work, you OK what customers get.

We never keep your LawnBoss password, and no job, move or invoice reaches a customer until you approve it.

## How to connect LawnBoss to your AI agent

1. **Sign in to LawnBoss in a Cloud Browser.** Create a Cotlet account, open LawnBoss in its Cloud Browser, sign in with your LawnBoss login and press Enable for agents.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. **Let the agent in.** Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

LawnBoss shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned LawnBoss on after connecting? Refresh the connector and the 8 tools appear.

Claude:

```
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"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: lawnboss_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: lawnboss_write
```

## All 8 LawnBoss MCP tools

### Customers

Search by name and address. New customers reach no one, so they run at once.

- **List customers** (`list_customers`, read): Customers with properties, searchable by name or address.
- **Add customer** (`add_customer`, write): Adds a customer with a property.

### Jobs

One-off and recurring jobs per crew. New jobs and moves wait for your OK.

- **List jobs** (`list_jobs`, read): Jobs for a day or range, by crew or status.
- **Schedule job** (`schedule_job`, write, asks first): Schedules a one-off or recurring job.
- **Reschedule job** (`reschedule_job`, write, asks first): Moves a job to another day or crew.

### Estimates and invoices

Draft estimates run at once. Sending an invoice waits for your OK.

- **Create estimate** (`create_estimate`, write): Drafts an estimate for a property.
- **Send invoice** (`send_invoice`, write, asks first): Invoices completed jobs and sends the payment link.
- **List unpaid invoices** (`list_unpaid_invoices`, read): Invoices with a balance, oldest first.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/lawnboss-api-mcp-server#tools

## Who can see my LawnBoss session, and how do I revoke it?

- **What we store.** Your signed-in LawnBoss profile, AES-256-GCM encrypted, in Finland. No password.
- **What your agent gets.** The 8 LawnBoss tools, never the session cookie.
- **What the session sees.** What your login sees: customers, jobs, estimates, invoices.
- **What no tool touches.** Payments, payroll and time clock, pesticide records, fleet, deletes.
- **If LawnBoss signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** Disable for agents, reset the browser, or change your LawnBoss password.

Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)).

## What happens when LawnBoss changes?

- **12 h** between tests of the LawnBoss reads
- **24 h** between tests of sends a customer would notice
- **$0** for a call to a LawnBoss tool paused for repair

When LawnBoss moves a button or renames a screen, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Reads Monday's jobs.** For the crew you name.
2. **Checks Tuesday.** Against the same crew's day.
3. **Proposes the moves.** And lists what does not fit.
4. **Waits, then moves.** The batch shows up in your Cotlet console first.

| Action | Undo |
|---|---|
| Add a customer or draft an estimate | Yes, edit or delete it in LawnBoss |
| Schedule or move a job | Yes, move it back; a notice already sent stays sent |
| Send an invoice | No, the customer has it; void it in LawnBoss |

3 of 8 tools ask first: schedule_job, reschedule_job, send_invoice. New customers and draft estimates reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.

MCP call:

```
{
  "name": "reschedule_job",
  "arguments": {
    "job_id": "J-40112",
    "date": "2026-11-11"
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/lawnboss/jobs/J-40112/reschedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-11-11"}'
```

Response:

```
{
  "job_id": "J-40112",
  "date": "2026-11-11",
  "crew": "Crew A",
  "status": "Scheduled"
}
```

A cron job or n8n flow can call the same tools over REST at `/api/v1/lawnboss` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.

## How much does the LawnBoss MCP server cost?

**About $29 a month** for a lawn care company with 2 crews, 4,940 credits. Your LawnBoss plan stays as it is.

| Job | Calls | Credits |
|---|---|---|
| Rain day moved | 20 × 3 | 600 |
| Estimate drafted | 2 × 20 | 400 |
| Job scheduled | 2 × 40 | 800 |
| Weekly invoicing | 40 × 4 | 1,600 |
| Unpaid invoices, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 4,940 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- LawnBoss itself is free

LawnBoss publishes no job counts, so the month is our example. Dollars at the $29 pack rate.

## LawnBoss MCP server on GitHub, Zapier or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| QuickBooks sync | Invoices and payments between LawnBoss and QuickBooks. | Accounting only; no jobs or questions. |
| LawnBoss AI pricing | LawnBoss's own estimates from satellite imagery. | Works inside LawnBoss; not your ChatGPT or Claude. |
| By hand | Every screen of LawnBoss, one job at a time. | Your evenings. |

LawnBoss has no API or Zapier app, so there is nothing to connect a script to. To schedule, move rain days and invoice from ChatGPT or Claude this week, Cotlet works in the LawnBoss account you already have.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the LawnBoss tools go to contact@cotlet.dev.

## LawnBoss MCP server: questions

### How do I get access?

Sign up free at https://cotlet.dev, open LawnBoss under Integrations in the console and sign in to LawnBoss in its Cloud Browser. The trial starts with your first app and asks for no card.

### How do I connect LawnBoss to ChatGPT or Claude?

Sign up at cotlet.dev, log in to LawnBoss once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your LawnBoss account through Cotlet, in their phone apps too.

### What can ChatGPT do in LawnBoss?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in LawnBoss: move a rained-out day; quote a new property; book recurring service. You ask in plain words, and anything that reaches other people waits for your OK first.

### Is there an official ChatGPT or Claude app for LawnBoss?

No. LawnBoss has no ChatGPT or Claude connector of its own and LawnBoss has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

### Can ChatGPT schedule jobs in LawnBoss?

Yes, with Cotlet. ChatGPT schedules one-off or recurring jobs for the crew and date you name, after your OK.

### Can ChatGPT reschedule a rain day in LawnBoss?

Yes, with Cotlet. ChatGPT reads the day's jobs for a crew and moves them to the day you name, after your OK, and lists what does not fit.

### Can ChatGPT send invoices in LawnBoss?

Yes, with Cotlet. ChatGPT invoices customers for completed jobs and sends the payment link after your OK, and lists what is unpaid.

### Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 8 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.

### Is Cotlet affiliated with LawnBoss?

No. Cotlet is independent and not affiliated with LawnBoss.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
