Buildium MCP server
Buildium in any MCP client, through Memtro: Buildium does not publish this server. Memtro's Buildium connector reads Buildium through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Buildium property management: rental properties and units, leases with tenants' names and dates, outstanding lease balances by age, tasks and work orders, vendors and staff. Can add a note to a property or lease, create a to-do task or a resident request, log a phone call, and raise a work order for a vendor, each only when asked.
Reads
buildium_rentalsBuildium rental properties: name, type and subtype, number of units, active or not, city and state.buildium_unitsBuildium rental units, optionally for one property: unit number, building, bedrooms, bathrooms, size, market rent…buildium_leasesBuildium leases: unit, status (Active, Past, Future), type, start and end dates, renewal offer status, rent due day and current tenants' names…buildium_outstanding_balancesBuildium leases with money owed: total balance and by age (0-30, 31-60, 61-90, over 90 days), with the lease, property (by name) and unit.buildium_tasksBuildium tasks of every kind (to-dos, resident, owner and contact requests): title, type, status, priority, due date, category, property…buildium_work_ordersBuildium work orders: title, status, priority, due date, vendor id, amount, whether entry is allowed, and the task it belongs to.buildium_vendorsBuildium vendors: name or company, category and whether active.buildium_staffBuildium staff users: id, name, role and whether active.
Acts, when you ask
These change something in Buildium. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
buildium_add_property_noteAdd a note to a Buildium rental property, visible to staff who can see the property.buildium_add_lease_noteAdd a note to a Buildium lease, visible to staff who can see the lease.buildium_create_todoCreate a to-do task in Buildium assigned to a staff user (ids from buildium_staff), optionally on a property and unit.buildium_create_resident_requestCreate a resident request (a maintenance or service request on behalf of a resident) in Buildium, against the resident's lease.buildium_log_phone_callLog a phone call in Buildium against a tenant, rental owner, association owner or vendor, with the time it took place (UTC).buildium_create_work_orderRaise a Buildium work order for a vendor (ids from buildium_vendors), either on an existing task (task_id) or with a new task (title, assignee…
Connect it
First connect Buildium on Dashboard → Connections, then add Memtro to your client once. The Buildium tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Buildium connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which leases end in the next 60 days?
- › Who owes rent for more than 60 days?
- › Which units are vacant right now?
- › Which work orders are still open for our plumbing vendor?
- › Raise a work order for the leaking tap at 12 Elm Street
Questions
- Is this an official Buildium MCP server?
- No. It is Memtro's MCP server with Memtro's Buildium connector behind it: the connector reads Buildium through its API with the credentials you connect on Dashboard → Connections, and Buildium publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Buildium?
- Only when you ask, and only what it has been granted: add a note to a rental property; add a note to a lease; create a to-do task assigned to a staff member; create a resident request for a lease's resident; log a phone call with a tenant, owner or vendor; raise a work order for a vendor (the vendor may be notified). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.