Lanten MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANTEN_API_KEY | Yes | Your API key from Settings → Developers | |
| LANTEN_API_URL | No | Override the base URL (e.g. for self-hosted instances). Defaults to https://app.lanten.ai/api/open/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tenantsA | List tenants for the account. Supports free-text search across name, email, phone, and unit address. Returns paginated results. |
| get_tenantA | Get a single tenant by ID, including their linked units. |
| create_tenantB | Create a new tenant. Optionally assign them to an existing unit. |
| update_tenantA | Update an existing tenant. Only supplied fields are changed. |
| delete_tenantA | Permanently delete a tenant. This cannot be undone. |
| list_unitsA | List property units for the account. Supports address search. Returns paginated results including current tenants. |
| get_unitA | Get a single property unit by ID, including current tenants. |
| create_unitB | Create a new property unit. |
| update_unitB | Update an existing property unit. Only supplied fields are changed. |
| delete_unitA | Permanently delete a property unit. This cannot be undone. |
| list_work_ordersA | List work orders (maintenance issues) for the account. Filter by status, priority, tenant, or unit. Supports search by title or code. |
| get_work_orderA | Get a single work order by ID, including tenant, unit, and attachments. |
| create_work_orderA | Create a new work order (maintenance issue). Optionally link to a tenant and/or unit. |
| update_work_orderA | Update an existing work order. Only supplied fields are changed. Setting status to "completed" automatically records the resolved time. |
| delete_work_orderA | Permanently delete a work order. This cannot be undone. |
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 15 tools
Each tool targets a specific resource and action (create, get, list, update, delete) with no overlap. Tenants, units, and work orders are clearly separated.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_tenant, list_work_orders). No deviations.
15 tools cover exactly the CRUD operations for three entities, which is within the ideal 3-15 range. No tool feels superfluous.
Full CRUD for tenants, units, and work orders, plus search and filtering in list operations. No obvious gaps in the property management domain.