Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Lanten MCP Server List all open work orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that connects AI assistants to the Lanten property management API. Use it with Claude, Cursor, Zed, or any MCP-compatible client to manage tenants, units, and work orders using natural language.
Get an API key — in your Lanten dashboard go to Settings → Developers and create a key.
Add to your MCP client config:
{
"mcpServers": {
"lanten": {
"command": "npx",
"args": ["-y", "@lanten-ai/mcp-server"],
"env": {
"LANTEN_API_KEY": "lk_your_api_key_here"
}
}
}
}For Claude Desktop this file lives at:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
For Claude Code run: claude mcp add lanten -e LANTEN_API_KEY=lk_your_key -- npx -y @lanten-ai/mcp-server
Restart your client and start chatting:
"List all open work orders for Flat 4, 12 Oak Street" "Create a new tenant: Jane Smith, jane@example.com, assign her to unit abc-123" "Mark work order WO-214 as completed"
Related MCP server: Buildium MCP Server
Tool | Description |
| List tenants with optional search and pagination |
| Get a single tenant by ID |
| Create a tenant, optionally linked to a unit |
| Update tenant fields (partial update) |
| Permanently delete a tenant |
Tool | Description |
| List property units with optional address search |
| Get a single unit by ID |
| Create a property unit |
| Update unit fields (partial update) |
| Permanently delete a unit |
Tool | Description |
| List work orders; filter by status, priority, tenant, or unit |
| Get a single work order by ID |
| Create a work order linked to a tenant/unit |
| Update a work order (status, priority, etc.) |
| Permanently delete a work order |
Priority levels: 0 Emergency · 1 High · 2 Medium · 3 Low
Statuses: reported · in_progress · completed · cancelled
Variable | Required | Description |
| ✅ | Your API key from Settings → Developers |
| — | Override the base URL (e.g. for self-hosted instances). Defaults to |
git clone https://github.com/lanten/mcp-server
cd mcp-server
npm install
npm run build
# Test with the MCP Inspector
LANTEN_API_KEY=lk_your_key npm run inspectorCreate a new tenant. Optionally assign them to an existing unit.
Inputs: firstName (required), lastName (required), email, phoneNumber, +2 more.
Create a new property unit.
Inputs: addressLine1 (required), city (required), country (required), postcode (required), +3 more.
Create a new work order (maintenance issue). Optionally link to a tenant and/or unit.
Inputs: title (required), description (required), priority, tenantId, +2 more.
Permanently delete a tenant. This cannot be undone.
Inputs: id (required).
Permanently delete a property unit. This cannot be undone.
Inputs: id (required).
Permanently delete a work order. This cannot be undone.
Inputs: id (required).
Get a single tenant by ID, including their linked units.
Inputs: id (required).
Get a single property unit by ID, including current tenants.
Inputs: id (required).
Get a single work order by ID, including tenant, unit, and attachments.
Inputs: id (required).
List tenants for the account. Supports free-text search across name, email, phone, and unit address. Returns paginated results.
Inputs: search, page, pageSize.
List property units for the account. Supports address search. Returns paginated results including current tenants.
Inputs: search, page, pageSize.
List work orders (maintenance issues) for the account. Filter by status, priority, tenant, or unit. Supports search by title or code.
Inputs: search, status, priority, tenantId, +3 more.
Update an existing tenant. Only supplied fields are changed.
Inputs: id (required), firstName, lastName, email, +2 more.
Update an existing property unit. Only supplied fields are changed.
Inputs: id (required), addressLine1, addressLine2, city, +4 more.
Update an existing work order. Only supplied fields are changed. Setting status to "completed" automatically records the resolved time.
Inputs: id (required), title, description, status, +4 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Connect AI assistants to PayRent to manage landlord portfolios, confirming changes first.
Property management AI: work orders, vendors, appliances, and triage for Claude and ChatGPT.
Connect AI assistants to Appimate's Business Agent Tools and Services.
Real estate agency CRM: listings, clients, leads and viewings from your AI assistant (OAuth).
