Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
DoorLoop MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read DoorLoop properties, units, leases, tenants and payments; create tasks and task updates.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http doorloop-mcp-by-usefulapi https://doorloop.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# doorloop_get_current_user, doorloop_list_properties, doorloop_get_property and 18 more
DoorLoop MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 707 servers
usefulapi707 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http doorloop-mcp-by-usefulapi https://doorloop.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the DoorLoop user that created this API key. Good first call to confirm the connection. DoorLoop API: GET /users/me.
No parameter schema on file.
List properties (buildings) with address, class and portfolio. DoorLoop API: GET /properties.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | Filter by property name. |
| group | string | no | Filter by portfolio id. |
| class | string | no | Filter by property class. |
| owner | string | no | Filter by owner id. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
Get one property by id. DoorLoop API: GET /properties/{propertyId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property_id | string | yes | The property_id (from the matching list tool). |
List rental units with rent, bedrooms and status. Without filter_active the API returns active units only. DoorLoop API: GET /units.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| owner | string | no | Filter by owner id. |
| text | string | no | Filter by unit name. |
| active | string | no | Which units to return by status. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
Get one unit by id. DoorLoop API: GET /units/{unitId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| unit_id | string | yes | The unit_id (from the matching list tool). |
List leases with dates, rent, status and outstanding balance. Use calculatedStatus or situation to find at-risk or late leases. DoorLoop API: GET /leases.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| owner | string | no | Filter by owner id. |
| unit | string | no | Filter by unit id. |
| tenant | string | no | Filter by tenant id. |
| text | string | no | Filter by lease name. |
| start_date_from | string | no | Lease start date from (yyyy-mm-dd). |
| start_date_to | string | no | Lease start date to (yyyy-mm-dd). |
| end_date_from | string | no | Lease end date from (yyyy-mm-dd). |
| end_date_to | string | no | Lease end date to (yyyy-mm-dd). |
| propertyClass | string | no | Filter by property class. |
| outstandingBalanceGreaterThan | number | no | Only leases with an outstanding balance above this amount. |
| status | string | no | Filter by lease status. |
| term | string | no | Filter by lease term. |
| calculatedStatus | string | no | Collections stage. |
| situation | string | no | Lease situation from balance and lifecycle. |
| evictionPending | boolean | no | Only leases with a pending eviction. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
Get one lease by id. DoorLoop API: GET /leases/{leaseId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lease_id | string | yes | The lease_id (from the matching list tool). |
List tenants joined to their leases, with move-in and move-out dates. Best way to map tenants to leases. DoorLoop API: GET /leases/tenants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| lease | string | no | Filter by lease id. |
| status | string | no | Occupancy status. |
| text | string | no | Filter by tenant name or email. |
| movedInAt_from | string | no | Move-in date from (yyyy-mm-dd). |
| movedInAt_to | string | no | Move-in date to (yyyy-mm-dd). |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List tenants and prospects with contact details. DoorLoop API: GET /tenants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| lease | string | no | Filter by lease id. |
| unit | string | no | Filter by unit id. |
| text | string | no | Filter by tenant name or email. |
| type | string | no | Filter by tenant type. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
Get one tenant by id. DoorLoop API: GET /tenants/{tenantId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tenant_id | string | yes | The tenant_id (from the matching list tool). |
List rent payments received on leases. DoorLoop API: GET /lease-payments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lease | string | no | Filter by lease id. |
| property | string | no | Filter by property id. |
| owner | string | no | Filter by owner id. |
| date_from | string | no | Payment date from (yyyy-mm-dd). |
| date_to | string | no | Payment date to (yyyy-mm-dd). |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List charges (rent, fees, late fees) billed on leases. Use totalBalanceGreaterThan to find unpaid charges. DoorLoop API: GET /lease-charges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lease | string | no | Filter by lease id. |
| property | string | no | Filter by property id. |
| owner | string | no | Filter by owner id. |
| unit | string | no | Filter by unit id. |
| date_from | string | no | Charge date from (yyyy-mm-dd). |
| date_to | string | no | Charge date to (yyyy-mm-dd). |
| totalBalanceGreaterThan | number | no | Only charges with a remaining balance above this amount. |
| lateFeeCharges | boolean | no | Only late-fee charges. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List tasks, work orders, tenant requests and owner requests. DoorLoop API: GET /tasks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| propertyGroup | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| unit | string | no | Filter by unit id. |
| type | string | no | Filter by task type. |
| status | string | no | Filter by task status. |
| createdAt_from | string | no | Created from (yyyy-mm-dd). |
| createdAt_to | string | no | Created to (yyyy-mm-dd). |
| dueDate_from | string | no | Due date from (yyyy-mm-dd). |
| dueDate_to | string | no | Due date to (yyyy-mm-dd). |
| assignedToUser | string | no | Filter by user id or "unassigned". |
| text | string | no | Filter by subject, description or reference. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
Get one task by id. DoorLoop API: GET /tasks/{taskId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | The task_id (from the matching list tool). |
List property owners. DoorLoop API: GET /owners.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Filter by portfolio id. |
| property | string | no | Filter by property id. |
| active | boolean | no | Filter by active or inactive. |
| text | string | no | Filter by owner name or email. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List maintenance vendors. DoorLoop API: GET /vendors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | no | Filter by property id. |
| active | boolean | no | Filter by active or inactive. |
| insurance_expires_before | string | no | Insurance expires before (yyyy-mm-dd). |
| openBalance | boolean | no | Only vendors with an open balance. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List portfolios (property groups). DoorLoop API: GET /property-groups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List DoorLoop users of the company. DoorLoop API: GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
List chart-of-accounts entries. DoorLoop API: GET /accounts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Account type, for example REVENUE_INCOME or EXPENSE_EXPENSE. |
| leaseChargeItem | boolean | no | Only lease charge items. |
| page_number | integer | no | Page number (default 1). |
| page_size | integer | no | Results per page (default 50, max 1000). |
| sort_by | string | no | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | no | Sort in descending order (default false). |
WRITE: create a task in DoorLoop. INTERNAL_TASK needs requested_by_user, TENANT_REQUEST needs requested_by_tenant, OWNER_REQUEST needs requested_by_owner, WORK_ORDER needs assigned_to_vendor. Notifications are off unless you set them. Each call creates a new task. DoorLoop API: POST /tasks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| subject | string | yes | Task subject. |
| status | string | yes | Initial status. |
| description | string | no | — |
| due_date | string | no | Due date (yyyy-mm-dd). |
| priority | string | no | — |
| property | string | no | Property id. |
| unit | string | no | Unit id. |
| requested_by_user | string | no | User id. Required for INTERNAL_TASK. |
| requested_by_tenant | string | no | Tenant id. Required for TENANT_REQUEST. |
| requested_by_owner | string | no | Owner id. Required for OWNER_REQUEST. |
| assigned_to_users | array | no | User ids to assign. |
| assigned_to_vendor | string | no | Vendor id. Required for WORK_ORDER. |
| instructions_to_vendor | string | no | — |
| notify_tenant | boolean | no | Notify the tenant (TENANT_REQUEST only). Default: no. |
| notify_assignees | boolean | no | Notify the assigned users. Default: no. |
WRITE: post a message on an existing task and optionally change its status, priority, due date or assignees. Each call adds a new update. Notifications are off unless you set them. DoorLoop API: POST /tasks/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | Task id (from doorloop_list_tasks). |
| message | string | yes | Update message. |
| status | string | no | — |
| priority | string | no | — |
| due_date | string | no | New due date (yyyy-mm-dd). |
| assigned_to_users | array | no | User ids to assign. |
| notify_tenant | boolean | no | Notify the tenant. Default: no. |
| notify_assignees | boolean | no | Notify the assigned users. Default: no. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DoorLoop MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.7.3 · scanned 11 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest52fa19e0dfef0bc2e927d6ab6c1be7bd21b14bf150c849e3cfdd2e68342cd2cc
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| doorloop_get_current_user | no tags | |
| doorloop_list_properties | no tags | |
| doorloop_get_property | no tags | |
| doorloop_list_units | no tags | |
| doorloop_get_unit | no tags | |
| doorloop_list_leases | no tags | |
| doorloop_get_lease | no tags | |
| doorloop_list_lease_tenants | no tags | |
| doorloop_list_tenants | no tags | |
| doorloop_get_tenant | no tags | |
| doorloop_list_lease_payments | no tags | |
| doorloop_list_lease_charges | no tags | |
| doorloop_list_tasks | no tags | |
| doorloop_get_task | no tags | |
| doorloop_list_owners | no tags | |
| doorloop_list_vendors | no tags | |
| doorloop_list_portfolios | no tags | |
| doorloop_list_users | no tags | |
| doorloop_list_accounts | no tags | |
| doorloop_create_task | state-write | state-write: declares destructiveHint: true |
| doorloop_post_task_update | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest52fa19e0dfef0bc2
Scanned2026-11-11
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.3.
1.7.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DoorLoop MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.