Yardi API and MCP server Let your AI agent run the busywork in Yardi Breeze.

ToolWhat it doesAccess

• list_properties Properties in your Breeze account, with address and unit count. read

  Returns the properties your Breeze user can see, with address, property type and number of units. A user limited to some properties sees only those. Use property_id in the other tools.

  MCP callyardi_read → list_properties

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

  Parameters

  Parameters: list_properties

  Name	Type	Description
  search string	string	Name or address contains.

  Example response

  {
    "properties": [
      {
        "property_id": "p_104",
        "name": "Maple Court",
        "type": "Residential",
        "address": "12 Maple St, Dayton, OH",
        "units": 24
      },
      {
        "property_id": "p_118",
        "name": "Elm Street Duplexes",
        "type": "Residential",
        "address": "8 Elm St, Dayton, OH",
        "units": 4
      }
    ]
  }

• list_tenants Tenants with property, unit, status, contact details and current balance. read

  Returns tenants with property, unit, status, email, phone and current balance, sorted by balance, highest first. Current tenants only by default. min_balance keeps tenants who owe at least that many whole dollars. Pass next_cursor back as cursor for the next page.

  MCP callyardi_read → list_tenants

  REST endpointGET https://cotlet.dev/api/v1/yardi/tenants

  Parameters

  Parameters: list_tenants

  Name	Type	Description
  property_id string	string	Only tenants of this property.
  status enum	enum	current, past, future or all. Default: current.
  min_balance integer	integer	Only tenants owing at least this amount, whole dollars.
  search string	string	Name, unit, email or phone contains.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "tenants": [
      {
        "tenant_id": "t_20481",
        "name": "Jordan Lee",
        "property": "Maple Court",
        "unit": "4B",
        "status": "current",
        "email": "jordan.lee@example.com",
        "phone": "+1 555 010 0142",
        "balance": "1250.00"
      },
      {
        "tenant_id": "t_20517",
        "name": "Priya Shah",
        "property": "Maple Court",
        "unit": "12A",
        "status": "current",
        "email": "priya.shah@example.com",
        "phone": "+1 555 010 0177",
        "balance": "640.00"
      }
    ],
    "next_cursor": null
  }

• get_tenant One tenant: contacts, lease dates, rent, balance and resident portal status. read

  Returns one tenant with contacts, lease start and end, monthly rent, current balance and whether the tenant has registered in the RentCafe resident portal. Breeze texts only reach tenants who registered and opted in there, so check portal_registered before send_text.

  MCP callyardi_read → get_tenant

  REST endpointGET https://cotlet.dev/api/v1/yardi/tenants/{tenant_id}

  Parameters

  Parameters: get_tenant

  Name	Type	Description
  tenant_id string required	string	Tenant ID from list_tenants.

  Example input

  {
    "tenant_id": "tenant_8c41d2"
  }

  Example response

  {
    "tenant_id": "t_20481",
    "name": "Jordan Lee",
    "property": "Maple Court",
    "unit": "4B",
    "status": "current",
    "lease_start": "2026-02-01",
    "lease_end": "2027-01-31",
    "monthly_rent": "1200.00",
    "balance": "1250.00",
    "portal_registered": true,
    "sms_opt_in": true
  }

• get_tenant_ledger Charges, payments and credits on a tenant account, with running balance. read

  Returns the ledger of one tenant, oldest first, with a running balance after each line. The period defaults to the last 90 days. Late fees and recurring rent that Breeze posts on its own show up as ordinary charges.

  MCP callyardi_read → get_tenant_ledger

  REST endpointGET https://cotlet.dev/api/v1/yardi/tenants/{tenant_id}/ledger

  Parameters

  Parameters: get_tenant_ledger

  Name	Type	Description
  tenant_id string required	string	Tenant ID from list_tenants.
  from date	date	Start date. Default: 90 days ago.
  to date	date	End date. Default: today.

  Example input

  {
    "tenant_id": "tenant_8c41d2"
  }

  Example response

  {
    "tenant_id": "t_20481",
    "from": "2026-08-01",
    "to": "2026-10-27",
    "opening_balance": "0.00",
    "lines": [
      {
        "date": "2026-09-01",
        "type": "Rent",
        "amount": "1200.00",
        "balance": "1200.00"
      },
      {
        "date": "2026-09-03",
        "type": "Payment",
        "amount": "-1200.00",
        "balance": "0.00"
      },
      {
        "date": "2026-10-01",
        "type": "Rent",
        "amount": "1200.00",
        "balance": "1200.00"
      },
      {
        "date": "2026-10-06",
        "type": "Late Fee",
        "amount": "50.00",
        "balance": "1250.00"
      }
    ],
    "closing_balance": "1250.00"
  }

• post_charge Post a one-off charge to a tenant account. writeasks first

  Posts one charge to one tenant and returns the balance before and after. charge_type must be a charge code set up in your Breeze account. The date defaults to today. There is no undo tool: a wrong charge is reversed in Breeze. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → post_charge

  REST endpointPOST https://cotlet.dev/api/v1/yardi/tenants/{tenant_id}/charges

  Parameters

  Parameters: post_charge

  Name	Type	Description
  tenant_id string required	string	Tenant ID from list_tenants.
  charge_type string required	string	Charge code as set up in your Breeze account, e.g. Late Fee.
  amount string required	string	Decimal amount, e.g. 75.00.
  date date	date	Transaction date. Default: today.
  memo string	string	Shown on the ledger line.

  Example input

  {
    "tenant_id": "tenant_8c41d2",
    "charge_type": "charge type",
    "amount": "amount"
  }

  Example response

  {
    "transaction_id": "tx_559102",
    "tenant_id": "t_20481",
    "unit": "4B",
    "charge_type": "Lockout Fee",
    "amount": "75.00",
    "date": "2026-10-27",
    "previous_balance": "1250.00",
    "new_balance": "1325.00"
  }

ToolWhat it doesAccess

• list_work_orders Work orders with status, property, unit, assignee and age. read

  Returns work orders, oldest first, with status, property, unit, tenant, assignee (a vendor or an employee) and creation date. Open work orders only by default. Pass next_cursor back as cursor for the next page.

  MCP callyardi_read → list_work_orders

  REST endpointGET https://cotlet.dev/api/v1/yardi/work-orders

  Parameters

  Parameters: list_work_orders

  Name	Type	Description
  status enum	enum	open, completed or all. Default: open.
  property_id string	string	Only work orders at this property.
  unit string	string	Only work orders on this unit.
  older_than_days integer	integer	Only work orders created at least this many days ago.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "work_orders": [
      {
        "work_order_id": "wo_7731",
        "title": "Water heater not heating",
        "property": "Elm Street Duplexes",
        "unit": "8B",
        "status": "In progress",
        "assigned_to": "Sam Ortiz",
        "created_at": "2026-10-14T09:12:00-04:00",
        "days_open": 13
      },
      {
        "work_order_id": "wo_7790",
        "title": "Hallway light out",
        "property": "Maple Court",
        "unit": "Common area",
        "status": "Open",
        "assigned_to": null,
        "created_at": "2026-10-19T15:40:00-04:00",
        "days_open": 8
      }
    ],
    "next_cursor": null
  }

• get_work_order One work order with its details, progress notes and attachments. read

  Returns one work order with the description, assignee, schedule, progress notes newest first and the names of attached photos and documents. Attachments are listed, not downloaded.

  MCP callyardi_read → get_work_order

  REST endpointGET https://cotlet.dev/api/v1/yardi/work-orders/{work_order_id}

  Parameters

  Parameters: get_work_order

  Name	Type	Description
  work_order_id string required	string	Work order ID from list_work_orders.

  Example input

  {
    "work_order_id": "work_order_8c41d2"
  }

  Example response

  {
    "work_order_id": "wo_7731",
    "title": "Water heater not heating",
    "property": "Elm Street Duplexes",
    "unit": "8B",
    "tenant": "Marcus Webb",
    "status": "In progress",
    "assigned_to": "Sam Ortiz",
    "scheduled_for": "2026-10-20",
    "notes": [
      {
        "date": "2026-10-16",
        "author": "Sam Ortiz",
        "text": "Ordered a replacement thermostat, waiting on the part."
      }
    ],
    "attachments": [
      "heater-label.jpg"
    ]
  }

• create_work_order Open a work order for a unit, optionally assigned to a vendor or employee. writeasks first

  Opens a work order for a property and unit with the status Open. Give tenant_id to tie it to the tenant who reported it and assigned_to to give it to a vendor or an employee in Breeze, who may be notified. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → create_work_order

  REST endpointPOST https://cotlet.dev/api/v1/yardi/properties/{property_id}/work-orders

  Parameters

  Parameters: create_work_order

  Name	Type	Description
  property_id string required	string	Property ID from list_properties.
  unit string	string	Unit name or number.
  tenant_id string	string	Tenant who reported it.
  title string required	string	Short description, e.g. "Kitchen sink leak".
  details string	string	Longer description for whoever does the work.
  assigned_to string	string	Vendor or employee name as it appears in Breeze.

  Example input

  {
    "property_id": "p_104",
    "unit": "12A",
    "tenant_id": "t_20517",
    "title": "Kitchen sink leak",
    "details": "Tenant emailed 7:40 am: water under the kitchen sink since last night. Has a dog, home after 3 pm.",
    "assigned_to": "Dana Ruiz"
  }

  Example response

  {
    "work_order_id": "wo_7812",
    "status": "Open",
    "property": "Maple Court",
    "unit": "12A",
    "tenant_id": "t_20517",
    "title": "Kitchen sink leak",
    "assigned_to": "Dana Ruiz",
    "created_at": "2026-10-27T08:30:00-04:00"
  }

• update_work_order Change the status or assignee of a work order, or add a progress note. writeasks first

  Changes one work order: status, assignee, or a progress note added to it. Marking it completed closes it in Breeze, and the change can reach the assignee and the tenant. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → update_work_order

  REST endpointPATCH https://cotlet.dev/api/v1/yardi/work-orders/{work_order_id}

  Parameters

  Parameters: update_work_order

  Name	Type	Description
  work_order_id string required	string	Work order ID from list_work_orders.
  status enum	enum	open, in_progress or completed.
  assigned_to string	string	Vendor or employee name as it appears in Breeze.
  note string	string	Progress note added to the work order.

  Example input

  {
    "work_order_id": "work_order_8c41d2"
  }

  Example response

  {
    "work_order_id": "wo_7731",
    "status": "In progress",
    "assigned_to": "Sam Ortiz",
    "note_added": true
  }

ToolWhat it doesAccess

• list_prospects Prospects with the property they asked about, source and status. read

  Returns prospects newest first, with name, contact details, the property they asked about, the listing source and whether they applied. since keeps prospects who first contacted you on or after that date.

  MCP callyardi_read → list_prospects

  REST endpointGET https://cotlet.dev/api/v1/yardi/prospects

  Parameters

  Parameters: list_prospects

  Name	Type	Description
  property_id string	string	Only prospects for this property.
  since date	date	Only prospects created on or after this date.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "prospects": [
      {
        "prospect_id": "pr_3304",
        "name": "Ana Lopez",
        "email": "ana.lopez@example.com",
        "property": "Elm Street Duplexes",
        "source": "RentCafe.com",
        "status": "inquiry",
        "created_at": "2026-10-24"
      },
      {
        "prospect_id": "pr_3297",
        "name": "Sam Patel",
        "email": "sam.patel@example.com",
        "property": "Elm Street Duplexes",
        "source": "Property website",
        "status": "applied",
        "created_at": "2026-10-22"
      }
    ],
    "next_cursor": null
  }

• list_owners Owners with their properties, ownership share and email. read

  Returns the owners in your Breeze account with email, the properties they own and the share of each, so a property with two owners shows both. An owner without an email comes back with email set to null.

  MCP callyardi_read → list_owners

  REST endpointGET https://cotlet.dev/api/v1/yardi/owners

  Parameters

  No parameters.

  Example response

  {
    "owners": [
      {
        "owner_id": "o_412",
        "name": "Hill Family Trust",
        "email": "hill.trust@example.com",
        "properties": [
          {
            "property": "Maple Court",
            "share": "100%"
          }
        ]
      },
      {
        "owner_id": "o_415",
        "name": "Ken Walsh",
        "email": null,
        "properties": [
          {
            "property": "Elm Street Duplexes",
            "share": "50%"
          }
        ]
      }
    ]
  }

• send_text Text one tenant through Breeze Text Messaging (SMS). writeasks first

  Sends one text to one tenant through Breeze's Text Messaging (SMS), under your account. Breeze texts only tenants who registered and opted in through RentCafe; anyone else comes back as not_reachable and nothing is sent. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → send_text

  REST endpointPOST https://cotlet.dev/api/v1/yardi/tenants/{tenant_id}/texts

  Parameters

  Parameters: send_text

  Name	Type	Description
  tenant_id string required	string	Tenant ID from list_tenants.
  message string required	string	Text message to the tenant.

  Example input

  {
    "tenant_id": "tenant_8c41d2",
    "message": "message"
  }

  Example response

  {
    "tenant_id": "t_20481",
    "to": "Jordan Lee",
    "status": "sent",
    "sent_at": "2026-10-27T09:05:00-04:00"
  }

• send_email Email one tenant or prospect from Breeze. writeasks first

  Sends one email from Breeze to one tenant or prospect, under your account. Give tenant_id or prospect_id, not both. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → send_email

  REST endpointPOST https://cotlet.dev/api/v1/yardi/emails

  Parameters

  Parameters: send_email

  Name	Type	Description
  tenant_id string	string	Tenant ID from list_tenants.
  prospect_id string	string	Prospect ID from list_prospects.
  subject string required	string	Email subject.
  body string required	string	Email text.

  Example input

  {
    "subject": "subject",
    "body": "body"
  }

  Example response

  {
    "to": "Priya Shah",
    "email": "priya.shah@example.com",
    "subject": "Work order logged: kitchen sink leak",
    "status": "sent",
    "sent_at": "2026-10-27T08:32:00-04:00"
  }

• send_owner_report Email an owner their report packet for a month. writeasks first

  Generates the owner's report packet for the month, as set up for that owner in Breeze, and emails it to the owner's address on file. An owner without an email returns no_email and nothing is sent. By default you confirm each call; you can switch that off for this tool.

  MCP callyardi_write → send_owner_report

  REST endpointPOST https://cotlet.dev/api/v1/yardi/owners/{owner_id}/report

  Parameters

  Parameters: send_owner_report

  Name	Type	Description
  owner_id string required	string	Owner ID from list_owners.
  month string required	string	Month as YYYY-MM.

  Example input

  {
    "owner_id": "owner_8c41d2",
    "month": "month"
  }

  Example response

  {
    "owner_id": "o_412",
    "owner": "Hill Family Trust",
    "month": "2026-09",
    "email": "hill.trust@example.com",
    "status": "sent"
  }