Read Buildium properties, units, leases, tenants, balances and bills; manage work orders. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"buildium": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"buildium": {
"type": "http",
"url": "https://buildium.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Client ID, Client secret and Environment.
An administrator first enables the API in Buildium → Settings → Application settings → Api settings (toggle Open API), then creates a key under Settings → Developer Tools → Create API Key, choosing which data it may read. The secret is shown only once, at creation. Keys are environment-bound: pick Sandbox for a sandbox account's key. Your credentials are used only to call the Buildium API on your behalf and to derive a private account id; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID, Client secret and Environment. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Buildium connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
buildium_list_rental_properties | read | 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 | read | Get a rental property Fetch one rental property by id. Buildium: GET /v1/rentals/{propertyId}. |
buildium_list_rental_units | read | 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 | read | Get a rental unit Fetch one rental unit by id. Buildium: GET /v1/rentals/units/{unitId}. |
buildium_list_rental_owners | read | 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 | read | 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). Buildium: GET /v1/leases. |
buildium_get_lease | read | Get a lease Fetch one lease by id, including tenants, cosigners, account details and move-out data. Buildium: GET /v1/leases/{leaseId}. |
buildium_list_outstanding_balances | read | List lease 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 | 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 | read | 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 | read | Get a tenant Fetch one rental tenant by id. Buildium: GET /v1/leases/tenants/{tenantId}. |
buildium_list_applicants | read | 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 | read | 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. Buildium: GET /v1/workorders. |
buildium_get_work_order | read | Get a work order Fetch one work order by id. Buildium: GET /v1/workorders/{workOrderId}. |
buildium_list_tasks | read | 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 | read | 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 | read | List bills List vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines. Read-only. Buildium: GET /v1/bills. |
buildium_list_gl_accounts | read | List general ledger 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 | read | List associations List community/HOA associations with address, manager, reserve, fiscal year and operating bank account. Buildium: GET /v1/associations. |
buildium_create_work_order | write | Create a 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 | write | Update a 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 | write | Create a to-do 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 | write | Update a to-do 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}. |
buildium_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
buildium_request_feature | Request a missing feature Tell usefulapi that the user needs something the Buildium tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
buildium_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Buildium (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
buildium_cancel_subscription | Cancel the Pro subscription Cancel the caller's Buildium Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run buildium_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Buildium server only. Subscribe with buildium_upgrade (it returns a Stripe Checkout link). Cancel any time with buildium_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running buildium_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Buildium. The server calls the Buildium API with your own Buildium access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Client ID, Client secret and Environment. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID, Client secret and Environment. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Buildium API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Buildium.
Yes, if you approve it. 4 of the 23 Buildium tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Buildium server only. Cancel any time: Pro then runs to the end of the paid period. Run buildium_usage_status to see how many calls you used.
Ask the AI to run buildium_upgrade: it returns a Stripe Checkout link. To cancel, run buildium_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with buildium_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.