Buildium API and MCP server Let your AI agent work your Buildium rent roll.

ToolWhat it doesAccess

• list_properties Your rental properties with address and unit count. read

  Returns the rental properties in your Buildium 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.

  MCP callbuildium_read → list_properties

  REST endpointGET https://cotlet.dev/api/v1/buildium/properties

  Parameters

  Parameters: list_properties

  Name	Type	Description
  search string	string	Match on property name or address.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "properties": [
      {
        "property_id": "48213",
        "name": "Maple Court",
        "address": "120 Maple St, Springfield",
        "units": 12
      }
    ],
    "next_cursor": null
  }

• list_leases Leases from the Rent roll with unit, tenants, rent, dates and balance. read

  Returns leases as Buildium's Rentals > Rent roll shows them: unit, tenants, monthly rent, start and end dates and the current balance. Search matches unit or tenant name. Use lease_id from here in the ledger and payment tools.

  MCP callbuildium_read → list_leases

  REST endpointGET https://cotlet.dev/api/v1/buildium/leases

  Parameters

  Parameters: list_leases

  Name	Type	Description
  search string	string	Match on unit or tenant name.
  status enum	enum	active, future or past. Default: active.
  property_id string	string	Only this property. Property ID from list_properties.
  cursor string	string	Next page cursor from the previous call.

  Example response

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

• list_outstanding_balances Leases with an outstanding balance as of today, largest first. read

  Returns what Buildium's Rentals > Outstanding balances page shows: each lease with a balance today, the tenants and the amount. Sorted by balance, largest first. Filter by property or by a minimum amount.

  MCP callbuildium_read → list_outstanding_balances

  REST endpointGET https://cotlet.dev/api/v1/buildium/outstanding-balances

  Parameters

  Parameters: list_outstanding_balances

  Name	Type	Description
  property_id string	string	Only this property. Property ID from list_properties.
  min_balance string	string	Only balances at or above this decimal amount.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "balances": [
      {
        "lease_id": "90517",
        "property": "Maple Court",
        "unit": "2B",
        "tenants": [
          "Marcus Hale"
        ],
        "balance": "1450.00"
      },
      {
        "lease_id": "90522",
        "property": "Maple Court",
        "unit": "7",
        "tenants": [
          "Rosa Lin"
        ],
        "balance": "320.00"
      }
    ],
    "total": "1770.00",
    "next_cursor": null
  }

• get_lease_ledger Charges, payments and credits on one lease, oldest first, with the running balance. read

  Returns the ledger from the lease's Financials tab, oldest first: charges, payments and credits, each with the running balance. Use it before recording a payment to catch one a colleague already entered.

  MCP callbuildium_read → get_lease_ledger

  REST endpointGET https://cotlet.dev/api/v1/buildium/leases/{lease_id}/ledger

  Parameters

  Parameters: get_lease_ledger

  Name	Type	Description
  lease_id string required	string	Lease ID from list_leases or list_outstanding_balances.
  from date	date	Start date. Default: 90 days ago.
  to date	date	End date. Default: today.

  Example input

  {
    "lease_id": "lease_8c41d2"
  }

  Example response

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

• get_delinquent_tenants_report Buildium's Delinquent tenants report: who owes what as of a date, with the last payment. read

  Runs the Delinquent tenants report from the Reports menu and returns its rows: tenant, unit, balance and last payment date as of the date you give. Resident status picks current, future or former tenants. Balance detail by GL account only comes back for a single property, as in Buildium.

  MCP callbuildium_read → get_delinquent_tenants_report

  REST endpointGET https://cotlet.dev/api/v1/buildium/delinquent-tenants-report

  Parameters

  Parameters: get_delinquent_tenants_report

  Name	Type	Description
  as_of date	date	Balances as of this date. Default: today.
  resident_status enum	enum	current, future or former. Default: current.
  property_id string	string	Only this property. Property ID from list_properties.

  Example response

  {
    "as_of": "2026-10-27",
    "rows": [
      {
        "tenant": "Marcus Hale",
        "property": "Maple Court",
        "unit": "2B",
        "balance": "1450.00",
        "last_payment": "2026-09-03"
      }
    ],
    "total": "1450.00"
  }

• record_lease_payment Record a payment received by check, cash or money order on a lease ledger. writeasks first

  Records a payment the same way as Receive payment on the lease ledger. Use the date the money was in hand, because Buildium charges late fees from the ledger dates. Buildium applies the money to the charge with the largest balance first unless the lease has its own allocation. The response lists the charges paid and the balance after. By default you confirm each call; you can switch that off for this tool.

  MCP callbuildium_write → record_lease_payment

  REST endpointPOST https://cotlet.dev/api/v1/buildium/leases/{lease_id}/payment

  Parameters

  Parameters: record_lease_payment

  Name	Type	Description
  lease_id string required	string	Lease ID from list_leases or list_outstanding_balances.
  amount string required	string	Decimal amount received, e.g. "1450.00".
  date date required	date	Date the payment was received.
  method enum required	enum	check, cash, money_order or cashiers_check.
  reference string	string	Check number or other reference.
  memo string	string	Shown on the ledger.

  Example input

  {
    "lease_id": "90517",
    "amount": "1450.00",
    "date": "2026-10-27",
    "method": "check",
    "reference": "1042"
  }

  Example response

  {
    "payment_id": "7781204",
    "lease_id": "90517",
    "amount": "1450.00",
    "date": "2026-10-27",
    "method": "check",
    "reference": "1042",
    "applied_to": [
      {
        "charge": "Rent October 2026",
        "amount": "1450.00"
      }
    ],
    "balance": "0.00"
  }

• post_lease_charge One-time charge on a lease, such as a utility bill or a repair the tenant pays. writeasks first

  Adds one charge to a lease ledger against a GL account from your chart of accounts. It raises the tenant's balance and shows in the Resident Center. It does not change your late fee rules. By default you confirm each call; you can switch that off for this tool.

  MCP callbuildium_write → post_lease_charge

  REST endpointPOST https://cotlet.dev/api/v1/buildium/leases/{lease_id}/charge

  Parameters

  Parameters: post_lease_charge

  Name	Type	Description
  lease_id string required	string	Lease ID from list_leases or list_outstanding_balances.
  amount string required	string	Decimal amount, e.g. "45.00".
  date date required	date	Charge date.
  gl_account string required	string	Income GL account as named in your Buildium chart of accounts.
  memo string	string	Shown on the ledger.

  Example input

  {
    "lease_id": "lease_8c41d2",
    "amount": "45.00",
    "date": "2026-10-01",
    "gl_account": "gl account"
  }

  Example response

  {
    "charge_id": "7781230",
    "lease_id": "90517",
    "amount": "45.00",
    "date": "2026-10-27",
    "gl_account": "Utility income",
    "balance": "45.00",
    "status": "posted"
  }

ToolWhat it doesAccess

• list_text_messages Two-way text conversations with residents from Communication > Messages. read

  Returns text threads with residents, newest message first, with the resident, their unit and the last messages. unanswered_only keeps threads where the resident wrote last. Only residents who opted in to texts appear here.

  MCP callbuildium_read → list_text_messages

  REST endpointGET https://cotlet.dev/api/v1/buildium/text-messages

  Parameters

  Parameters: list_text_messages

  Name	Type	Description
  unanswered_only boolean	boolean	Only threads where the resident wrote last. Default: false.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "threads": [
      {
        "thread_id": "tx_5521",
        "resident": "Rosa Lin",
        "unit": "Maple Court 7",
        "last_from": "resident",
        "last_at": "2026-10-27T08:14:00Z",
        "last_message": "Is the plumber still coming today?"
      }
    ],
    "next_cursor": null
  }

• send_text_message Text up to 10 residents who opted in, each as a separate message. writeasks first

  Sends a text from Communication > Messages to one or more residents, at most 10 per call. Buildium sends each message separately, so residents do not see each other. Residents who have not opted in are skipped and listed in the response. By default you confirm each call; you can switch that off for this tool.

  MCP callbuildium_write → send_text_message

  REST endpointPOST https://cotlet.dev/api/v1/buildium/text-messages

  Parameters

  Parameters: send_text_message

  Name	Type	Description
  residents string[] required	string[]	Resident names or IDs, at most 10.
  message string required	string	Message text.

  Example input

  {
    "residents": [
      "residents"
    ],
    "message": "message"
  }

  Example response

  {
    "sent": [
      {
        "resident": "Marcus Hale",
        "unit": "Maple Court 2B"
      }
    ],
    "skipped_not_opted_in": [],
    "status": "sent"
  }

• send_announcement Announcement to the residents of chosen properties by email, text and Resident Center. writeasks first

  Publishes an announcement to the residents of the properties you choose. The subject shows in email and in the Resident Center and is capped at 100 characters. Buildium sends no text when the body is over 140 characters, and announcement texts reach US numbers only. By default you confirm each call; you can switch that off for this tool.

  MCP callbuildium_write → send_announcement

  REST endpointPOST https://cotlet.dev/api/v1/buildium/announcements

  Parameters

  Parameters: send_announcement

  Name	Type	Description
  subject string required	string	Up to 100 characters.
  body string required	string	Message. Over 140 characters goes out without the text version.
  property_ids string[] required	string[]	Property IDs from list_properties.
  expires date	date	Date the announcement leaves the Resident Center.

  Example input

  {
    "subject": "subject",
    "body": "body",
    "property_ids": [
      "property ids"
    ]
  }

  Example response

  {
    "announcement_id": "8814",
    "subject": "Water off Thursday",
    "properties": [
      "Maple Court"
    ],
    "sms": true,
    "expires": "2026-10-31",
    "status": "published"
  }

ToolWhat it doesAccess

• list_tasks Tasks from Tasks > All tasks with type, status, property and assignee. read

  Returns tasks, newest first: resident requests, owner requests, contact requests and to-dos, each with its subject, property, unit, status and who it is assigned to. Use it to check whether a request is already logged before creating a task.

  MCP callbuildium_read → list_tasks

  REST endpointGET https://cotlet.dev/api/v1/buildium/tasks

  Parameters

  Parameters: list_tasks

  Name	Type	Description
  status enum	enum	new, in_progress, completed or deferred. Default: all open.
  property_id string	string	Only this property. Property ID from list_properties.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "tasks": [
      {
        "task_id": "311045",
        "type": "Resident request",
        "subject": "Kitchen sink leaking",
        "property": "Maple Court",
        "unit": "7",
        "status": "New",
        "assigned_to": "Sam Ortiz",
        "created": "2026-10-26"
      }
    ],
    "next_cursor": null
  }

• create_task New to-do or resident request task for a property or unit. write

  Creates a task with a subject, type, property, optional unit, priority and assignee from your staff. A to-do stays inside your team. It runs without asking first, because the task can be deleted in Buildium in one step.

  MCP callbuildium_write → create_task

  REST endpointPOST https://cotlet.dev/api/v1/buildium/properties/{property_id}/tasks

  Parameters

  Parameters: create_task

  Name	Type	Description
  subject string required	string	Short title.
  type enum required	enum	to_do or resident_request.
  property_id string required	string	Property ID from list_properties.
  unit string	string	Unit the task concerns.
  description string	string	Details for whoever does the work.
  priority enum	enum	low, normal or high. Default: normal.
  assigned_to string	string	Staff member, as named in Buildium.

  Example input

  {
    "subject": "subject",
    "type": "to_do",
    "property_id": "property_8c41d2"
  }

  Example response

  {
    "task_id": "311046",
    "type": "Resident request",
    "subject": "Kitchen sink leaking",
    "property": "Maple Court",
    "unit": "7",
    "priority": "high",
    "status": "New"
  }

• add_work_order Work order on an existing task, assigned to a vendor. writeasks first

  Adds a work order on the task's Work Order tab, the same as Add work order in Buildium. The task's request type, contact information and subject carry over. It assigns work to an outside vendor. By default you confirm each call; you can switch that off for this tool.

  MCP callbuildium_write → add_work_order

  REST endpointPOST https://cotlet.dev/api/v1/buildium/tasks/{task_id}/work-orders

  Parameters

  Parameters: add_work_order

  Name	Type	Description
  task_id string required	string	Task ID from list_tasks or create_task.
  vendor string required	string	Vendor name as listed in Buildium.
  work_details string	string	What the vendor should do.
  entry_allowed boolean	boolean	Whether the vendor may enter the unit.

  Example input

  {
    "task_id": "task_8c41d2",
    "vendor": "vendor"
  }

  Example response

  {
    "work_order_id": "52890",
    "task_id": "311046",
    "vendor": "Ortiz Plumbing",
    "subject": "Kitchen sink leaking",
    "entry_allowed": true,
    "status": "created"
  }