EZ Lawn Biller MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet API key, obtained at https://cotlet.dev/app. Required for local stdio usage and tool calls; without it, tool calls return an error asking you to set COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
EZ Lawn Biller through Cotlet.dev. Call ez_lawn_biller_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ez_lawn_biller_guideA | How to work in EZ Lawn Biller (plan lawn routes, record payments and review past-due accounts): its screens and the sign-in link. Call this first. |
| ez_lawn_biller_statusB | Check that your Cotlet.dev account and EZ Lawn Biller are ready: account, credits and EZ Lawn Biller connection. |
| ez_lawn_biller_openB | Open a EZ Lawn Biller page in your signed-in Cloud Browser (default https://landlord.app.ezlawnbiller.com) to work with plan lawn routes, record payments and review past-due accounts. |
| ez_lawn_biller_readA | Read the current EZ Lawn Biller page: its text and numbered buttons, links and fields. |
| ez_lawn_biller_clickB | Click a numbered element on the current EZ Lawn Biller page. |
| ez_lawn_biller_typeB | Type text into a numbered field on the current EZ Lawn Biller page. |
| ez_lawn_biller_closeA | Close the EZ Lawn Biller browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role in a browser-automation workflow: guide, status check, open session, read page, click, type, and close. There is no meaningful overlap between them, so an agent can select the right tool without confusion.
All seven tools use the same snake_case ez_lawn_biller_ prefix followed by a short action label. Although 'guide' and 'status' are noun-like rather than pure verbs, the overall convention is highly predictable and consistent.
Seven tools is a well-scoped set for a browser-driven billing app: enough to cover orientation, session lifecycle, reading, and interaction without bloat. Each tool earns its place in the workflow.
The surface covers the essential browser automation lifecycle: guidance, readiness check, open, read, click, type, and close. Minor gaps exist around navigation (back/forward), scrolling, or explicit form submission, but these are largely workable through read/click/type.