DoorLoop MCP Server

Tenants, leases, rent charges and payments for landlords.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/doorloop'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

DoorLoop API and MCP server

DoorLoop has an open REST API, but it is not self-serve (checked 11 Oct 2026). The pricing page lists API access on the Premium plan only, DoorLoop says it is "still selective about who gets access", and you apply and talk by phone before you get the documentation. There is no official DoorLoop MCP server.

Tenants, leases, rent charges and payments for landlords. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Property management software for landlords and property managers: properties and units, tenants, leases, rent collection, maintenance tasks, communications and accounting.

What is the DoorLoop API?

Cotlet's DoorLoop API exposes 14 endpoints for your own DoorLoop account: list properties, list units, list tenants, list leases, get lease transactions, list tasks, list communications, create tenant, create task, create lease, post lease charge, record lease payment, issue lease credit and send announcement. The list_properties endpoint returns your properties with address, type and unit count. Each endpoint takes simple JSON inputs like cursor, property_id or lease_id and works both as an operation of the doorloop_read or doorloop_write MCP tool for agents and as a REST call for scripts.

  • Category: Real estate
  • Endpoints: 14 (7 read, 7 write)
  • Updated: 2026-11-12

DoorLoop has an open REST API, but it is not self-serve (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for DoorLoop with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

Does DoorLoop have an official API?

DoorLoop has an open REST API, but it is not self-serve (checked 11 Oct 2026). The pricing page lists API access on the Premium plan only, DoorLoop says it is "still selective about who gets access", and you apply and talk by phone before you get the documentation. There is no official DoorLoop MCP server.

TaskDoorLoop officialCotlet
List tenants, units and leasesPartly: Premium plan and DoorLoop approval; Zapier has Find Lease, Find Tenant or Prospect and Find UnitYes
Create a lease with term, deposit and chargesPartly: The API reference documents Create a Lease; Premium and approvalYes
Post a one-time charge, such as a late feePartly: Zapier action Create Lease Charge; PremiumYes
Issue a lease creditPartly: Zapier action Create Lease Credit; PremiumYes
Create a task or work orderPartly: Zapier action Create a Task/Work Order; PremiumYes
Record a rent paymentPartly: The API reference documents Create a Lease Payment; Premium and approval. Zapier has a New Lease Payment trigger but no action to record oneYes
Send an announcement by email, text, voice or tenant portalNo: Only in the DoorLoop app, on Pro or PremiumYes
Read the Communications LogPartly: The API reference documents List all Communication Logs; Premium and approvalYes

Sources: DoorLoop pricing (API access, Zapier, plans), DoorLoop partner page (apply for API access), DoorLoop API reference: authentication, DoorLoop API reference: create a lease payment, DoorLoop Help: send an announcement to your tenants, DoorLoop Help: receive a payment on a lease, DoorLoop Help: set up automatic late fees

Quick reference

DoorLoop has an open REST API, but it is not self-serve (checked 11 Oct 2026). The pricing page lists API access on the Premium plan only, DoorLoop says it is "still selective about who gets access", and you apply and talk by phone before you get the documentation. There is no official DoorLoop MCP server.
Cotlet provides a hosted MCP server and REST API for DoorLoop: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=doorloop and request the app in the Cotlet console. ChatGPT and Claude connect with OAuth at https://cotlet.dev/mcp/v1/connect, no API key; code editors and scripts use an API key from the console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    doorloop_read, doorloop_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/doorloop, each operation at its own route, e.g. POST /api/v1/doorloop/leases/{lease_id}/payment
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_properties, list_units, list_tenants, list_leases, get_lease_transactions, list_tasks, list_communications, create_tenant, create_task, create_lease, post_lease_charge, record_lease_payment, issue_lease_credit, send_announcement
Confirm      create_lease, post_lease_charge, record_lease_payment, issue_lease_credit, send_announcement (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/doorloop-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=doorloop and requests DoorLoop in the Cotlet console.
2. The user signs in to DoorLoop once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables DoorLoop for agents. An agent cannot do this step.
3. ChatGPT and Claude: the user adds https://cotlet.dev/mcp/v1/connect as a connector and signs in to Cotlet (OAuth). Code editors and scripts: an API key from the console goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted DoorLoop server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source DoorLoop MCP server instead.

Policy: Cotlet never stores passwords and never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to DoorLoop in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get DoorLoop only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no DoorLoop login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following DoorLoop's terms; Cotlet is not affiliated with DoorLoop.

What can an AI agent do in DoorLoop?

Cotlet is best for landlords and small property managers who want their AI agent to post charges, record payments, set up leases and message tenants in DoorLoop without running or fixing a server.

  • Record check and cash rent payments (runs: daily): "Record today's rent checks in DoorLoop: Unit 2B Marcus Hale $1,450 check 1042, Unit 3A Priya Shah $1,500 cash, Unit 6 Leo Brandt $1,640 by Zelle. Skip anything already entered and tell me what is still owed." → list_leases, get_lease_transactions, record_lease_payment
  • Send announcements to tenants of a property (runs: weekly): "Tell all tenants at Maple Court by email and text that the water is off Thursday from 9 to 12, show me the text first, and later tell me whose text failed." → list_properties, send_announcement, list_communications
  • Set up a new lease: "Set up a 12-month lease for Dana Reed (dana@example.com) in Unit 4 at Maple Court, $1,600 a month due on the 1st, starting Nov 1, with a $1,600 deposit. Check the unit is free first." → list_units, list_leases, list_tenants, create_tenant, create_lease
  • Charge late fees on unpaid rent (runs: monthly): "Find leases that still owe October rent and post a $50 late fee on each one." → list_leases, get_lease_transactions, post_lease_charge
  • Find leases ending soon and vacant units (runs: weekly): "Which leases end in the next 60 days, and which units are vacant?" → list_leases, list_units

Can DoorLoop automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a DoorLoop connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to record check and cash rent payments, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

WhereHow to connectHow to schedule
Your AI agentAdd https://cotlet.dev/mcp/v1 with your API key.A scheduled agent run, for example a Claude Code routine.
n8nMCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/doorloop/leases.Schedule Trigger node.
MakeHTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH.Scenario schedule.
ZapierWebhooks by Zapier, Custom Request: the same method, URL, header and body.Schedule by Zapier trigger.
Your own scriptGET https://cotlet.dev/api/v1/doorloop/leases with your API key.cron or GitHub Actions.

Tools

For AI agents: Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to DoorLoop.

list_properties

Your properties with address, type and unit count. Access: read. REST: GET /api/v1/doorloop/properties. MCP: doorloop_read → list_properties.

ParameterTypeRequiredDescription
searchstringnoMatch on property name or address.
cursorstringnoNext page cursor from the previous call.

Returns the properties in your DoorLoop account, with address and number of units. Search matches the property name or address. Use the property_id of each item in the other tools.

Example response:

{
  "properties": [
    {
      "property_id": "pr_3a91c7",
      "name": "Maple Court",
      "address": "120 Maple St, Springfield",
      "type": "Multi-family",
      "units": 12
    }
  ],
  "next_cursor": null
}

list_units

Units with property, rent and whether each is occupied or vacant. Access: read. REST: GET /api/v1/doorloop/units. MCP: doorloop_read → list_units.

ParameterTypeRequiredDescription
property_idstringnoOnly this property. Property ID from list_properties.
statusenumnoall, occupied or vacant. Default: all.
cursorstringnoNext page cursor from the previous call.

Returns units with the property they belong to and their occupancy. Filter by property or by occupied or vacant. Use unit_id from here in create_lease.

Example response:

{
  "units": [
    {
      "unit_id": "un_5b20d4",
      "property": "Maple Court",
      "name": "Unit 4",
      "status": "vacant",
      "market_rent": "1600.00"
    }
  ],
  "next_cursor": null
}

list_tenants

Tenants with email, phone, unit and current lease. Access: read. REST: GET /api/v1/doorloop/tenants. MCP: doorloop_read → list_tenants.

ParameterTypeRequiredDescription
searchstringnoMatch on name, email or phone.
property_idstringnoOnly this property. Property ID from list_properties.
cursorstringnoNext page cursor from the previous call.

Returns tenants with contact details and the lease they are on. Search matches name, email or phone. Use tenant_id from here in create_lease.

Example response:

{
  "tenants": [
    {
      "tenant_id": "tn_91c0e7",
      "name": "Dana Reed",
      "email": "dana@example.com",
      "phone": "+15555550123",
      "unit": "Unit 4",
      "lease_id": null
    }
  ],
  "next_cursor": null
}

list_leases

Leases with unit, tenants, rent, start and end dates and balance due. Access: read. REST: GET /api/v1/doorloop/leases. MCP: doorloop_read → list_leases.

ParameterTypeRequiredDescription
searchstringnoMatch on unit or tenant name.
statusenumnoactive or ended. Default: active.
ends_beforedatenoOnly leases ending on or before this date.
property_idstringnoOnly this property. Property ID from list_properties.
cursorstringnoNext page cursor from the previous call.

Returns leases with the unit, the tenants on them, monthly rent, dates and the balance due. Filter by status, by end date or by property. Use lease_id from here in the other lease tools. Search matches unit or tenant name.

Example response:

{
  "leases": [
    {
      "lease_id": "ls_64f1a9c2",
      "unit": "Unit 2B",
      "property": "Maple Court",
      "tenants": [
        "Marcus Hale"
      ],
      "rent": "1450.00",
      "start_date": "2026-01-01",
      "end_date": "2026-12-31",
      "balance_due": "1450.00"
    }
  ],
  "next_cursor": null
}

get_lease_transactions

Charges, payments and credits on a lease, oldest first, with the running balance. Access: read. REST: GET /api/v1/doorloop/leases/{lease_id}/transactions. MCP: doorloop_read → get_lease_transactions.

ParameterTypeRequiredDescription
lease_idstringyesLease ID from list_leases.
fromdatenoStart date. Default: lease start.
todatenoEnd date. Default: today.

Returns the ledger of one lease, oldest first: charges, payments and credits, each with a running balance. Use it to see whether a rent charge is still open before you add a fee or record a payment.

Example response:

{
  "lease_id": "ls_64f1a9c2",
  "transactions": [
    {
      "type": "charge",
      "date": "2026-10-01",
      "description": "Rent October 2026",
      "amount": "1450.00",
      "balance": "1450.00"
    }
  ],
  "balance_due": "1450.00"
}

list_tasks

Tasks and work orders with status, due date, property and assignee. Access: read. REST: GET /api/v1/doorloop/tasks. MCP: doorloop_read → list_tasks.

ParameterTypeRequiredDescription
statusstringnoOnly tasks with this status, as DoorLoop shows it.
property_idstringnoOnly this property. Property ID from list_properties.
cursorstringnoNext page cursor from the previous call.

Returns tasks and work orders, filtered by status or property. Each item has its subject, the property or unit it concerns, the due date and who it is assigned to.

Example response:

{
  "tasks": [
    {
      "task_id": "tk_20c8",
      "subject": "Fix hallway light",
      "property": "Maple Court",
      "unit": null,
      "status": "open",
      "due_date": "2026-10-15",
      "assignee": "Sam Ortiz"
    }
  ],
  "next_cursor": null
}

list_communications

The Communications Log: announcements and messages sent, with channel and delivery status. Access: read. REST: GET /api/v1/doorloop/communications. MCP: doorloop_read → list_communications.

ParameterTypeRequiredDescription
sincedatetimenoOnly entries sent after this time.
cursorstringnoNext page cursor from the previous call.

Returns entries from the Communications Log, newest first, with the channel, subject and delivery status. Use it after send_announcement to see who the announcement reached.

Example response:

{
  "communications": [
    {
      "communication_id": "cm_77f0",
      "subject": "Water shutoff Thursday",
      "channel": "email",
      "sent_at": "2026-10-11T09:02:00Z",
      "delivery": "delivered",
      "recipients": 12
    }
  ],
  "next_cursor": null
}

create_tenant

Add a tenant contact, ready to put on a lease. Sends nothing. Access: write. REST: POST /api/v1/doorloop/tenants. MCP: doorloop_write → create_tenant.

ParameterTypeRequiredDescription
first_namestringyesFirst name.
last_namestringyesLast name.
emailstringnoEmail address.
phonestringnoPhone number, E.164.

Adds one tenant contact. It sends nothing to the tenant and attaches no charge. It runs without asking first, because it reaches no one and the contact can be deleted in DoorLoop.

Example response:

{
  "tenant_id": "tn_91c0e7",
  "name": "Dana Reed",
  "email": "dana@example.com",
  "status": "created"
}

create_task

New task or work order for a property or unit. Access: write. REST: POST /api/v1/doorloop/tasks. MCP: doorloop_write → create_task.

ParameterTypeRequiredDescription
subjectstringyesShort title.
descriptionstringnoDetails for whoever does the work.
property_idstringnoOnly this property. Property ID from list_properties.
unit_idstringnoUnit it concerns.
due_datedatenoDue date.

Creates a task or work order with a subject, optional property or unit and a due date. It does not message anyone by itself. It runs without asking first, because it reaches no tenant and the task can be removed in DoorLoop.

Example response:

{
  "task_id": "tk_20c9",
  "subject": "Replace smoke detector, Unit 2B",
  "property": "Maple Court",
  "due_date": "2026-10-18",
  "status": "created"
}

create_lease

New lease on a unit with tenants, term, monthly rent and security deposit. Access: write, asks the user first. REST: POST /api/v1/doorloop/units/{unit_id}/leases. MCP: doorloop_write → create_lease.

ParameterTypeRequiredDescription
unit_idstringyesUnit ID from list_units.
tenant_idsstring[]yesTenant IDs from list_tenants or create_tenant.
start_datedateyesFirst day of the lease.
end_datedatenoLast day. Leave empty for month-to-month.
rentobjectyesamount and due_day of the recurring rent charge.
security_depositobjectnoamount and due_date.

Creates a lease on one unit in a single step: tenants, term, recurring rent with its due day and an optional security deposit. Leave end_date empty for a month-to-month lease. The lease creates charges on the ledger. By default you confirm each call; you can switch that off for this tool.

Example response:

{
  "lease_id": "ls_9e13b5",
  "unit": "Unit 4",
  "tenants": [
    "Dana Reed"
  ],
  "start_date": "2026-11-01",
  "end_date": "2027-10-31",
  "rent": {
    "amount": "1600.00",
    "due_day": 1
  },
  "security_deposit": {
    "amount": "1600.00",
    "due_date": "2026-11-01"
  },
  "status": "created"
}

post_lease_charge

One-time charge on a lease, such as a late fee. It shows on the tenant's balance. Access: write, asks the user first. REST: POST /api/v1/doorloop/leases/{lease_id}/charge. MCP: doorloop_write → post_lease_charge.

ParameterTypeRequiredDescription
lease_idstringyesLease ID from list_leases.
amountstringyesDecimal amount, e.g. "50.00".
datedateyesCharge date.
accountstringyesIncome account, as named in your DoorLoop chart of accounts.
memostringnoShown on the ledger.

Adds one charge to a lease ledger, for example a late fee or a utility bill. It raises the balance due. It does not change your late fee policy. By default you confirm each call; you can switch that off for this tool.

Example response:

{
  "charge_id": "ch_41b7",
  "lease_id": "ls_64f1a9c2",
  "amount": "50.00",
  "date": "2026-10-11",
  "account": "Late Fees",
  "balance_due": "1500.00",
  "status": "posted"
}

record_lease_payment

Record a payment received outside online payments and apply it to open charges. Access: write, asks the user first. REST: POST /api/v1/doorloop/leases/{lease_id}/payment. MCP: doorloop_write → record_lease_payment.

ParameterTypeRequiredDescription
lease_idstringyesLease ID from list_leases.
amountstringyesDecimal amount received.
datedateyesDate received.
methodstringyesPayment method as DoorLoop lists it, e.g. check or cash.
referencestringnoCheck number or other reference.

Records a payment on a lease, the same as Receive Payment in DoorLoop, and applies it to open charges. The response lists the charges it was applied to and the balance after. By default you confirm each call; you can switch that off for this tool.

Example response:

{
  "payment_id": "pm_8d2e71b0",
  "lease_id": "ls_64f1a9c2",
  "amount": "1450.00",
  "method": "check",
  "reference": "1042",
  "applied_to": [
    {
      "charge": "Rent October 2026",
      "amount": "1450.00"
    }
  ],
  "balance_due": "0.00"
}

issue_lease_credit

Credit a lease, such as a rent concession, lowering the tenant's balance. Access: write, asks the user first. REST: POST /api/v1/doorloop/leases/{lease_id}/credit. MCP: doorloop_write → issue_lease_credit.

ParameterTypeRequiredDescription
lease_idstringyesLease ID from list_leases.
amountstringyesDecimal amount.
datedateyesCredit date.
memostringnoReason, shown on the ledger.

Adds a credit to a lease ledger, which lowers the balance due. Use the memo to record the reason. By default you confirm each call; you can switch that off for this tool.

Example response:

{
  "credit_id": "cr_19a4",
  "lease_id": "ls_64f1a9c2",
  "amount": "100.00",
  "date": "2026-10-11",
  "balance_due": "1350.00",
  "status": "posted"
}

send_announcement

Announcement to tenants by email, text or tenant portal. Texts use announcement credits. Access: write, asks the user first. REST: POST /api/v1/doorloop/announcements. MCP: doorloop_write → send_announcement.

ParameterTypeRequiredDescription
subjectstringyesAnnouncement title.
bodystringyesMessage text.
property_idsstring[]noOnly tenants in these properties. Default: all.
channelsstring[]yesAny of email, text, portal.

Sends an announcement to tenants of the full portfolio or of chosen properties. Email and portal posts are free. Text messages use announcement credits (1 per 160 characters) and are capped at 800 characters. Announcements need DoorLoop's Pro or Premium plan. By default you confirm each call; you can switch that off for this tool.

Example response:

{
  "communication_id": "cm_77f0",
  "subject": "Water shutoff Thursday",
  "channels": [
    "email",
    "text"
  ],
  "recipients": 12,
  "status": "sent"
}

How do I connect DoorLoop to ChatGPT, Claude, Cursor or Codex?

Connecting DoorLoop takes three steps: sign up, sign in to DoorLoop once in your Cloud Browser and enable it for agents, then add Cotlet to ChatGPT or Claude as a connector, with no API key, or add one MCP server or call the REST API with an API key.

Connect DoorLoop to your agent.

  1. Create an account Sign up and add DoorLoop in the console. ChatGPT and Claude need no API key: you sign in to Cotlet when you add the connector. Code editors and scripts take an API key from the console.

  2. Sign in to DoorLoop in your Cloud Browser Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to DoorLoop there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

  3. Add Cotlet to ChatGPT, Claude or your agent Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

    ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:

claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

Cursor:

{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
  1. Ask your agent Ask in plain words. Your agent finds the DoorLoop tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.
Record today's rent checks in DoorLoop: Unit 2B Marcus Hale $1,450 check 1042, Unit 3A Priya Shah $1,500 cash, Unit 6 Leo Brandt $1,640 by Zelle. Skip anything already entered and tell me what is still owed.

Call DoorLoop from your scripts.

  1. Export your API key Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.
export COTLET_API_KEY="cotlet_..."
  1. Call a tool Every tool is an endpoint under /api/v1/doorloop with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.
curl -X POST https://cotlet.dev/api/v1/doorloop/leases/ls_64f1a9c2/payment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":"1450.00","date":"2026-10-11","method":"check","reference":"1042"}'
  1. Read the result You get plain JSON back, ready for your script. A failed call costs nothing.
{
  "payment_id": "pm_8d2e71b0",
  "lease_id": "ls_64f1a9c2",
  "amount": "1450.00",
  "method": "check",
  "reference": "1042",
  "applied_to": [
    {
      "charge": "Rent October 2026",
      "amount": "1450.00"
    }
  ],
  "balance_due": "0.00"
}

How to use the DoorLoop REST API

Create your Cotlet API key

Create a Cotlet API key with access to DoorLoop and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect DoorLoop in Cotlet and enable it for agents. Account access: Your own DoorLoop account (a user who can manage leases, payments and communications).

Make your first DoorLoop API request

REST:

curl https://cotlet.dev/api/v1/doorloop/properties \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read properties and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "doorloop",
  "tool": "list_properties",
  "result": {
    "properties": [
      {
        "property_id": "pr_3a91c7",
        "name": "Maple Court",
        "address": "120 Maple St, Springfield",
        "type": "Multi-family",
        "units": 12
      }
    ],
    "next_cursor": null
  }
}

Returns the properties in your DoorLoop account, with address and number of units. Search matches the property name or address.

Use the property_id of each item in the other tools.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

DoorLoop workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestLeases with unit, tenants, rent, start and end dates and balance due. Use list_leases in your configured property report.
MakeHTTP > Make a requestCharges, payments and credits on a lease, oldest first, with the running balance. Use get_lease_transactions in your configured property report.
Python or Node.jsREST APITasks and work orders with status, due date, property and assignee. Use list_tasks in your configured property report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads DoorLoop; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Why use Cotlet for DoorLoop?

Built for agents

  • One MCP server for every app you connect.
  • The same tools as a REST API for scripts and cron jobs.
  • Works with ChatGPT, Claude, Claude Code, Codex and Cursor.

Your login stays yours

  • You sign in to DoorLoop yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
  • A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
  • The model never sees a login.
  • No stored passwords, no MFA bypass.

You stay in control

  • Scope each API key: its apps, its tools, read only or read and write.
  • Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
  • Every background request listed in your Background activity. Disable for agents in one click.

Kept working for you

  • We test every integration every 6 hours.
  • When DoorLoop changes, the tool pauses until we fix it.
  • Failed calls cost nothing.

Is it safe to connect DoorLoop to Cotlet?

Yes. You sign in to DoorLoop yourself, in your own Cloud Browser, and we never save your password. Your agents only get DoorLoop once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

  • A+ on Qualys SSL Labs: Encryption in transit: TLS setup and certificates, on all four server addresses. Live result
  • A+ on securityheaders.com: Browser protections sent with every page, all six headers present. Live result
  • A+ on Mozilla Observatory: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. Live result
  • Clean on Sucuri SiteCheck: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. Live result

How Cotlet protects your access

Common concerns

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is this an official DoorLoop integration?

No, Cotlet is independent of DoorLoop. DoorLoop's own API comes only with a paid plan. Cotlet works through your own DoorLoop account, the way you use DoorLoop in the browser, so you need no partner approval and no developer setup.

What about client data and GDPR?

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

Can I start with read only?

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

Is it reliable?

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

How do I stop?

Press Disable for agents next to DoorLoop in your console: your agents lose access at once and you stay signed in. Signing out of DoorLoop in the browser works too, and Reset browser deletes the whole profile.

Is there a DoorLoop MCP server on GitHub?

Yes. Community DoorLoop CLIs and MCP servers exist on GitHub, usually maintained by one person. They need a DoorLoop API token, so they only work if your account has API access. You install and fix them yourself; Cotlet hosts and maintains the same for you, and works in your signed-in session.

GitHub MCP serverCotlet
SetupGet API access from DoorLoop, create a token, install the tool, add it to each MCP clientSign up, sign in to DoorLoop once, add one MCP server or API key
When DoorLoop changesIt breaks until you or the maintainer fix itOur team tests it daily and fixes it for you; failed calls are free
Your DoorLoop accessAn API token in a file or environment variable on your computerSigned in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click
When access expiresTools fail until you replace the tokenYour Cloud Browser keeps you signed in; if DoorLoop logs you out, your agent gets a link to sign in again
UpkeepYou update, monitor and debug it yourselfNothing to host or update
Where it runsYour computer, while it is onHosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule
PriceFree, paid for with your timeFree 7-day trial, then pay-as-you-go credit packs, no subscription

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when DoorLoop changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want your sign-in to stay on your own computer
  • you only need it now and then, from one MCP client

How much does the DoorLoop API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the DoorLoop API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 to 100 credits (10 for most tools, about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

CreditsPrice, one timeCalls at 10 creditsPer 1,000 credits
5,000$29500$5.80
15,000$791,500$5.27
32,000$1493,200$4.66
60,000$2496,000$4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header. See full pricing

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own DoorLoop account.

  • Company details: Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. Terms of service
  • Your sign-in: You sign in to DoorLoop yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get DoorLoop only after you enable it. When DoorLoop signs you out, your agent gives you a link to sign in again. Security
  • Revoking access: Press Disable for agents next to DoorLoop, sign out of DoorLoop in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
  • What we never do: Store passwords or bypass MFA.
  • DoorLoop's terms: You use your own DoorLoop account and stay responsible for following DoorLoop's terms. Cotlet is independent and not affiliated with DoorLoop. Terms
  • Contact: Questions about the company, security or an app: contact@cotlet.dev

Also listed on: Odel, mcpbeat

DoorLoop API and MCP: questions

How do I get access?

Sign up free, open DoorLoop in the console and press Activate. Then you create your API key and connect DoorLoop there.

Do I need to be technical?

No. You sign in to DoorLoop once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is it safe to connect DoorLoop to Cotlet?

Yes. You sign in to DoorLoop yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get DoorLoop once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Is a hosted server safer than a local one? My DoorLoop sign-in would leave my computer.

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your DoorLoop cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

Why does Cotlet send requests instead of clicking in my browser?

To be fast, Cotlet doesn't click through DoorLoop's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. DoorLoop sees the same browser and IP you signed in with, and every request is listed in your Background activity.

What if someone gets my Cotlet API key?

The key holds no DoorLoop login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

Why a signed-in browser and not OAuth, like other integration platforms?

DoorLoop offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

How do I connect DoorLoop to ChatGPT or Claude?

Sign up at cotlet.dev, log in to DoorLoop once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your DoorLoop account through Cotlet, in their phone apps too.

What can ChatGPT do in DoorLoop?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in DoorLoop: record check and cash rent payments; send announcements to tenants of a property; set up a new lease. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need DoorLoop's Premium plan or API access?

No. Cotlet works in your own DoorLoop account and does not use the API or Zapier, which DoorLoop lists on Premium. Announcements need Pro or Premium, because DoorLoop does not offer them on Starter.

Does a text announcement cost extra?

Yes, in DoorLoop. Text messages use announcement credits, 1 credit per 160 characters, while email and tenant portal posts are free. Cotlet does not add to that; it bills only its own credits per call.

Can my agent post or send messages in DoorLoop without asking me?

No. Every call to create_lease, post_lease_charge, record_lease_payment, issue_lease_credit or send_announcement waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_tenant and create_task run without asking, because they send nothing to anyone and one call undoes it.

Can I use the DoorLoop API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/doorloop from the HTTP Request node.

Can I use the DoorLoop API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.