[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)

# EZ Lawn Biller API and MCP server: Let your AI agent move the rained-out stops.

> No publicly documented EZ Lawn Biller API was found: ezlawnbiller.com/api, /developers and /docs returned 404 on 11 Nov 2026, and its FAQ names QuickBooks as its integration. Its own crew app and customer portal run inside EZ Lawn Biller. No official EZ Lawn Biller MCP server was found.

EZ Lawn Biller has no publicly documented API that we could find, and no official EZ Lawn Biller MCP server was found (checked 11 Nov 2026). Cotlet runs a hosted EZ Lawn Biller MCP server with 277 tools that ChatGPT and Claude use in your own EZ Lawn Biller account to plan routes, close visits and chase past-due statements.

- Free 7-day trial, no card
- Unofficial, not affiliated with EZ Lawn Biller
- Page: https://cotlet.dev/integrations/ez-lawn-biller-api-mcp-server

## What can your AI agent do in EZ Lawn Biller?

- Move rained-out stops in a schedule draft
- Mark the crew's mowing visits completed
- Record the week's check payments
- Email past-due statements to customers who owe
- Send an estimate to a new lawn prospect
- Text customers about a weather delay

## Does EZ Lawn Biller have an MCP server or an API?

- No public EZ Lawn Biller API documentation or key page was found on 11 Nov 2026.
- QuickBooks sync keeps your books in step; it does not run routes or notices.
- The crew app and customer portal are part of EZ Lawn Biller itself.

| What you need | EZ Lawn Biller API | QuickBooks sync | Cotlet |
|---|---|---|---|
| Move rained-out stops | None found | Accounting only | In your account |
| Record a check payment | None found | Syncs to QuickBooks | In your account |
| Send past-due notices | None found | Accounting only | In your account |

Checked 11 Nov 2026. Sources: [EZ Lawn Biller FAQ](https://ezlawnbiller.com/faq/), [EZ Lawn Biller features](https://ezlawnbiller.com/features/), [Manual: billing and payments](https://ezlawnbiller.com/manual/billing-and-payments/), [Manual: scheduling and routes](https://ezlawnbiller.com/manual/scheduling-and-routes/), [Manual: QuickBooks](https://ezlawnbiller.com/manual/quickbooks/)

## How does the EZ Lawn Biller MCP server work?

1. **Sign in to EZ Lawn Biller.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the busywork.** Ask it to move Tuesday's rained-out stops to Thursday.

Your agent works in your own EZ Lawn Biller customers, routes and statements, within your EZ Lawn Biller role.

## How to connect EZ Lawn Biller to your AI agent

1. **Sign in to EZ Lawn Biller in a Cloud Browser.** Open EZ Lawn Biller in your Cotlet Cloud Browser and sign in at landlord.app.ezlawnbiller.com with your own EZ Lawn Biller login.
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.

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

ChatGPT:

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

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

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: ez_lawn_biller_read
```

## All 277 EZ Lawn Biller MCP tools

### Getting Started

Dashboard, Today's Schedule, Customer search and more.

- **Dashboard** (`read_dashboard`, read): Inspect location, recurring-charge, visit, and income totals.
- **Today's Schedule** (`read_today_schedule`, read): Inspect today's stops from the dashboard.
- **Customer search** (`search_customers`, read): Find customers from the dashboard.
- **Setup Wizard** (`run_setup_wizard`, write, asks first): Configure company, payments, portal, reports, email, and technician.

### Company Settings

Company settings, Brand colour, Statement contact lines and more.

- **Company settings** (`read_company_settings`, read): Inspect permission-allowed configuration tabs.
- **Brand colour** (`change_brand_colour`, write): Change branding through the setup wizard.
- **Statement contact lines** (`configure_statement_header`, write, asks first): Choose printed address, phone, and email.
- **Held billing reminders** (`configure_held_billing_reminders`, write, asks first): Set reminder enablement and interval.
- **Stripe connection** (`configure_stripe`, write, asks first): Turn card payments through Stripe on or off. The Stripe secret key itself is entered by you.
- **Gateway Order** (`set_gateway_order`, write, asks first): Set autopay gateway preference.
- **Bank transfers** (`configure_ach`, write): Set ACH availability and the ACH fee. The webhook secret is entered by you.
- **Late Fees** (`configure_late_fees`, write, asks first): Configure company late-fee rules, thresholds, timing, autopay treatment, and notices; individual customer exemptions are managed separately.
- **Portal settings** (`configure_customer_portal`, write, asks first): Toggle portal, saved-card management, and statement login links.
- **Email settings** (`configure_smtp`, write, asks first): Set SMTP, sender identity, and footer.
- **SMS settings** (`configure_twilio`, write, asks first): Set the Twilio sending number for texts. The Twilio credentials themselves are entered by you.
- **Visit Report Settings** (`configure_visit_reports`, write, asks first): Set delivery, content, photo limits, footer, and opt-out.
- **Preview** (`preview_visit_report_email`, read): Preview unsaved report choices without sending.
- **Open web page** (`open_visit_report_web_page`, read): Inspect report using saved choices.
- **Manage EZ Lawn Biller Plan** (`read_plan_usage`, read): Inspect current-month location count and projected usage.
- **Manual help** (`read_manual_help`, read): Search manual and open interactive workflow documentation.
- **Email support** (`contact_support_from_app`, write, asks first): Contact support by email through the app; the exact in-app control is unspecified.
- **Configure card paypal processing fee** (`configure_card_paypal_processing_fee`, write, asks first): Set the processing fee charged on card and PayPal payments in Settings > Payments, separate from ACH fees.

### Your Team

Manage Staff, Add Technician, New Staff and more.

- **Manage Staff** (`list_staff`, read): Inspect users and assigned roles.
- **Add Technician** (`add_technician`, write, asks first): Create technician and send setup instructions.
- **New Staff** (`create_office_staff`, write, asks first): Create an office user with a role. You set and share the initial password.
- **Remove staff** (`remove_office_staff`, write, asks first): Revoke login while retaining history; restrictions apply.
- **Roles & Permissions** (`read_roles_permissions`, read): Inspect role access.
- **Custom role** (`create_custom_role`, write, asks first): Build a permission combination.
- **Staff role** (`assign_staff_role`, write, asks first): Assign or restore user roles.
- **Permission controls** (`edit_role_permissions`, write, asks first): Set viewing, making, settings, and report access.
- **Technician profile** (`edit_technician_profile`, write): Set home base, qualifications, capacities, and colour.
- **Work Schedule** (`edit_technician_work_schedule`, write, asks first): Set weekday hours, breaks, and break flexibility.
- **Staff impersonation** (`impersonate_staff`, write, asks first): Enter an authorized staff member's perspective.
- **Customer impersonation** (`impersonate_customer`, write, asks first): Enter a customer's portal perspective.
- **Stop Impersonating** (`stop_impersonating`, write): Return to your own account.
- **Geographic service areas** (`set_technician_service_areas`, write, asks first): Assign zones or ZIP codes.
- **Technician credentials** (`edit_technician_credentials`, write): Manage technician-profile certifications, qualifications, and hire-date information, not login credentials.
- **Activity log** (`read_activity_log`, read): Review user, payment, schedule, and customer-change audit history.

### Customers

Customer list, Details, New Customer and more.

- **Customer list** (`list_customers`, read): Find customers, including paused and canceled records.
- **Details** (`read_customer_details`, read): Inspect contacts, locations, notes, and preferences.
- **New Customer** (`create_customer`, write, asks first): Create customer and first recurring service.
- **Edit customer** (`edit_customer`, write): Change customer information and secondary email.
- **Remove customer** (`remove_customer`, write, asks first): Remove customers with the required permission.
- **Add Location** (`add_customer_location`, write): Add geocoded address and service instructions.
- **Service Windows** (`set_location_service_windows`, write, asks first): Set allowed weekday service times.
- **Billing Address** (`set_billing_address`, write): Designate the billing location.
- **Phone numbers** (`manage_customer_phone_numbers`, write): Add numbers; choose primary and SMS destination.
- **CC emails** (`manage_cc_emails`, write): Add copy recipients, labels, types, and enablement.
- **Customer notes** (`add_customer_note`, write): Record staff-only account notes.
- **Pin notes** (`pin_customer_note`, write): Keep important notes above others.
- **Customer Settings** (`read_customer_settings_table`, read): Search, filter, sort, and inspect delivery settings.
- **Customer delivery settings** (`change_customer_delivery_settings`, write): Change individual statement and report channel preferences.
- **Group settings** (`bulk_change_customer_settings`, write, asks first): Administrators update selected customers; email resubscription restricted.
- **Undo** (`undo_customer_settings_change`, write): Reverse the most recent settings-table change.
- **Cancel customer** (`cancel_customer`, write, asks first): Stop services without deleting history.
- **Reactivate customer** (`reactivate_customer`, write, asks first): Bring a canceled customer back.
- **Mark on-demand** (`mark_customer_on_demand`, write, asks first): Move customer to one-off work.
- **Add visit** (`add_service_visit`, write, asks first): Add another visit to an existing repeating plan.
- **Edit visit** (`edit_service_visit`, write, asks first): Edit one visit's date, technician, or location; bulk edit technician or move visits within the same week, subject to collision checks.
- **Cancel this visit** (`cancel_service_visit`, write, asks first): Skip a visit without nightly regeneration.
- **Delete visits** (`delete_service_visits`, write, asks first): Remove bookings singly or in bulk; recurring visits may regenerate.
- **Services** (`read_customer_service_history`, read): Search, filter, sort, and open visits and recorded data.

### Service Catalog

Service catalog, New recurring item, Edit recurring item and more.

- **Service catalog** (`read_service_catalog`, read): Inspect repeating items, one-time services, and checklists.
- **New recurring item** (`create_recurring_billing_item`, write): Define price, tax, billing, visits, duration, and proration.
- **Edit recurring item** (`edit_recurring_billing_item`, write): Change template defaults; existing visit frequency is preserved.
- **Add service type** (`create_service_type`, write): Create category inside the service form.
- **Edit service type** (`edit_service_type`, write): Change category duration and calendar colour.
- **Delete service type** (`delete_service_type`, write, asks first): Delete only when no services use it.
- **Service checklist** (`configure_service_checklist`, write): Define questions and required or optional answers.
- **Restore default** (`restore_default_checklist`, write): Restore the job-specific starter checklist.
- **Inventory checklist** (`configure_inventory_checklist`, write): Set normal supplies and deduction quantities.
- **Add Item** (`add_subscription_item`, write, asks first): Add individually priced and scheduled billing lines.
- **New one-time service** (`create_one_time_service`, write): Create reusable job with price and checklist.

### One-Off Jobs & On-Demand Customers

Edit one-time service, Delete one-time service, Add starter services and more.

- **Edit one-time service** (`edit_one_time_service`, write): Change starter-job name, price, and checklist.
- **Delete one-time service** (`delete_one_time_service`, write, asks first): Remove unwanted starter jobs.
- **Add starter services** (`restore_starter_services`, write): Restore missing starter jobs without replacing existing ones.
- **Mark completed** (`mark_visit_completed`, write, asks first): Mark a visit complete from the office; post any charge required by its billing arrangement, without duplicating already-posted or estimate-carried charges.
- **New On-Demand Customer** (`create_on_demand_customer`, write, asks first): Create customer, sell job, and book technician/date together.
- **Sell a service** (`sell_one_off_job`, write, asks first): Book an existing customer's one-time job.
- **One-off billing** (`set_one_off_billing_moment`, write, asks first): Bill on completion or post immediately with chosen date.
- **Use existing customer** (`reuse_existing_customer`, write): Resolve duplicate email by attaching job to existing customer.
- **Convert to subscriber** (`convert_to_subscriber`, write, asks first): Start recurring service; confirm cancellation of conflicting bookings.

### Subscriptions

Recurring Billing, Recurring service, Edit recurring billing and more.

- **Recurring Billing** (`read_subscriptions`, read): Inspect subscription items, lifecycle, dates, and frequencies.
- **Recurring service** (`create_subscription`, write, asks first): Create location-linked service with billing and optional autopay.
- **Edit recurring billing** (`edit_subscription_billing`, write, asks first): Change payment method and location.
- **Edit billing item** (`edit_subscription_item`, write, asks first): Change customer-specific price, frequency, and charge dates.
- **Change visit days** (`change_visit_days`, write, asks first): Set frequency, visit days, and fixed/flexible policy.
- **Pause** (`pause_subscription`, write, asks first): Pause services, optionally with automatic resume.
- **Scheduled Pause** (`schedule_subscription_pause`, write, asks first): Arrange a future pause.
- **Resume** (`resume_subscription`, write, asks first): Restart visits from the chosen first date.
- **Cancel** (`cancel_subscription`, write, asks first): Terminate with reason and effective date.
- **Reactivate** (`reactivate_subscription`, write, asks first): Restart canceled service with dates and technician.
- **Reactivate stopped line** (`reactivate_subscription_line`, write, asks first): Restart an individually stopped billing line.
- **Proration** (`configure_proration`, write, asks first): Choose full, daily, weekly, or deferred first-period billing.
- **Auto-Pause** (`configure_auto_pause`, write, asks first): Set overdue grace, minimum balance, and notification.
- **Auto-Resume** (`configure_auto_resume`, write, asks first): Set recovery threshold, delay, and notification.
- **Correction preview** (`preview_subscription_correction`, read): Inspect proposed visits, statements, charges, and balance.
- **Apply correction** (`apply_subscription_correction`, write, asks first): Rewrite eligible recent-sale starts and first charges.

### Billing & Payments

Undo cancellation, Billing History, Issue Charge and more.

- **Undo cancellation** (`undo_subscription_cancellation`, write, asks first): Reverse pending cancellation and restore service dates.
- **Billing History** (`read_customer_ledger`, read): Inspect charges, payments, credits, fees, and running balance.
- **Issue Charge** (`issue_manual_charge`, write, asks first): Post categorized amount, description, date, and optional tax.
- **Record Payment** (`record_offline_payment`, write): Record amount, method, reference, and date.
- **Issue Credit** (`issue_credit`, write, asks first): Post adjustment with reason and description.
- **Refund** (`refund_payment`, write, asks first): Process full/partial refund through original gateway.
- **Change charge date** (`change_charge_date`, write, asks first): Edit future-dated charge timing.
- **Statements** (`read_statements`, read): Inspect open/closed periods and current/next-month documents.
- **Statement PDF** (`download_statement_pdf`, read): Download a customer's statement.
- **Send statement** (`send_customer_statement`, write, asks first): Email or text one customer's selected statement.
- **Waive this late fee** (`waive_late_fee`, write, asks first): Post equal credit while retaining the original fee.
- **Customer late fees** (`set_customer_late_fee_exemption`, write, asks first): Enable or exempt automatic fees for one customer.
- **Default autopay method** (`set_default_autopay_method`, write, asks first): Choose the saved method for authorized automatic payments.
- **Payment retries** (`configure_autopay_retries`, write, asks first): Configure autopay retry scheduling and failure handling; configure subscription auto-pause separately in company settings.
- **Confirmation thresholds** (`configure_large_adjustment_confirmation`, write, asks first): Set confirmation threshold for credits/refunds.
- **Offer PayPal automatic payments again** (`reoffer_paypal_automatic_payments`, write, asks first): Restore offering after PayPal approves Reference Transactions.

### Scheduling & Routes

Schedule, Route map, Create a Draft and more.

- **Schedule** (`read_schedule`, read): Navigate weeks/months and inspect stops, days, and Overflow.
- **Route map** (`read_route_map`, read): Inspect pins, technician locations, and route lines.
- **Create a Draft** (`create_schedule_draft`, write): Make a private planning copy.
- **Return to LIVE** (`discard_schedule_draft`, write): Throw away unpublished planning changes.
- **Apply Draft to LIVE** (`publish_schedule_draft`, write, asks first): Publish assignments to technician phones.
- **Move stop** (`move_route_stop`, write, asks first): Change technician, day, or stop order.
- **Force anyway** (`force_route_move`, write, asks first): Override a warned scheduling constraint.
- **Future-week changes** (`apply_stop_change_to_future_weeks`, write, asks first): Repeat a stop reassignment in future weeks.
- **Route Optimizer** (`run_route_optimizer`, write): Arrange draft using concentration, workload, balance, or contiguous modes.
- **Optimize Order** (`optimize_stop_order`, write, asks first): Reorder daily driving without changing assignments.
- **Apply To All Weeks** (`optimize_all_weeks`, write, asks first): Extend optimization across the term.
- **Copy to Future Weeks** (`copy_routes_to_future_weeks`, write, asks first): Copy assignments and exact driving order forward.
- **Lock stop** (`lock_route_stop`, write): Protect a stop from optimizer changes.
- **Customize Routes** (`read_customize_routes`, read): Filter and sort the week's unfinished stops.
- **Save route changes** (`save_customize_routes`, write, asks first): Bulk save reassignments and recalculate affected driving order.
- **Open PDF** (`open_route_pdf`, read): Preview grouped LIVE routes with configurable stop details.
- **Download PDF** (`download_route_pdf`, read): Save filtered weekly routes or technician/day route sheets.
- **Day assignment drawer** (`read_day_assignment_drawer`, read): Inspect counts, driving time, customers, status, and order.
- **Reorder stops** (`reorder_day_stops`, write, asks first): Drag stops within the day drawer.

### Estimates

Estimates list, Estimate details, New estimate and more.

- **Estimates list** (`list_estimates`, read): Search, sort, filter statuses, customers, dates, and summary groups.
- **Estimate details** (`read_estimate`, read): Inspect lines, billing, jobs, timeline, delivery, and approval audit.
- **New estimate** (`create_estimate_draft`, write): Set customer, location, ordered lines, tax, terms, and collection.
- **Edit estimate** (`edit_estimate_draft`, write): Change an unsent estimate.
- **Delete draft** (`delete_estimate_draft`, write, asks first): Remove unsent estimate without reusing its number.
- **Create customer** (`create_customer_from_estimate`, write): Add customer/location inside builder without booking work.
- **Preview as customer** (`preview_estimate_as_customer`, read): Open read-only customer view.
- **Download PDF** (`download_estimate_pdf`, read): Retrieve estimate when its link works.
- **Send / Resend** (`send_estimate`, write, asks first): Email/text chosen recipients; new sends replace old links.
- **Resend selected** (`bulk_resend_estimates`, write, asks first): Resend selected sent/viewed estimates using default channels.
- **Generate & copy link** (`generate_estimate_link`, write, asks first): Expose approval link and mark estimate sent without messaging.
- **Extend validity** (`extend_estimate_validity`, write, asks first): Change expiry; reminder eligibility can restart.
- **Revoke link** (`revoke_estimate_link`, write, asks first): Stop approval link and associated reminders.
- **Void** (`void_estimate`, write, asks first): Permanently cancel an eligible estimate.
- **Record approval** (`record_estimate_approval`, write, asks first): Record offline approval for an eligible, unexpired bill-to-balance estimate, choosing billing timing and an optional confirmation email.
- **Bill the customer** (`change_estimate_billing_moment`, write, asks first): Change charge trigger before posting.
- **Bill now** (`bill_estimate_now`, write, asks first): Post approved estimate's charge immediately.
- **Schedule jobs** (`schedule_estimate_jobs`, write, asks first): Select dates, technician, checklist/service, and note; repetition shortcuts supported.
- **Edit estimate job** (`edit_estimate_job`, write, asks first): Change unfinished job date, technician, service, or note.
- **Delete estimate job** (`delete_estimate_job`, write, asks first): Remove an unfinished job from its route.
- **Templates** (`list_estimate_templates`, read): Inspect and sort reusable estimates.
- **New template** (`create_estimate_template`, write): Save reusable lines, copy, terms, and validity.
- **Edit template** (`edit_estimate_template`, write): Change reusable estimate defaults.
- **Archive template** (`archive_estimate_template`, write): Remove template from builder choices.
- **Estimate settings** (`configure_estimates`, write, asks first): Set numbering, defaults, limits, reminders, payment timing, and company alerts.
- **Estimate help** (`read_estimate_contextual_help`, read): Inspect field explanations and matching manual sections.

### Messaging, SMS & Notifications

Email All Statements, Email Selected, Compose email and more.

- **Email All Statements** (`email_all_statements`, write, asks first): Email eligible statements in bulk.
- **Email Selected** (`email_selected_statements`, write, asks first): Send explicitly selected statements, including empty ones.
- **Compose email** (`compose_customer_email`, write): Prepare email for one customer or group.
- **Send email** (`send_customer_email`, write, asks first): Send individual or group customer email.
- **Compose text** (`compose_customer_text`, write): Prepare individual or group SMS.
- **Send text** (`send_customer_text`, write, asks first): Send SMS after account verification and enablement.
- **Message Log** (`read_message_log`, read): Inspect communications and sent/delivered/failed outcomes.
- **SMS Usage** (`read_sms_usage`, read): Inspect text volumes and costs by period.
- **Appointment reminders** (`configure_appointment_reminders`, write, asks first): Enable automatic pre-service email/SMS reminders.
- **Custom templates** (`edit_notification_template`, write, asks first): Change notification subject and body.
- **Notification types** (`toggle_notification_type`, write, asks first): Enable or disable particular automatic messages.
- **Customer preferences** (`set_customer_notification_preferences`, write): Manage channel preferences on a customer's behalf.
- **Delivery tracking** (`read_email_delivery_tracking`, read): Inspect sent, opened, and bounced email outcomes.
- **Report Access** (`read_visit_report_access`, read): Inspect confirmed reads, first/last read, count, and filtered opens.
- **Visit report subscription** (`manage_visit_report_opt_out`, write, asks first): Manage customer's email/SMS report opt-out independently.

### Statements

Print All, Text All, Statement automation and more.

- **Print All** (`print_all_statements`, read): Print statements using customer delivery eligibility.
- **Text All** (`text_all_statements`, write, asks first): Text statements to customers with eligible SMS delivery.
- **Statement automation** (`configure_statement_automation`, write, asks first): Select current/next-month send, timing, empty documents, SMS, and link lifespan.
- **Send next month's statements** (`send_next_month_statements`, write, asks first): Select recipients and send during the allowed advance-billing window.
- **Statement preview** (`preview_statement_send`, read): Preview each recipient's next-month statement email and its attached PDF before sending.
- **Statement dry run** (`dry_run_statement_send`, read): Dry-run the next-month statement send before sending actual messages.
- **Statement test** (`send_statement_test`, write, asks first): Send yourself a test of the displayed next-month statement email.
- **Statement run** (`read_statement_send_run`, read): Inspect recipient results for a next-month statement send run.
- **Statements to print** (`print_statement_run_exceptions`, read): Print paper-delivery and missing-email recipients.
- **Changes after sending** (`read_statement_changes_after_sending`, read): Inspect changes after sending next month's statement; payments are not listed.
- **Send updated statement** (`send_updated_statements`, write, asks first): Notify selected customers of post-send changes.
- **Mark as reviewed** (`mark_statement_changes_reviewed`, write): Dismiss reviewed changes until another change occurs.
- **Review held billing** (`read_held_billing`, read): Inspect waiting periods and billed/skipped decisions.
- **Bill held periods** (`bill_held_periods`, write, asks first): Post selected, customer-wide, or all held charges.
- **Skip held periods** (`skip_held_periods`, write, asks first): Close held lines without charging.

### Past-Due Notices

Past-due recipients, Save notice draft, Notice templates and more.

- **Past-due recipients** (`select_past_due_recipients`, read): Filter owed amounts, payment age, status, and recent notices.
- **Save notice draft** (`save_past_due_draft`, write): Save recipient/message work for later.
- **Notice templates** (`manage_past_due_templates`, write): Create, edit, copy, or archive saved notice wording.
- **Notice preview** (`preview_past_due_notices`, read): Review personalized notices and validate merge fields.
- **Notice dry run** (`dry_run_past_due_notices`, read): Check recipients and exclusions without sending.
- **Send test to me** (`send_past_due_test`, write, asks first): Email yourself a sample notice and statement.
- **Review & send notices** (`send_past_due_notices`, write, asks first): Send personalized collection messages with statements.
- **Run history** (`read_past_due_run_history`, read): Inspect past runs and recipient delivery results.
- **Retry failed notices** (`retry_failed_past_due_notices`, write, asks first): Start another send for failed recipients.
- **Cancel run** (`cancel_past_due_run`, write, asks first): Stop notices not already handed to mail server.
- **Print notice exceptions** (`print_past_due_exceptions`, read): Print statements for customers who cannot be emailed.
- **Export notice CSV** (`export_past_due_run_csv`, read): Download collection-run records.

### Inventory

Catalog, Inventory item, Stock and more.

- **Catalog** (`read_inventory_catalog`, read): Inspect supplies and configured units/costs.
- **Inventory item** (`create_inventory_item`, write): Define item name, unit, cost, and category.
- **Stock** (`read_stock_levels`, read): Inspect warehouse and technician-truck quantities.
- **Add stock** (`receive_stock`, write): Record deliveries with quantity and unit cost.
- **Transfer stock** (`transfer_stock`, write): Move supplies between warehouse and trucks.
- **Manual adjustment** (`adjust_stock`, write): Correct breakage, loss, counts, or returns.
- **Activity** (`read_stock_activity`, read): Inspect movement timestamps and responsible users.
- **Chemical Usage** (`read_inventory_usage_report`, read): Inspect supply consumption over a period.
- **Chemical Cost** (`read_inventory_cost_report`, read): Inspect total supply costs.
- **Low-stock alerts** (`read_low_stock_alerts`, read): Receive notices before supplies run out.
- **Inventory Value** (`read_inventory_value`, read): Inspect value of stock on hand.
- **Material Cost Per Service** (`read_material_cost_per_service`, read): Inspect material expense per visit/customer/technician.
- **Usage Trends** (`read_inventory_usage_trends`, read): Inspect seasonal usage and comparative consumption.

### The Mobile App

Daily schedule, Service summary, Checklist and more.

- **Daily schedule** (`read_mobile_schedule`, read): Inspect route order, instructions, contacts, and distance; select dates.
- **Service summary** (`record_service_summary`, write): Enter serviced areas, mowing height, treatment, and issues.
- **Checklist** (`complete_mobile_checklist`, write): Answer required and optional job-specific questions.
- **Supplies used** (`record_mobile_supply_usage`, write): Record or adjust product quantities for truck deduction.
- **Service notes** (`add_mobile_service_notes`, write): Record visit notes; non-checklist notes remain internal.
- **Sync status** (`read_mobile_sync_status`, read): Inspect online/offline indicator.
- **Mobile App Data** (`read_visit_gps_evidence`, read): Inspect start/end coordinates, timestamps, and distance from property.
- **Photo evidence** (`read_photo_metadata`, read): Inspect image, location, timestamp, technician, and image details.
- **Minimum photo requirements** (`set_visit_photo_requirement`, write): Set how many photos completion requires.
- **Problem reports** (`read_field_problem_reports`, read): See immediately flagged field problem reports as an owner or manager; no dedicated report screen is specified.
- **Submit field problem report** (`submit_field_problem_report`, write, asks first): Flag a field problem from the crew app so the office sees it in real time.

### Customer Portal

Customer Dashboard, Billing history, Statements and more.

- **Customer Dashboard** (`read_portal_dashboard`, read): Inspect owed/overdue amounts, activity, and subscribed services.
- **Billing history** (`read_portal_billing_history`, read): Inspect own charges, payments, credits, and balance.
- **Statements** (`download_portal_statements`, read): Open and download own monthly statements.
- **Payments** (`pay_portal_balance`, write, asks first): Pay by configured card, PayPal, or ACH.
- **Change saved card** (`change_portal_saved_card`, write): Replace saved card, including a running service's card.
- **Remove saved card** (`remove_portal_saved_card`, write, asks first): Remove saved payment card.
- **Automatic payments** (`enable_portal_automatic_payments`, write, asks first): Authorize automatic card or approved PayPal payments.
- **Cancel automatic payments** (`cancel_portal_automatic_payments`, write, asks first): Stop all automatic charges and delete saved gateway details.
- **Services** (`read_portal_services`, read): Inspect subscribed services and visit weekdays.
- **Reset portal password** (`reset_customer_portal_password`, write, asks first): Generate replacement credentials; previous password stops working.
- **Email portal password** (`email_customer_portal_password`, write, asks first): Send generated password without exposing it to staff.
- **Service visit reports** (`read_portal_service_reports`, read): Read the customer's own lawn-service reports and recorded photos, measurements, and customer-visible notes when available; do not infer pool-specific readings.

### Reports

Send visit report, Balances, Income and more.

- **Send visit report** (`send_visit_report`, write, asks first): Deliver photo/summary report by email, text, or both.
- **Balances** (`read_balances_report`, read): Inspect balances, overdue age, and payment recency.
- **Income** (`read_income_report`, read): Inspect money received by period.
- **Credits** (`read_credits_report`, read): Inspect credits issued.
- **Charges** (`read_charges_report`, read): Inspect posted charges by period.
- **Recurring** (`read_recurring_report`, read): Inspect monthly recurring value and growth.
- **Lawn Treated** (`read_lawn_treated_report`, read): Inspect completed services by technician, period, and type.
- **Schedule report** (`read_schedule_report`, read): Filter/sort LIVE stops across arbitrary periods and completion status.
- **Sales Tax** (`read_sales_tax_report`, read): Inspect collected tax by period.
- **Inventory report** (`read_inventory_reports`, read): Inspect usage, cost, and present stock value.
- **Report filters** (`filter_reports`, read): Apply date, customer, and report-specific filters.
- **Open schedule PDF** (`open_schedule_report_pdf`, read): Preview grouped route sheets with optional contact/notes.
- **Download schedule PDF** (`download_schedule_report_pdf`, read): Save configured schedule document.
- **Schedule CSV** (`export_schedule_report_csv`, read): Export full filtered schedule without PDF row limit.
- **Export report** (`export_report_csv`, read): Download filtered report results.
- **Technician performance** (`read_technician_performance`, read): Inspect lawns serviced per technician, average service time, route completion rates, and service-quality metrics.
- **Refund reporting** (`read_refund_report`, read): Inspect reported credits and processed refunds in financial reporting; do not assume a separate Refund report tab.
- **Read route efficiency analytics** (`read_route_efficiency_analytics`, read): Read route efficiency analytics: average stops per day, drive time between stops and completion rates.

### Payroll

Pay Profile, Technician pay, Run Payroll and more.

- **Pay Profile** (`read_technician_pay_profile`, read): Inspect earning types and date-effective rates.
- **Technician pay** (`configure_technician_pay`, write): Set hourly/per-visit compensation and company/individual rates.
- **Run Payroll** (`calculate_payroll`, write): Calculate technician earnings for a selected period; actual payroll is processed by an external payroll provider.
- **Review payroll** (`review_payroll_calculation`, read): Inspect calculated earnings before approval.
- **Finalize payroll** (`finalize_payroll_run`, write, asks first): Approve and finalize an earnings-calculation run and make its pay statements available; do not process or disburse payroll.
- **Pay Statements** (`read_pay_statements`, read): Inspect earnings breakdown and completed services; technicians see their own.
- **Pay statement PDF** (`download_pay_statement_pdf`, read): Download pay statement for external payroll processing.
- **Historical payroll** (`read_payroll_history`, read): Inspect past runs and compare periods.
- **Earnings reports** (`read_earnings_reports`, read): Inspect labor cost by technician, period, or service.
- **Per-service rates** (`configure_service_pay_rates`, write): Configure service-specific and combined earning types.
- **Distribute pay statements** (`distribute_pay_statements`, write, asks first): Distribute generated earnings statements using the vendor-documented capability; no specific delivery mechanism or funds transfer is established.

### QuickBooks

Connect to QuickBooks, Reconnect, Disconnect QuickBooks and more.

- **Connect to QuickBooks** (`connect_quickbooks`, write): Authorize Intuit OAuth connection.
- **Reconnect** (`reconnect_quickbooks`, write): Renew an expired connection.
- **Disconnect QuickBooks** (`disconnect_quickbooks`, write, asks first): Revoke integration access.
- **Auto-sync** (`set_quickbooks_auto_sync`, write, asks first): Enable automatic outgoing accounting exports.
- **Export Dashboard** (`read_quickbooks_export_dashboard`, read): Inspect exported, pending, skipped, failed counts and errors.
- **Export customers** (`export_quickbooks_customers`, write, asks first): Send customers to QuickBooks.
- **Export items** (`export_quickbooks_items`, write, asks first): Send service templates to QuickBooks.
- **Export statements** (`export_quickbooks_statements`, write, asks first): Send statements as QuickBooks invoices.
- **Export payments** (`export_quickbooks_payments`, write, asks first): Send payment records to QuickBooks.
- **Retry export** (`retry_quickbooks_export`, write, asks first): Resend a failed accounting entity.
- **Default Income Account** (`set_quickbooks_income_account`, write): Set destination account and release waiting service items.

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

## Who can see my EZ Lawn Biller session, and how do I revoke it?

- **What we store.** Your signed-in EZ Lawn Biller profile, AES-256-GCM encrypted, in Finland. No password.
- **What your agent gets.** The 277 EZ Lawn Biller tools, never the session cookie.
- **What the session sees.** The customers, locations, routes, visits, statements and reports your EZ Lawn Biller login can open as Admin or staff.
- **What no tool touches.** Field presence stays with your crew: starting and completing visits on site, phone calls, live-camera photos and offline work on crew phones. Also your plan, company profile, card numbers, Stripe and PayPal secrets and your password.
- **If EZ Lawn Biller 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 EZ Lawn Biller 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 EZ Lawn Biller changes?

Cotlet watches the apps it serves and updates the server when EZ Lawn Biller changes its schedule, route or billing screens.

New EZ Lawn Biller features become available to your agent.

Your EZ Lawn Biller role determines which customers, routes and statements it sees.

Cotlet never sees or stores your password. If EZ Lawn Biller signs you out, open your Cloud Browser with one click from the Cotlet console and sign in again.

## Approvals, undo and mistakes

1. **Read the route.** See the day's stops and visits.
2. **Make a draft.** Moved stops stay in a private draft, ready to review.
3. **You approve.** The draft is published to technicians' phones.
4. **Bill and chase.** Statements and past-due notices follow your approval.

| Action | Undo |
|---|---|
| Publish a schedule draft | Make another draft and publish it |
| Mark a visit completed | Edit the visit in EZ Lawn Biller |
| Record a payment | Correct it on the customer's ledger in EZ Lawn Biller |
| Send past-due notices | Sent emails cannot be recalled; a running batch can be cancelled |

Tools marked Asks first wait for your approval by default; you can switch that off per tool. Unmarked tools run at once.

MCP call:

```
{
  "name": "record_offline_payment",
  "arguments": {
    "record": "Example customer",
    "fields": {
      "amount": 120,
      "method": "Check",
      "reference": "1042",
      "date": "2026-11-12"
    }
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/ez-lawn-biller/offline-payments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"record":"Example customer","fields":{"amount":120,"method":"Check","reference":"1042","date":"2026-11-12"}}'
```

Response:

```
{
  "payment": "Saved",
  "balance": "Updated"
}
```

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

## How much does the EZ Lawn Biller MCP server cost?

**About $19 a month** for a lawn care company with one crew and about 60 weekly mowing customers, over four weeks, 3,240 credits. Your EZ Lawn Biller plan stays as it is.

| Job | Calls | Credits |
|---|---|---|
| Read the day's schedule on 22 workdays | 1 × 22 | 220 |
| Mark 15 visits completed from the office a week | 1 × 60 | 600 |
| Record 30 check and cash payments | 1 × 30 | 300 |
| Move rained-out stops in a weekly draft | 2 × 4 | 80 |
| Text customers about weather delays | 1 × 20 | 200 |
| Send 10 estimates to new prospects | 1 × 10 | 100 |
| Add 8 new customers and their services | 1 × 8 | 80 |
| Send past-due notices to 12 customers | 1 × 12 | 120 |
| Read the balances report each week | 1 × 4 | 40 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 3,240 |

The $29 pack covers a typical month for most owners.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your EZ Lawn Biller plan and role apply.

Illustrative consumption at the smallest credit pack rate, not a subscription or measured usage. Buy credit packs separately; extra calls add usage.

## EZ Lawn Biller MCP server: connection options

| Option | What it does | Where it stops |
|---|---|---|
| QuickBooks integration | Keeps invoices and payments in step with your books | Accounting sync; no routes, visits or customer messages |
| Crew app | Technicians see routes and complete visits on their phones | Field work inside EZ Lawn Biller; not an agent connection |
| Customer portal | Customers see statements and pay online | Customer self-service; not an office assistant |

Cotlet works through your own EZ Lawn Biller sign-in and covers the office work between the crew's visits and your books.

## 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 EZ Lawn Biller tools go to contact@cotlet.dev.

## EZ Lawn Biller MCP server: questions

### How do I get access?

Start a free Cotlet trial, open EZ Lawn Biller in your Cloud Browser and sign in at landlord.app.ezlawnbiller.com with your own EZ Lawn Biller login. Your agent then gets the 277 EZ Lawn Biller tools.

### How do I connect EZ Lawn Biller to ChatGPT or Claude?

Sign up at cotlet.dev, log in to EZ Lawn Biller 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 EZ Lawn Biller account through Cotlet, in their phone apps too.

### What can ChatGPT do in EZ Lawn Biller?

ChatGPT and Claude read the day's routes, plan stop changes in a schedule draft, mark visits completed from the office, add customers and on-demand jobs, record cash and check payments, send estimates and statements and run past-due notices, within your EZ Lawn Biller role. Crews still take visit photos and calls on their phones; the agent reads those records.

### Is there an official ChatGPT or Claude app for EZ Lawn Biller?

No official EZ Lawn Biller MCP server was found on ezlawnbiller.com or in its manual, and no EZ Lawn Biller listing was verified in the ChatGPT apps or Claude connectors directories (checked 11 Nov 2026). Cotlet is an independent MCP server for ChatGPT, Claude and other agents in your signed-in EZ Lawn Biller account.

### Can ChatGPT reschedule lawn visits in EZ Lawn Biller?

ChatGPT moves the stops you name in a private schedule draft and publishes it after you approve, so technicians' phones get the new routes.

### Can ChatGPT mark a visit completed in EZ Lawn Biller?

ChatGPT marks the visit you name completed from the office after you approve it, posting any charge its billing arrangement requires without duplicating it.

### Can ChatGPT record a payment in EZ Lawn Biller?

ChatGPT records the cash or check payment you give it, with amount, method, reference and date, on the customer's account.

### Can ChatGPT send past-due notices in EZ Lawn Biller?

ChatGPT selects the customers who owe you, previews each personalized notice and sends them with their statements after you approve the run.

### Can ChatGPT take visit photos in EZ Lawn Biller?

No. Visit photos are taken with the crew phone's camera, with watermark and GPS. ChatGPT reads existing visit photos, their metadata and the GPS record of each visit.

### Does EZ Lawn Biller have an API?

No publicly documented EZ Lawn Biller API was found on 11 Nov 2026: its /api, /developers and /docs pages returned 404, and its FAQ names QuickBooks as its integration. Cotlet works through your own EZ Lawn Biller sign-in.

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

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

### Is Cotlet affiliated with EZ Lawn Biller?

No. Cotlet is independent and not affiliated with EZ Lawn Biller.

---

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.