MCP PropTech
Triggers automated workflows via webhooks for maintenance status changes and vendor escalations, allowing for extended automation such as emailing vendors or generating reports.
Connects to the Twilio API to facilitate sending WhatsApp notifications to tenants, supporting features like ticket acknowledgment and scheduling updates.
Provides capabilities to send automated tenant updates and maintenance notifications via WhatsApp using various message templates for acknowledgments, delays, and resolutions.
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., "@MCP PropTech Escalate the leaking water heater in unit 4C to a plumber and notify the tenant"
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.
MCP PropTech — Property Maintenance Automation
A production-ready Model Context Protocol (MCP) server that lets a Claude-powered agent orchestrate your full property maintenance workflow — built on top of an existing n8n + WhatsApp automation system.
┌─────────────────────────────────────────────────────────┐
│ Claude Agent / Desktop │
└────────────────────────┬────────────────────────────────┘
│ MCP (stdio / SSE)
┌────────────────────────▼────────────────────────────────┐
│ MCP PropTech Maintenance Server │
│ │
│ get_open_tickets update_maintenance_status │
│ notify_tenant escalate_to_vendor │
└──────┬──────────────────────────────────┬───────────────┘
│ │
┌──────▼──────┐ ┌────────▼──────────┐
│ Ticket DB │ │ Integrations │
│ (in-memory │ │ ┌─────────────┐ │
│ → Postgres │ │ │ n8n │ │
│ in prod) │ │ │ Webhooks │ │
└─────────────┘ │ ├─────────────┤ │
│ │ Twilio │ │
│ │ WhatsApp │ │
│ └─────────────┘ │
└───────────────────┘Tools
Tool | Description |
| Query tickets filtered by status, priority, category, property |
| Drive tickets through the lifecycle with audit notes |
| Send WhatsApp messages via 5 templates (acknowledgement, scheduled, update, resolved, delay) |
| Assign vendor, trigger n8n workflow, notify tenant in one call |
Related MCP server: n8n Manager for AI Agents
Quick start
# 1. Install dependencies
npm install
# 2. Configure environment
cp .env.example .env
# Fill in ANTHROPIC_API_KEY, Twilio creds, n8n webhook URLs
# 3. Run the agent (single pass over the ticket queue)
npm run agent
# 4. Run as a daemon (checks every 5 minutes)
npm run agent:dev -- --daemonClaude Desktop integration
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"proptech-maintenance": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/MCPPropTech/src/mcp-server/index.ts"],
"env": {
"ANTHROPIC_API_KEY": "sk-ant-...",
"TWILIO_ACCOUNT_SID": "AC...",
"TWILIO_AUTH_TOKEN": "...",
"TWILIO_WHATSAPP_FROM": "whatsapp:+14155238886",
"N8N_WEBHOOK_MAINTENANCE": "https://your-n8n.com/webhook/maintenance",
"N8N_WEBHOOK_ESCALATE": "https://your-n8n.com/webhook/escalate"
}
}
}
}Then from Claude Desktop you can say things like:
"Show me all open emergency tickets"
"Escalate the burst pipe in unit 3B to a plumber"
"Send Marcus in 7A a WhatsApp update on his AC ticket"
Architecture
MCP Server (src/mcp-server/)
The server runs over stdio (for Claude Desktop / agent SDK) and exposes the
four tools above. Swap StdioServerTransport for SSEServerTransport to serve
over HTTP for remote deployments.
Ticket Store (src/data/)
An in-memory store with 6 seed tickets covering every status and priority.
Replace TicketStore internals with a Postgres/Supabase/Airtable adapter for
production — the tool handlers only call the store interface.
n8n Integration (src/integrations/n8n.ts)
Fires webhooks to two n8n endpoints:
Maintenance webhook — on every status change and tenant notification
Escalation webhook — when a vendor is assigned
Your n8n workflows handle the rest: emailing vendors, updating spreadsheets, creating calendar invites, sending owner reports.
WhatsApp / Twilio (src/integrations/whatsapp.ts)
Uses the Twilio API to send WhatsApp messages. Gracefully falls back to simulation mode (console logging) when credentials are not set — perfect for demos and local development.
Claude Agent (src/agent/maintenance-agent.ts)
A full agentic loop using @anthropic-ai/sdk that:
Connects to the MCP server via
StdioClientTransportFetches available tools and converts them to the Anthropic tool format
Runs an agentic loop until Claude stops calling tools
Logs each tool call and result to the console
Lifecycle state machine
open ──→ in_progress ──→ resolved ──→ closed
│ │ ↑
│ └──→ awaiting_tenant
│ │
└──→ escalated ←────┘
│
└──→ in_progress / resolvedEnvironment variables
Variable | Required | Description |
| Agent only | Claude API key |
| Optional | Twilio account SID for WhatsApp |
| Optional | Twilio auth token |
| Optional | Sender WhatsApp number |
| Optional | n8n status-change webhook URL |
| Optional | n8n vendor escalation webhook URL |
| Optional | n8n API key (if required by your instance) |
| Optional | JSON map overriding default vendor directory |
| Optional | Daemon poll interval (default: 300000 = 5 min) |
Available Tools
4 toolsescalate_to_vendorA
Escalates a maintenance ticket to a specialist vendor. Selects the right vendor from the directory based on trade (plumbing, electrical, hvac, etc.), updates ticket status to 'escalated', triggers an n8n workflow that emails/WhatsApps the vendor, and sends the tenant an update message. Use overrideVendorPhone to assign a specific vendor instead of the default.
Inputs: ticketId (required), trade (required), urgencyNote (required), preferredTime, +1 more.
get_open_ticketsA
Retrieves maintenance tickets from the property management system. Filters by status (default: all non-resolved), priority, category, and property. Returns tickets sorted by priority (emergency first) then recency.
Inputs: status, priority, category, propertyId, +1 more.
notify_tenantA
Sends a WhatsApp message to the tenant associated with a ticket. Supports five message templates: acknowledgement, scheduled, update, resolved, delay. Pass customMessage to override the template. Falls back to SMS if WhatsApp fails. Logs the notification to n8n and appends to ticket internal notes.
Inputs: ticketId (required), messageType (required), customMessage, scheduledFor.
update_maintenance_statusA
Updates the status of a maintenance ticket and records a history note. Fires an n8n webhook so your automation system stays in sync. Valid transitions: open→in_progress|awaiting_tenant|escalated, in_progress→awaiting_tenant|resolved|escalated, awaiting_tenant→in_progress|resolved|closed, escalated→in_progress|resolved, resolved→closed.
Inputs: ticketId (required), newStatus (required), note (required), updatedBy, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: escalate_to_vendor handles vendor escalation, get_open_tickets retrieves ticket data, notify_tenant sends tenant notifications, and update_maintenance_status updates ticket status. The descriptions specify unique actions and contexts, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., escalate_to_vendor, get_open_tickets) using snake_case throughout. This predictable naming scheme enhances readability and agent usability without any deviations or mixed conventions.
With 4 tools, the count is reasonable for a property tech maintenance domain, covering key operations like retrieval, status updates, notifications, and escalations. It's slightly lean but well-scoped, as each tool serves a distinct function without redundancy.
The tool set covers core maintenance workflows: retrieving tickets, updating statuses, notifying tenants, and escalating to vendors. Minor gaps exist, such as no tool for creating new tickets or managing vendor directories, but agents can likely work around these with the provided tools.
Related MCP Connectors
Property management AI: work orders, vendors, appliances, and triage for Claude and ChatGPT.
Property maintenance triage and vendor packet generator.
Run a home-service business from your AI: jobs, customers, invoices, estimates, texts.
Work with your AppFolio® portfolio: tenants, vacancies, reports, maintenance, financials, and more.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage n8n automation workflows through natural language commands, including creating, executing, monitoring, and organizing workflows with full CRUD operations and execution management.122 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage n8n workflow automation instances through tools for workflow CRUD operations, execution monitoring, and webhook triggering. It facilitates programmatic interaction with n8n instances via the n8n API with AI-optimized descriptions and error handling.62MIT
- FlicenseAqualityDmaintenanceConnects AI assistants to the Lanten property management API, allowing them to manage tenants, units, and work orders using natural language.1511 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage rental properties on TenantCloud via natural language, including contacts, messaging, maintenance, and financials.-