Yardbook MCP Server
Customers, jobs, schedules and invoices in Yardbook for landscapers.
託管 MCP 伺服器
npx add-mcp 'https://cotlet.dev/mcp/v1/yardbook'可安裝到 Claude Code、Codex、Cursor 等客戶端
文件
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Yardbook API and MCP server: Let your AI agent do the lawn care office work in Yardbook.
Yardbook has no public API, no developer docs, no webhooks and no MCP server (checked 27 Oct 2026). Cotlet runs 14 Yardbook tools hosted, over MCP for agents and REST for scripts, in your own Yardbook login.
Customers, jobs, schedules and invoices in Yardbook for landscapers. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Yardbook
- Page: https://cotlet.dev/integrations/yardbook-api-mcp-server
What can you automate in Yardbook?
- Add a customer with crew notes
- Book weekly or biweekly mowing
- Read tomorrow's route by crew
- Turn site notes into an estimate
- Invoice finished jobs
- Match checks and cash to invoices
Does Yardbook have an MCP server or an API?
- The Zapier app has 10 triggers, such as Job Completed and Estimate Approved, and 2 actions: Create Lead and Create AI Event. Zapier MCP offers the same 2 actions.
- Nothing official reads your schedule, writes an estimate or invoice, or records a payment.
- n8n has no Yardbook node, and viaSocket's Yardbook MCP page lists no Yardbook actions yet.
| What you need | Zapier and Zapier MCP | AgentZap | Cotlet |
|---|---|---|---|
| Add a lead or prospect | Yes, Create Lead | From phone calls | Yes |
| Book a recurring job on a crew | No | From calls, says it uses an API | Yes, weekly or biweekly |
| Search customers, jobs, invoices | New events only | No | Any time |
| Write and send estimates and invoices | No | No | Yes, sends after your OK |
| Record check and cash payments | No | No | Yes, after your OK |
| Price on top of Yardbook | Free plan, then Zapier tasks | $109 a month | Pay per call |
Checked 27 Oct 2026. Sources: Zapier: Yardbook triggers and actions, Zapier MCP for Yardbook, AgentZap: Yardbook AI receptionist, viaSocket: yardbook MCP
How does Cotlet connect to Yardbook?
- Sign in to Yardbook. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Yardbook password, and no estimate, invoice or recorded payment goes through until you approve it.
Connect Yardbook to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Yardbook for agents. Sign up, log in to Yardbook as the owner or an office user in its Cloud Browser, then press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in your agent's MCP server or connector settings.
- Approve the connection. Chat apps send you to a Cotlet sign-in. Editors, n8n and scripts use an API key from the console.
Yardbook shares the address https://cotlet.dev/mcp/v1 with the other apps you enable. Turned Yardbook on after you connected? Refresh the connector and the 14 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-yardbook \
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-yardbook": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-yardbook]
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: yardbook_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: yardbook_write
How to use the Yardbook REST API
Create your Cotlet API key
Create a Cotlet API key with access to Yardbook and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Yardbook in Cotlet and enable it for agents. Account access: Your own Yardbook account (email and password, the account owner or an office user).
Make your first Yardbook API request
REST:
curl "https://cotlet.dev/api/v1/yardbook/customers?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read customers and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "yardbook",
"tool": "list_customers",
"result": {
"customers": [
{
"customer_id": "284117",
"name": "Maria Lopez",
"type": "customer",
"address": "18 Elm Street",
"email": "maria@example.com",
"phone": "555-0142",
"balance": "0.00"
},
{
"customer_id": "284230",
"name": "Parker Property",
"type": "customer",
"address": "7 Ridge Road",
"email": "office@parker.example.com",
"phone": "555-0177",
"balance": "240.00"
}
],
"next_cursor": null
}
}
Lists customers, prospects or both. Search matches name, address, email and phone.
Balance is the amount the customer still owes on open invoices. Pass next_cursor back as cursor for the next page.
limit: 1 to 200. Default: 50.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Yardbook workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Scheduled and completed jobs in a date range, with customer, services and assigned crew member. Use list_jobs in your configured business report. |
| Make | HTTP > Make a request | Estimates with customer, total and status, newest first. Use list_estimates in your configured business report. |
| Python or Node.js | REST API | Full invoice: line items, payments recorded and amount due. Use get_invoice in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Yardbook; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Yardbook API endpoints and MCP tools
Customers and prospects
Search takes a name, street, email or phone, so a prospect from your quote form is found before a second record is made. No tool edits or deletes an existing customer.
- List customers (
list_customers, read): Customers and prospects with address, email, phone and balance. - Get customer (
get_customer, read): One customer with contact details, notes, upcoming jobs, open estimates and invoices. - Create customer (
create_customer, write): Add a customer or prospect with contact details and service address.
Jobs, routes and crews
A series repeats weekly or biweekly; twice a month or a seasonal stop date is still set in Yardbook. Crews must already exist in My Company.
- List jobs (
list_jobs, read): Scheduled and completed jobs in a date range, with customer, services and assigned crew member. - Schedule job (
schedule_job, write): Add a one-time or recurring job to the schedule, optionally assigned to a crew member. - Complete job (
complete_job, write): Mark a job as completed, so it can be invoiced.
Estimates
Drafts reach no one. A sent estimate carries Yardbook's online Approve link when you turned that on in Invoice Settings.
- List estimates (
list_estimates, read): Estimates with customer, total and status, newest first. - Create estimate (
create_estimate, write): Draft estimate for a customer or prospect. Nothing is sent until you call send_estimate. - Send estimate (
send_estimate, write, asks first): Email an estimate to the customer with a link to approve it online.
Invoices and payments
Payments are recorded, never charged: no tool moves money or touches Stripe. A check larger than the bill becomes a customer credit in Yardbook.
- List invoices (
list_invoices, read): Invoices with customer, total, amount due, due date and status. - Get invoice (
get_invoice, read): Full invoice: line items, payments recorded and amount due. - Create invoice (
create_invoice, write): Invoice from a completed job or an approved estimate, or with your own line items. Not sent yet. - Send invoice (
send_invoice, write, asks first): Email an invoice to the customer with a link to view it. - Record payment (
record_payment, write, asks first): Record a cash, check or other payment received against an invoice.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/yardbook-api-mcp-server#tools
Who can see my Yardbook session, and how do I revoke it?
- What we store. Your logged-in Yardbook profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 14 Yardbook tools, never the session cookie.
- What the session sees. What your login sees: customers, addresses, gate codes, jobs, invoices.
- What no tool touches. Stripe, card charges, Plaid, plan and billing, employees, deletes.
- If you are logged out. You log in to Yardbook again yourself, in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser, or change your Yardbook password.
Gate codes and alarm notes sit in the customer record, so the agent reads them like your office does. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.
Is it against Yardbook's terms? Account safety
While not an exhaustive list, you agree not to: ... use "bots," "spiders," "crawlers," website search/retrieval application, or other manual or automatic device or process to retrieve, index, "data mine," probe, scan, test the vulnerability of any system or network or breach or otherwise circumvent the intended functionality of the Services
Yardbook Terms of Service, Restrictions, last updated 25 Apr 2023
The same terms say "You may not share your account information with another person" and let Yardbook suspend an account at its sole discretion. A paid Business or Enterprise plan gets 30 days' notice to cure a material breach first. Cotlet works in the Yardbook web app with your own login, and Yardbook could still call that an automatic process. We found no public case of a Yardbook account closed for automation (checked 27 Oct 2026).
How we keep your Yardbook looking like your office:
- Your own Yardbook account, logged in by you
- One Cloud Browser with a steady IP and cookies
- Estimates, invoices and payments wait for your OK (3 tools)
- No tool deletes a customer, job, invoice or payment
- If Yardbook objects, we pause the Yardbook tools for everyone within 24 h
Month-end billing for 50 accounts is 100 calls. Spread it over an evening instead of firing it all in one minute.
What happens when Yardbook changes?
- 12 h between tests of the Yardbook reads and drafts
- 24 h between tests of sends a customer would get
- $0 for a call to a Yardbook tool paused for repair
When Yardbook renames a menu or moves a field on the job form, we fix the tool and your agent calls it the same way as before. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Looks for the household. By phone and street, so a prospect is not added twice.
- Reads the route. Which crew already works that street on that weekday.
- Books the series. Weekly or biweekly, with the gate code in the notes.
- Reports what it did. Customer, crew, first visit, and anything left for you.
| Action | Undo |
|---|---|
| Create a customer or prospect | Edit or remove it in Yardbook by hand |
| Schedule a recurring job | End This Recurring Activity, future visits go |
| Draft an estimate or invoice | Delete it in Yardbook while unsent |
| Send an estimate | No, the email is out; set it back to pending to resend |
| Send an invoice | No; it moves to Pending Payment and can only go inactive |
| Record a payment | Delete Payment on the invoice in Yardbook |
3 of 14 tools ask first: send_estimate, send_invoice and record_payment. New customers, jobs and drafts reach no customer, so they run at once. You can switch the wait off per tool for a month-end batch you already checked.
A payment that does not match the invoice leaves it in Pending Payment or creates a credit. The agent names both before it records.
MCP call:
{
"name": "schedule_job",
"arguments": {
"customer_id": "284117",
"date": "2026-10-13",
"services": [
"Mowing",
"Edging"
],
"repeat": "weekly",
"assignee_id": "5521",
"notes": "Side gate code 1234. Bag clippings."
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/yardbook/customers/284117/job/schedule \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"2026-10-13","services":["Mowing","Edging"],"repeat":"weekly","assignee_id":"5521","notes":"Side gate code 1234. Bag clippings."}'
Response:
{
"job_id": "9930412",
"customer_id": "284117",
"date": "2026-10-13",
"repeat": "weekly",
"status": "scheduled",
"services": [
"Mowing",
"Edging"
],
"assignee": "Crew 1"
}
A nightly script or n8n flow can call the same tools over REST at /api/v1/yardbook, with the same key and price per call, for example tomorrow's route sent to the crew lead at 8 pm. A booking on a crew that does not exist fails, and failed calls are free. Each tool row above shows its REST path.
How much does the Yardbook MCP server cost?
About $22 a month for one crew with 50 weekly accounts, 3,720 credits. Your Yardbook plan stays as it is, free Starter included.
| Job | Calls | Credits |
|---|---|---|
| Tomorrow's route and crew, each workday | 1 × 22 | 220 |
| Month-end invoice and email per account | 2 × 50 | 1,000 |
| New customer with a weekly mowing series | 4 × 6 | 240 |
| Estimate from walk-through notes | 4 × 8 | 320 |
| Record a week of checks | 7 × 4 | 280 |
| Overdue list and three reminders, weekly | 4 × 4 | 160 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 3,720 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on Starter (free), Business ($34.99) and Enterprise ($49.99)
Lawn care forums and listings put a full-time solo route at 40 to 60 weekly accounts, so the month is our example: 50 accounts billed at month end, 6 new customers, 8 estimates, about 6 checks a week. Yardbook's prices are its annual rates from January 2026. Dollars at the $29 pack rate.
Yardbook MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| davidcolatti/yardbook-scrape | An unnamed scraper with no README, 0 stars. | Last push 19 Nov 2020; no server, no writes. |
| JohnCt14/field-intake | Phone form for one lawn company that exports a CSV for Yardbook. | Someone still types the CSV into Yardbook. |
| Zapier MCP for Yardbook | Create Lead and Create AI Event as MCP tools. | No jobs, estimates, invoices or payments. |
| Jobber, QuoteIQ, LMN, Aspire | Field service platforms with more built-in automation. | You move customers and history off Yardbook and pay per month. |
We found no Yardbook MCP server on GitHub and no other hosted one. For phone calls that should land as jobs, a receptionist like AgentZap is the closer fit. For the estimate, invoice and payment desk, Cotlet works in the Yardbook you already run.
Who runs Cotlet
Cotlet is built by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Yardbook tools to contact@cotlet.dev.
Yardbook API and MCP: questions
How do I get access?
Create a free account at https://cotlet.dev, open Yardbook under Integrations in the console and log in to Yardbook in its Cloud Browser. The trial starts when you sign up, no card asked.
How do I connect Yardbook to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Yardbook 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 Yardbook account through Cotlet, in their phone apps too.
What can ChatGPT do in Yardbook?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Yardbook: chase unpaid invoices; add a new customer and schedule recurring lawn jobs; turn site-visit notes into an estimate. You ask in plain words, and anything that reaches other people waits for your OK first.
Does Yardbook have a Zapier action for invoices or jobs?
No. The Zapier app has 10 triggers and two actions, Create Lead and Create AI Event (checked 11 Oct 2026). Scheduling jobs, estimates, invoices and payments are not available there, which is what Cotlet adds.
Do I need a paid Yardbook plan?
No. The tools work on the free Starter plan. Bulk texts and automatic invoice reminders need Business, and QuickBooks sync needs Enterprise, the same as when you work in Yardbook yourself.
Can the agent charge a customer's card?
No. record_payment only writes down a check, cash or other payment you already received. Card payments still go through Yardbook and Stripe as before.
Can it react when a job is completed?
Cotlet has no Yardbook trigger. Run your agent on a schedule, or let Yardbook's Zapier trigger Job Completed start it.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 14 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Yardbook?
No. Cotlet is independent and not affiliated with Yardbook, Inc.
Can I use the Yardbook API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
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
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.