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

ToolWhat it doesAccess

• list_customers Customers with properties, searchable by name or address. read

  Returns customers with ID, properties, recurring service and balance.

  MCP calllawnboss_read → list_customers

  REST endpointGET https://cotlet.dev/api/v1/lawnboss/customers

  Parameters

  Parameters: list_customers

  Name	Type	Description
  query string	string	Name or address.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "customers": [
      {
        "customer_id": "LB-2210",
        "name": "Karen Mitchell",
        "property": "1840 Northwest Blvd, Columbus, OH",
        "service": "Weekly mow",
        "balance": "0.00"
      }
    ],
    "page": 1
  }

• add_customer Adds a customer with a property. write

  Creates the customer and property. Reaches no one, so it runs at once.

  MCP calllawnboss_write → add_customer

  REST endpointPOST https://cotlet.dev/api/v1/lawnboss/customers

  Parameters

  Parameters: add_customer

  Name	Type	Description
  name string required	string	Customer name.
  address string required	string	Property address.
  phone string	string	Phone.
  email string	string	Email.

  Example input

  {
    "name": "Jane Doe",
    "address": "address"
  }

  Example response

  {
    "customer_id": "LB-2288",
    "name": "Tom Becker",
    "property": "92 Arcadia Ave, Columbus, OH"
  }

ToolWhat it doesAccess

• list_jobs Jobs for a day or range, by crew or status. read

  Returns jobs with customer, property, service, crew and status.

  MCP calllawnboss_read → list_jobs

  REST endpointGET https://cotlet.dev/api/v1/lawnboss/jobs

  Parameters

  Parameters: list_jobs

  Name	Type	Description
  date_from string required	string	ISO date.
  date_to string	string	ISO date. Default: date_from.
  crew string	string	Crew name.

  Example input

  {
    "date_from": "date from"
  }

  Example response

  {
    "jobs": [
      {
        "job_id": "J-40112",
        "customer": "Karen Mitchell",
        "service": "Weekly mow",
        "crew": "Crew A",
        "date": "2026-11-10",
        "status": "Scheduled"
      }
    ]
  }

• schedule_job Schedules a one-off or recurring job. writeasks first

  Creates the job for the property, crew and date. Your settings decide whether the customer gets a notice. By default you confirm each call; you can switch that off for this tool.

  MCP calllawnboss_write → schedule_job

  REST endpointPOST https://cotlet.dev/api/v1/lawnboss/customers/{customer_id}/job/schedule

  Parameters

  Parameters: schedule_job

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  service string required	string	Service name.
  date string required	string	ISO date.
  crew string	string	Crew name.
  repeat string	string	Weekly, Every 2 weeks, Monthly or empty.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "service": "service",
    "date": "date"
  }

  Example response

  {
    "job_id": "J-40177",
    "customer": "Tom Becker",
    "service": "Leaf cleanup",
    "crew": "Crew B",
    "date": "2026-11-12",
    "repeat": null,
    "status": "Scheduled"
  }

• reschedule_job Moves a job to another day or crew. writeasks first

  Moves the job, for example off a rained-out day. Your settings decide whether the customer hears about it. By default you confirm each call; you can switch that off for this tool.

  MCP calllawnboss_write → reschedule_job

  REST endpointPOST https://cotlet.dev/api/v1/lawnboss/jobs/{job_id}/reschedule

  Parameters

  Parameters: reschedule_job

  Name	Type	Description
  job_id string required	string	Job ID from list_jobs.
  date string required	string	New ISO date.
  crew string	string	New crew. Default: unchanged.

  Example input

  {
    "job_id": "J-40112",
    "date": "2026-11-11"
  }

  Example response

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

ToolWhat it doesAccess

• create_estimate Drafts an estimate for a property. write

  Creates the estimate with line items. Sending it is a separate step, so drafting runs at once.

  MCP calllawnboss_write → create_estimate

  REST endpointPOST https://cotlet.dev/api/v1/lawnboss/customers/{customer_id}/estimates

  Parameters

  Parameters: create_estimate

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  items array required	array	Service, quantity, price.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "items": "items"
  }

  Example response

  {
    "estimate_id": "E-1902",
    "customer": "Tom Becker",
    "total": "325.00",
    "status": "Draft"
  }

• send_invoice Invoices completed jobs and sends the payment link. writeasks first

  Creates the invoice for the customer's completed jobs and sends it, the way LawnBoss does. By default you confirm each call; you can switch that off for this tool.

  MCP calllawnboss_write → send_invoice

  REST endpointPOST https://cotlet.dev/api/v1/lawnboss/customers/{customer_id}/invoices

  Parameters

  Parameters: send_invoice

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  job_ids array	array	Jobs to bill. Default: all completed and unbilled.

  Example input

  {
    "customer_id": "customer_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-7731",
    "customer": "Karen Mitchell",
    "total": "180.00",
    "status": "Sent"
  }

• list_unpaid_invoices Invoices with a balance, oldest first. read

  Returns unpaid invoices with customer, balance and days since sent.

  MCP calllawnboss_read → list_unpaid_invoices

  REST endpointGET https://cotlet.dev/api/v1/lawnboss/unpaid-invoices

  Parameters

  Parameters: list_unpaid_invoices

  Name	Type	Description
  min_days integer	integer	Only invoices sent at least this many days ago.

  Example response

  {
    "invoices": [
      {
        "invoice_id": "INV-7604",
        "customer": "Linda Alvarez",
        "balance": "240.00",
        "days": 26
      }
    ]
  }