Buildium MCP by usefulapi is an MCP server with 23 tools an agent can call, among them buildium_create_todo_task, buildium_create_work_order, buildium_get_lease. It answers at https://buildium.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
buildium_create_todo_task | Create an internal to-do task assigned to a staff user, optionally tied to a property/unit and category, with a due date. Buildium: POST /v1/tasks/todorequests. Inputs: title, assigned_to_user_id, priority, status, description, due_date |
buildium_create_work_order | Create a work order for a vendor. Attach it to an existing task (task_id) or create a new task with it (task: title, priority, status, assigned staff user, optional due date/property/unit). vendor_id and entry_allowed are required. Line ite Inputs: vendor_id, entry_allowed, title, work_details, invoice_number, chargeable_to |
buildium_get_lease | Fetch one lease by id, including tenants, cosigners, account details and move-out data. Buildium: GET /v1/leases/{leaseId}. Inputs: lease_id |
buildium_get_rental_property | Fetch one rental property by id. Buildium: GET /v1/rentals/{propertyId}. Inputs: property_id |
buildium_get_rental_unit | Fetch one rental unit by id. Buildium: GET /v1/rentals/units/{unitId}. Inputs: unit_id |
buildium_get_tenant | Fetch one rental tenant by id. Buildium: GET /v1/leases/tenants/{tenantId}. Inputs: tenant_id |
buildium_get_work_order | Fetch one work order by id. Buildium: GET /v1/workorders/{workOrderId}. Inputs: work_order_id |
buildium_list_applicants | List rental applicants with contact details, status and their applications. Filter by application status, unit, name, email, submission date or entity. Buildium: GET /v1/applicants. Inputs: entity_type, entity_id, application_statuses, unit_ids, name, email |
buildium_list_associations | List community/HOA associations with address, manager, reserve, fiscal year and operating bank account. Buildium: GET /v1/associations. Inputs: ids, location, status, operating_bank_account_ids, last_updated_from, last_updated_to |
buildium_list_bills | List vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines. Read-only. paid_status is required: Buildium rejects a bill list without a paid filter. Open bills: paid_status U Inputs: entity_type, entity_id, vendor_id, reference_number, paid_status, paid_date_from |
buildium_list_gl_accounts | List the chart of accounts: GL accounts with number, name, type/subtype, sub-accounts and bank/credit-card flags. Useful for finding the gl_account_id for work order line items. Buildium: GET /v1/glaccounts. Inputs: account_types, limit, offset, orderby |
buildium_list_lease_transactions | Read a lease's ledger: charges, payments, credits, refunds, deposits and other transactions with date, type, total amount and journal lines. Read-only — this server never posts to a ledger. Buildium: GET /v1/leases/{leaseId}/transactions. Inputs: lease_id, transaction_date_from, transaction_date_to, transaction_types, limit, offset |
buildium_list_leases | List leases with unit, dates, lease type/status, current tenants, rent/deposit account details and eviction flag. Filter by property, owner, unit number, tenant name, dates, lease type or status (Active/Past/Future). Sort by a scalar return Inputs: property_ids, rental_owner_ids, unit_number, tenant_name, lease_date_from, lease_date_to |
buildium_list_outstanding_balances | Delinquency report: leases that owe money, with aged buckets (0-30, 31-60, 61-90, 90+ days), total balance, past-due-email and eviction-pending dates. Leases with zero or credit balances are not returned. Buildium: GET /v1/leases/outstandin Inputs: entity_type, entity_id, lease_statuses, lease_ids, past_due_email, balance_duration |
buildium_list_rental_owners | List rental owners (the landlords you manage for) with contact details, management-agreement dates and the property ids they own. Buildium: GET /v1/rentals/owners. Inputs: property_ids, status, agreement_days_remaining, owner_name, phone, last_updated_from |
buildium_list_rental_properties | List rental properties (buildings) with address, unit count, type/subtype and manager. Filter by location (city/state contains), type, subtype, status, rental owner or property ids. Buildium: GET /v1/rentals. Inputs: location, types, subtypes, status, rental_owner_ids, property_ids |
buildium_list_rental_units | List rental units with unit number, bedrooms/bathrooms, size, market rent and whether each unit is listed or occupied. Filter by property. Buildium: GET /v1/rentals/units. Inputs: property_ids, last_updated_from, last_updated_to, limit, offset, orderby |
buildium_list_tasks | List all tasks/requests — contact requests, resident requests, rental owner requests and to-dos — with category, property, unit, requester, assignee, status, priority and due date. Buildium: GET /v1/tasks. Inputs: entity_type, entity_id, statuses, type, unit_id, unit_agreement_id |
buildium_list_tenants | List rental tenants with contact details, emergency contact, address and leases. Filter by name, email, phone, unit number, property, owner, unit ids or lease term status. Buildium: GET /v1/leases/tenants. Inputs: name, email, phone, unit_number, property_ids, rental_owner_ids |
buildium_list_vendors | List vendors (contractors, suppliers) with contact details, category, insurance and default expense GL account. Filter by name, email, phone, website, status or insurance expiration. Buildium: GET /v1/vendors. Inputs: name, email, phone, website, status, insurance_expiration |
buildium_list_work_orders | List work orders with title, status, priority, due date, vendor, amount, line items, linked task and bill ids. Filter by entity, status, priority, task type, unit, vendor, assignee, dates, amount, billed flag or title. Supply entity_type wi Inputs: entity_type, entity_id, statuses, type, unit_id, unit_agreement_id |
buildium_update_todo_task | Update a to-do task — change status (e.g. mark Completed), priority, assignee, due date, title or category, optionally with an update message. Buildium's PUT replaces the whole record, so this reads the current task first and only changes t Inputs: todo_task_id, title, status, priority, assigned_to_user_id, due_date |
buildium_update_work_order | Update a work order's details. Buildium's PUT replaces the whole record, so this reads the current work order first and only changes the fields you pass — everything else (including line items and entry contacts) is preserved. Passing line_ Inputs: work_order_id, title, work_details, invoice_number, chargeable_to, entry_allowed |
Every block below points at https://buildium.usefulapi.io/mcp. Pick your client and copy.
claude mcp add --transport http buildium-mcp-by-usefulapi https://buildium.usefulapi.io/mcp
{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://buildium.usefulapi.io/mcp"]
}
}
}{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
}{
"servers": {
"buildium-mcp-by-usefulapi": {
"type": "http",
"url": "https://buildium.usefulapi.io/mcp"
}
}
}{
"context_servers": {
"buildium-mcp-by-usefulapi": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"serverUrl": "https://buildium.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
}name: Buildium MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
- name: Buildium MCP by usefulapi
type: streamable-http
url: https://buildium.usefulapi.io/mcp{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"httpUrl": "https://buildium.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"type": "http",
"url": "https://buildium.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"buildium-mcp-by-usefulapi": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbuildium.usefulapi.io%2Fmcp&type=streamable_http&id=buildium-mcp-by-usefulapi&name=Buildium%20MCP%20by%20usefulapi
It answered our last check on 15 November 2026 in 329 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by usefulapi.io and served from buildium.usefulapi.io, the vendor's own domain: https://buildium.usefulapi.io/mcp.
23, as returned by the server's own tools/list on 18 November 2026: buildium_create_todo_task, buildium_create_work_order, buildium_get_lease, buildium_get_rental_property, buildium_get_rental_unit, buildium_get_tenant, buildium_get_work_order, buildium_list_applicants, and 15 more.
It answered our last check on 15 November 2026 in 329 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://buildium.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.usefulapi. Endpoint host: buildium.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:buildium.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.