MCP portfolio tools
Read-only portfolio tools available with an org MCP API key.
All tools require Authorization: Bearer with an org MCP API key on the HTTP MCP endpoint.
Tools return JSON text content. Default list limits are 15 rows unless noted.
Tool reference#
portfolio_list_properties
List properties for the org.
| Input | Type | Default |
|---|---|---|
limit | number (1–50) | 15 |
portfolio_list_leases
List leases with property, unit, tenant names, status, dates.
| Input | Type | Default |
|---|---|---|
limit | number (1–50) | 15 |
portfolio_list_tenants
List tenants linked to the org.
| Input | Type | Default |
|---|---|---|
limit | number (1–50) | 15 |
portfolio_list_maintenance
Recent maintenance / work order requests.
| Input | Type | Default |
|---|---|---|
limit | number (1–50) | 15 |
portfolio_list_applications
Recent rental applications.
| Input | Type | Default |
|---|---|---|
limit | number (1–50) | 15 |
portfolio_get_property
Summary for one property.
| Input | Type | Required |
|---|---|---|
propertyId | string | yes |
portfolio_financial_summary
Rent collected this month and last month (org aggregate).
No inputs.
portfolio_applications_summary
Application counts grouped by status.
No inputs.
portfolio_leases_expiring_soon
Active leases ending within N days.
| Input | Type | Default |
|---|---|---|
days | number (1–365) | 30 |
Global MCP tools (platform bearer)#
When using the platform MCP bearer (internal), registry and knowledge tools are also available. Org keys unlock portfolio_* tools only in v1 — no write/mutation tools on MCP.
Audit#
Each portfolio tool invocation is logged (toolName, latency, success — no request payloads). View counts in manager Developers → Usage.