Yardbook MCP Server and API by Cotlet

dev.cotletPublished by cotlet.devOfficial publisherv1.0.2Updated Nov 11, 2026

Yardbook landscaping business management MCP server: list customers, schedule job, create invoice.

The publisher's own server: Cotlet

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that connects an assistant to Yardbook landscaping business management to list customers, schedule jobs and create invoices.

What you can do
  • List and look up Yardbook customers
  • Schedule jobs for customers
  • Create invoices
  • All actions go through the Cotlet API layer in front of Yardbook
When to use it
Useful when you run a landscaping or field-service business on Yardbook and want an assistant to look up customers, book jobs or draft invoices without switching apps.
Requirements
A remote streamable HTTP endpoint at cotlet.dev; no local package. A Cotlet API key, created in the Cotlet dashboard, sent as an Authorization header in the form Bearer plus the key. Network access to cotlet.dev.
Before you install
The server can create jobs and invoices, which change business records. It requires a Cotlet API key in the Authorization header, and requests pass through Cotlet's service to Yardbook, so customer and billing data reach a third party. Only the description is available; no tool list or documentation was provided.

Installation

In SourceWeft

  1. Open Yardbook MCP Server and API by Cotlet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.cotlet%2Fyardbook/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "yardbook-and-api-by-cotlet": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/yardbook/connect"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestNov 11, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Cotlet integrations