LMN MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Get your API key at https://cotlet.dev/app and export it as 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.
LMN through Cotlet.dev. Call lmn_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 |
|---|---|
| lmn_guideA | How to work in LMN (review landscaping estimates, schedules, timesheets and invoices): its screens and the sign-in link. Call this first. |
| lmn_statusA | Check that your Cotlet.dev account and LMN are ready: account, credits and LMN connection. |
| lmn_openA | Open a LMN page in your signed-in Cloud Browser (default https://my.golmn.com) to work with review landscaping estimates, schedules, timesheets and invoices. |
| lmn_readB | Read the current LMN page: its text and numbered buttons, links and fields. |
| lmn_clickC | Click a numbered element on the current LMN page. |
| lmn_typeC | Type text into a numbered field on the current LMN page. |
| lmn_closeA | Close the LMN 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 targets a distinct phase of browser work: guide (onboarding docs), status (readiness check), open (session start), read (page inspection), click and type (element interaction), and close (session teardown). The lmn_guide vs lmn_status boundary is slightly close but descriptions clearly separate documentation from account/connection checks.
All seven tools use the same lmn_ prefix followed by a concise snake_case verb or state name (open, read, click, type, close, guide, status). The pattern is predictable and consistent throughout.
Seven tools is well-scoped for a browser automation surface; each tool corresponds to a discrete step (start, inspect, interact, finish) with no redundant primitives. Nothing feels padded or missing from the core interaction loop.
The set covers the full session lifecycle—status, open, read, click, type, close—plus a guide, which is strong for the stated purpose. Minor gaps remain: no explicit navigation/goto for arbitrary URLs, no scroll or wait primitive, and no select/dropdown helper, which could matter for multi-page LMN workflows.