ToolsMCP
Buildium MCP Server and API by Cotlet
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- cotlet.dev
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.1 · updated
- Official links
Publisher’s description
Buildium MCP server: record lease payment, list outstanding balances, send text message.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.1, registry status active. 2 remote endpoints (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- cotlet.dev
- Version observed
- 1.0.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/dev.cotlet%2Fbuildium/versions/1.0.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “payment”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “payment”, “send”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://cotlet.dev/mcp/v1/buildium/connect(streamable-http)https://cotlet.dev/mcp/v1/buildium(streamable-http, declares a required credential)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
dev.cotlet/buildium
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.