EZ Lawn Biller MCP server for ChatGPT and Claude
Connect EZ Lawn Biller to ChatGPT, Claude and other AI agents through Cotlet. Work with routes, customer records, visit history and payments in your own signed-in account. Cotlet is independent and not affiliated with EZ Lawn Biller. If EZ Lawn Biller offers an official API for your needs, we recommend it.
What you can ask
Show the customers with past-due balances.
Prepare changes to the stops I name in a private schedule draft and ask me before publishing.
Record the cash payment I provide, with its amount, reference and date. Ask me before saving.
Connect in 2 minutes
Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.
ChatGPT
Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.
Claude Code
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
Cursor
Copy .cursor/mcp.json from this repo into your project:
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
Run it locally (stdio)
This repo is a real MCP server. It speaks MCP over stdio, lists its EZ Lawn Biller tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
{"mcpServers": {"ez-lawn-biller": {"command": "python3", "args": ["/absolute/path/to/ez-lawn-biller-mcp/ez_lawn_biller_agent.py", "serve"], "env": {"COTLET_API_KEY": "your-key"}}}}
Or with Docker:
docker build -t ez-lawn-biller-mcp .
docker run -i --rm -e COTLET_API_KEY ez-lawn-biller-mcp
Tools: ez_lawn_biller_guide, ez_lawn_biller_status, ez_lawn_biller_open, ez_lawn_biller_read, ez_lawn_biller_click, ez_lawn_biller_type, ez_lawn_biller_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
Command line
Python 3.10+, nothing else to install. Run from this repo:
export COTLET_API_KEY="your-key"
python3 ez_lawn_biller_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 ez_lawn_biller_agent.py status # is EZ Lawn Biller ready in your Cotlet.dev account
python3 ez_lawn_biller_agent.py guide # EZ Lawn Biller screens and sign-in link
python3 ez_lawn_biller_agent.py read # open EZ Lawn Biller, read the page, close the browser
python3 ez_lawn_biller_agent.py tools # list Cotlet.dev tools
python3 ez_lawn_biller_agent.py serve # start the stdio MCP server (same as no argument)
Questions from EZ Lawn Biller users
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.
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 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.
Is Cotlet affiliated with EZ Lawn Biller?
No. Cotlet is independent and not affiliated with EZ Lawn Biller.
Find it on
Request access: https://cotlet.dev/signup?app=ez-lawn-biller&utm_source=github&utm_medium=readme&utm_campaign=ez-lawn-biller
Metadata
Release files for ez-lawn-biller-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ez_lawn_biller_mcp-1.1.0.tar.gz | 8.1 kB | Without provenance | Details for ez_lawn_biller_mcp-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ez_lawn_biller_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for ez_lawn_biller_mcp-1.1.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / ez_lawn_biller_mcp-1.1.0.tar.gz
| Download URL | ez_lawn_biller_mcp-1.1.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
143dd38444ef784d27fb482645e7fa2e5ac28b0265c2db0d92950568bc32c1a2
|
|
BLAKE2b-256 checksum How to use checksums |
a1c7ff50013d66a5d24737fc1a88fe9bb642e09283576319d532c2615e82d049
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ez_lawn_biller_mcp-1.1.0-py3-none-any.whl
| Download URL | ez_lawn_biller_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2fa0aa82bd76d2eef883404f7bb5531b3af685bf8d9eda59aefe110d53eedbd
|
|
BLAKE2b-256 checksum How to use checksums |
47e8704df5f2ac04a86ded2223e9d7399f4182f730ec65dda7aae38bf09951ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ez-lawn-biller-mcp 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.