Connect DoorLoop to Claude Code

Make Claude manage leases and tenants in DoorLoop. From the terminal, inside the sessions where you already work.

How do you connect DoorLoop to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect DoorLoop, you add a DoorLoop MCP server: a small hosted service that exposes DoorLoop's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own DoorLoop account. No API keys pasted into config files.

claude mcp add --transport http doorloop https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in DoorLoop once connected?

Full read-write means Claude can pull the rent roll, flag overdue balances, and act on what it finds: creating maintenance tasks, posting lease charges or credits, and drafting tenant notes. Portfolio questions get answered in seconds, and every financial posting waits for your explicit approval first.

Pull the rent roll and flag leases with overdue balances
Retrieve a tenant's details, lease terms, and payment history
Create a maintenance task and assign it to a team member, after you approve
Post a lease charge or credit to a tenant ledger, after you approve
Draft a note on a tenant or lease record for your review
Run a profit and loss or cash flow report for a property

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same DoorLoop access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the DoorLoop API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when DoorLoop changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build DoorLoop connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same DoorLoop connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own DoorLoop account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on DoorLoop's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to DoorLoop?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the DoorLoop account it signs in with. Revoking access is one click in DoorLoop.

More on the DoorLoop connector

DoorLoop connector for claude.ai AppFolio + Claude Code Buildium + Claude Code Follow Up Boss + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us