LMN MCP Server
Landscape estimates, proposals, jobs, schedules, invoices and payments in LMN.
Server MCP Terhosting
npx add-mcp 'https://cotlet.dev/mcp/v1/lmn'Terpasang ke Claude Code, Codex, Cursor, dan lainnya
Dokumentasi
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
LMN API and MCP server: Let your AI agent run the landscaping office.
LMN gives accounts on plans that include it an API Key and API Username, found by a Security Admin under Settings > Integrations, to connect its Zapier integration. No public developer API, LMN MCP server or official ChatGPT or Claude connector was verified.
LMN hands out an API Key only for its Zapier integration, and has no MCP server (checked 13 Nov 2026). Cotlet runs a hosted LMN MCP server with 23 tools that ChatGPT, Claude and your scripts use in your own LMN account. Proposals, invoices, texts and every card charge wait for your OK.
- Free 7-day trial, no card
- Unofficial, not affiliated with LMN or Granum
- Page: https://cotlet.dev/integrations/lmn-api-mcp-server
What can your AI agent do in LMN?
- Follow up proposals nobody answered
- Turn a sold estimate into a scheduled job
- Review and approve yesterday's timesheets
- Generate and send month-end invoices
- Run autopay payments after your OK
- Stop visits and billing for a cancelled customer
Does LMN have an MCP server or an API?
- The Zapier integration has one trigger, an estimate created or updated, and five actions: create a to-do, a request or communication history, and find or create and update a contact.
- AskLMN answers questions about your LMN data in plain English inside LMN; it is a closed beta for Professional plans and above.
- LMN syncs invoices and payments with QuickBooks Online from its own Accounting page.
| What you need | LMN + Zapier | AskLMN | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | Fixed zaps, no agent | LMN's own assistant, closed beta | Hosted MCP server |
| Proposals, jobs and schedule | Estimate trigger only | Answers questions, no actions | 23 tools, writes after your OK |
| Timesheets, invoices and payments | Not in the integration | Answers questions, no actions | Review, generate, send, charge |
| Run from n8n or a script | Through Zapier | Inside LMN only | REST, same key |
Checked 13 Nov 2026. Sources: LMN + Zapier: a guide, AskLMN, LMN Help Center, LMN by Granum, Help: New QuickBooks Online setup, Help: Build your LMN Operating Budget, Help: Create a Service Estimate, Help: Create a Standard Estimate, Help: Estimate List, Help: Send Proposals via Text, Help: Standard Web Proposals, Help: Jobs Setup & Management, Help: Change Orders in LMN, Help: Schedule Tab, Help: Cancel / Stop a Service, Help: Approve Timesheets, Help: Generate Invoices, Help: Invoice List, Help: Invoice Templates & Automation, Help: Payment Runs with Stripe, Help: Payment Runs with Fiserv & Payrix, Help: Automated Visit Reminder Texts
How does the LMN MCP server work?
- Log in to LMN. Once, in a browser we host for you.
- Connect your AI agent. One address in its settings.
- Hand it the office work. It previews the billing, you approve it.
Your agent works in your own signed-in Cloud Browser. Writes, texts to customers and every card charge wait for your OK.
How to connect LMN to your AI agent
- Sign in to LMN in a Cloud Browser. Open my.golmn.com in your Cotlet Cloud Browser and log in with your own LMN user.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
- Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
LMN answers on the shared address https://cotlet.dev/mcp/v1 like every other app you activate, so a single connector is enough. Activated LMN later? Refresh the connector and the 23 LMN tools load.
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: lmn_read
All 23 LMN MCP tools
Built from the owner workflows of the LMN Help Center. Read tools run at once. Write tools take an action; list, get, preview and the review actions only read, the rest change LMN and ask first.
Budget and pricing
The operating budget prices every estimate through the Price List; services and service types carry estimates into jobs.
- Build the operating budget (
manage_budget, write, asks first): Read or build an Operating Budget or Express Budget, choose the overhead recovery method and activate it. - Set price list rates, taxes and templates (
manage_price_list, write, asks first): Read or add production rate calculators, estimate templates and default taxes in the Price List. - Set up services and service types (
manage_services, write, asks first): List or add the services and service types used on estimates, jobs and billing.
Estimates and proposals
Service estimates for recurring work, Standard estimates for installs, and web proposals clients sign in the browser.
- Read the estimate list (
list_estimates, read): Read the Estimate List with type, status, proposal status, version and total. - Create service and standard estimates (
manage_estimates, write, asks first): Create a Service estimate for recurring work or a Standard estimate for a project, and mark items optional. - Send web proposals by email or text (
send_proposal, write, asks first): Send an estimate as a web proposal by email, text or both, or read its proposal status. - Set up the lead form (
configure_lead_form, write, asks first): Read or change the Lead Generation Form that turns website inquiries into CRM contacts.
Jobs, schedule and crews
Jobs from sold estimates, change orders, visits on the calendar and the timesheets crews send back.
- Create jobs from estimates (
manage_jobs, write, asks first): List jobs, create one from a sold estimate, set it up for invoicing, add tasks or link an estimate. - Add change orders (
manage_change_orders, write, asks first): Create a change order on a sold job, share it with the customer, or approve it. - Schedule visits (
manage_schedule, write, asks first): Read scheduled visits, or schedule a one-time or recurring visit for a job. - Stop a service (
stop_service, write, asks first): Stop visits and billing for a job that should no longer be serviced. - Set up work calendars (
manage_work_calendars, write, asks first): List work calendars or add one for recurring or non-recurring work. - Review and approve timesheets (
manage_timesheets, write, asks first): Read the Daily Review and timesheet alerts, approve timesheets, or punch a crew out from the office. - Set payroll codes and wage costs (
manage_payroll_settings, write, asks first): List or add payroll codes, or add a wage cost for a staff member. - Send visit reminder texts (
manage_sms, write, asks first): List SMS templates, add one with variables, or switch visit reminder texts on or off.
Invoicing and payments
Generate, send and remind; record checks; charge saved cards only after your OK.
- Generate invoices (
generate_invoices, write, asks first): Find invoices ready to create for a date range and invoice group, generate them, or revert an invoice run. - Send invoices to the customer portal (
manage_invoices, write, asks first): List invoices by stage, create an ad hoc invoice on a job, approve it, or email and publish it to the customer portal. - Manage invoice groups (
manage_invoice_groups, write, asks first): List invoice groups, create one, or add and remove jobsites. - Automate invoices and reminders (
configure_invoice_automation, write, asks first): Set a job's invoice schedule, or edit the invoice email templates and automatic reminders. - Review payments (
list_payments, read): Read the Payments page: online and manual payments by name, date, status and method. - Record payments (
record_payment, write, asks first): Record a check or cash payment, or charge a one-time online payment with the customer's saved method. - Run payment runs (
run_payments, write, asks first): List invoices ready for a payment run, or charge them against the customers' cards on file. - Request a payment method (
request_payment_method, write, asks first): Email a customer a request to add a card, or a bank account for ACH, to their file.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/lmn-api-mcp-server#tools
Who can see my LMN session, and how do I revoke it?
- What we store. Your signed-in LMN browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- What your agent gets. The 23 LMN tools. The session cookie stays in the Cloud Browser.
- What the session sees. What your LMN user and its permissions open: estimates, jobs, timesheets, invoices.
- What no tool touches. Users and seats, security permissions, SMS verification, payment processor settings, and the QuickBooks connection and sync.
- If LMN signs you out. You log in again yourself, in the same Cloud Browser.
- How to cut access. Disable LMN for agents, reset the browser, or change your LMN password.
You type your LMN password yourself; the agent only uses the session that login leaves behind. Cotlet never sees your API Key. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
What happens when LMN changes?
LMN is moving pages to new designs: change orders already live only on the redesigned job page, and web proposals replace the classic Print Reports flow on accounts that have them. Cotlet follows those screens, and your agent keeps the same tool names.
Features that LMN switches on per account, such as change orders, text proposals and the lead form, are there for the agent only when they are there for you.
If LMN logs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.
Approvals, undo and mistakes
- Preview the billing. generate_invoices lists what is ready.
- Show you the totals. And any invoice flagged for review.
- Generate after your OK. One invoice run you can revert.
- Send when you say. manage_invoices emails and publishes them.
| Action | How to put it right |
|---|---|
| Invoices generated too early | Revert the invoice run; the invoices go back to Generate |
| Visit scheduled on the wrong day | Move it again with manage_schedule |
| Proposal or invoice sent | Already with your customer: follow up with them |
| Payment run charged | A real card charge: no tool call undoes it, so keep confirmation on |
All 21 write tools ask first: by default you confirm each call, and you can switch that off per tool. Keep it on for run_payments and record_payment, which move money. The 2 read tools run at once.
MCP call:
{
"name": "generate_invoices",
"arguments": {
"action": "preview",
"from": "2026-11-01",
"to": "2026-11-30",
"group": "Maintenance",
"filter": "all_billable"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/lmn/invoices/generate \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"preview","from":"2026-11-01","to":"2026-11-30","group":"Maintenance","filter":"all_billable"}'
Response:
{
"from": "2026-11-01",
"to": "2026-11-30",
"group": "Maintenance",
"ready": 42,
"flagged_for_review": 1
}
The example previews November for the Maintenance group: 42 invoices ready, 1 flagged, nothing generated yet. A cron job or n8n flow can make the same call over REST at /api/v1/lmn with the same key and price, in JSON. Failed calls are free.
How much does the LMN MCP server cost?
About $26 a month for a landscape company with two crews in season, 4,440 credits. Your LMN plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Timesheet review and approval | 3 × 22 | 660 |
| Schedule moves | 2 × 20 | 400 |
| Daily payments check | 1 × 20 | 200 |
| Monday proposal follow-up | 11 × 4 | 440 |
| New estimates and proposals | 3 × 10 | 300 |
| Jobs from sold estimates | 2 × 6 | 120 |
| Change orders | 2 × 3 | 60 |
| Payments recorded | 1 × 30 | 300 |
| Month-end billing, 42 invoices | 44 × 1 | 440 |
| Autopay payment run | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 294 calls | 4,440 |
The smallest pack, 5,000 credits for $29, covers this month. Winter months with fewer visits use fewer calls.
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your LMN plan, payment processor and fees apply as they are
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
LMN MCP server: other ways to connect
| Option | What it does | Where it stops |
|---|---|---|
| LMN + Zapier | An estimate trigger and contact, to-do, request and history actions. | Nothing for jobs, timesheets, invoices or payments; needs a plan that includes it. |
| AskLMN | Plain-English answers about your LMN data, inside LMN. | Closed beta, Professional and above; it answers, it does not act. |
| LMN automations | Invoice reminders, visit reminder texts and invoice schedules you set once. | Fixed rules inside LMN, no agent. |
| By hand | Open each screen in LMN. | One screen at a time, after the crews are in. |
If the Zapier integration covers your job, use it: it is LMN's own route. Cotlet fits the rest, when you want ChatGPT, Claude or a script to work in LMN from your own login, with nothing to host.
Who runs Cotlet
Take Group sp. z o.o. builds and runs Cotlet. The company is registered in Poland, EU (VAT PL6342984273), has worked since 2019 and is led by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Ask about the LMN tools at contact@cotlet.dev.
LMN MCP server: questions
How do I get access?
Sign up free at https://cotlet.dev/signup?app=lmn, turn on LMN under Integrations in the console and log in at https://my.golmn.com/lmn/ in your Cloud Browser. Then connect your AI agent and ask it about your open estimates. The trial needs no card.
Does LMN have an API?
LMN gives accounts on eligible plans an API Key and API Username, which Security Admins find in Settings > Integrations, for its Zapier integration: one trigger (an estimate is created or updated) and five actions on to-dos, requests, communication history and contacts (checked 13 Nov 2026). No LMN MCP server or official ChatGPT or Claude connector was verified; AskLMN answers questions inside LMN in a closed beta. Cotlet does not use the API Key: it works in your own signed-in LMN account.
How is this different from AskLMN?
AskLMN is LMN's own assistant for questions about your data, in a closed beta for Professional plans and above. Cotlet is separate: it lets ChatGPT, Claude or a script you choose do work in LMN, such as sending proposals, approving timesheets and generating invoices, with your OK.
Can the agent charge my customers' cards?
Only through LMN Pay steps LMN already has: a one-time payment with a saved method, or a payment run against cards on file with autopay. Both wait for your OK every time, and LMN still asks for CONFIRM before a run. Reading payments charges nothing.
Do I need a Security Admin user?
Not for Cotlet. LMN asks for Security Admin to see the Zapier API Key and to save SMS templates. Cotlet uses your login, so each tool works when your user can do the same thing in LMN.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 23 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
Is Cotlet affiliated with LMN?
No. Cotlet is independent and not affiliated with LMN or Granum.
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.