Bring Real Estate
to Claude Desktop
Learn how to connect DoorLoop to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the DoorLoop MCP Server?
Connect your DoorLoop account to any AI agent and take full control of your rental portfolio and real estate operations through natural conversation.
What you can do
- Property Orchestration — List and manage your entire real estate portfolio programmatically, including retrieving detailed metadata for properties and individual units
- Tenant & Lease Lifecycle — Access complete tenant profiles and monitor active lease agreements to maintain high-fidelity records of your occupants
- Maintenance Architecture — Monitor maintenance requests and programmatically create new work orders to coordinate repairs and service vendors efficiently
- Lead & Prospecting — Retrieve directories of potential tenants (leads) to streamline your vacancy filling and marketing workflows
- Financial Visibility — Access summarized rent roll reports and vendor directories directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from DoorLoop (Settings > Integrations)
3. Start managing your rental business from Claude, Cursor, or any MCP client
No more manual toggling between unit lists or digging through maintenance logs. Your AI acts as your dedicated property operations and lease coordinator.
Who is this for?
- Property Managers — instantly retrieve tenant contact info and check unit availability using natural language commands
- Maintenance Coordinators — track work order status and dispatch vendors without leaving your communication tools
- Real Estate Investors — monitor portfolio performance and rent roll reports through simple AI queries
Built-in capabilities (12)
Requires subject and unit/property IDs. Create a new maintenance work order
Get details for a specific lease
Get details for a specific property
Get the current rent roll report
Get details for a specific tenant
List all lease agreements
List all properties
List prospective tenants
List all tenants
Can be filtered by property ID. List all rental units
List all service vendors
List all maintenance work orders
Why Claude Desktop?
Claude Desktop is the definitive way to connect DoorLoop to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
DoorLoop in Claude Desktop
DoorLoop and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DoorLoop to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DoorLoop in Claude Desktop
The DoorLoop MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DoorLoop for Claude Desktop
Every tool call from Claude Desktop to the DoorLoop MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my DoorLoop API Key?
Log in to DoorLoop, navigate to Settings > Integrations, and generate a new key for the Public API.
Can I filter units by property?
Yes! The list_units tool allows you to specify a property_id to retrieve only the units belonging to a specific building or site.
Does it support creating maintenance work orders?
Absolutely. Use the create_work_order tool to programmatically generate a maintenance request for a specific unit with a subject and description.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
