# Buildium MCP by usefulapi

> Buildium MCP by usefulapi is an MCP server. Read Buildium properties, units, leases, tenants, balances and bills; manage work orders. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/buildium/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/buildium
- **MCP Registry name:** io.usefulapi/buildium
- **Listing updated:** 2026-11-13

## About

Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http buildium https://buildium.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://buildium.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "buildium": {
      "url": "https://buildium.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "buildium": {
      "type": "http",
      "url": "https://buildium.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "buildium": {
      "serverUrl": "https://buildium.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "buildium": {
      "type": "http",
      "url": "https://buildium.usefulapi.io/mcp"
    }
  }
}
```

## Tools

- `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.
- `buildium_get_rental_property`: Fetch one rental property by id. Buildium: GET /v1/rentals/{propertyId}.
- `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.
- `buildium_get_rental_unit`: Fetch one rental unit by id. Buildium: GET /v1/rentals/units/{unitId}.
- `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.
- `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 returned lease field, e.g. LastUpdatedDateTime desc,Id asc or LeaseToDate asc,Id asc; nested fields, Name, Rent and LastUpdated are not supported. Buildium: GET /v1/l
- `buildium_get_lease`: Fetch one lease by id, including tenants, cosigners, account details and move-out data. Buildium: GET /v1/leases/{leaseId}.
- `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/outstandingbalances.
- `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.
- `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.
- `buildium_get_tenant`: Fetch one rental tenant by id. Buildium: GET /v1/leases/tenants/{tenantId}.
- `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.
- `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 with entity_id (Rental for a property); statuses refer to the associated task. Dates must be YYYY-MM-DD, and each from value must be at most its to value. orderby
- `buildium_get_work_order`: Fetch one work order by id. Buildium: GET /v1/workorders/{workOrderId}.
- `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.
- `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.
- `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 Unpaid. Paid bills: paid_status Paid with paid_date_from and paid_date_to. All bills of a property: one call of each. paid_status Any sends no status filter and 
- `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.
- `buildium_list_associations`: List community/HOA associations with address, manager, reserve, fiscal year and operating bank account. Buildium: GET /v1/associations.
- `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 items are optional (quantity x unit price, optional GL account). Buildium: POST /v1/workorders.
- `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_items REPLACES all existing line items. Status/priority/due date live on the linked task. Buildium: GET then PUT /v1/workorders/{workOrderId}.
- `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.
- `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 the fields you pass. Buildium: GET then PUT /v1/tasks/todorequests/{toDoTaskId}.

## FAQ

### How do I add Buildium MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http buildium https://buildium.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/buildium-mcp-by-usefulapi
