AppFolio MCP server Let your AI agent run your AppFolio work orders.

ToolWhat it doesAccess

• list_properties Properties in your AppFolio account with address and units. read

  Returns the properties your user can see, with address and unit count. Search matches the property name or address. Use the names it returns in the other tools.

  MCP callappfolio_read → list_properties

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

  Parameters

  Parameters: list_properties

  Name	Type	Description
  search string	string	Match on property name or address.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "properties": [
      {
        "name": "Maple Court",
        "address": "120 Maple St, Springfield",
        "units": 12
      }
    ],
    "next_cursor": null
  }

• list_vendors Vendors saved in AppFolio with trade and contact. read

  Returns the vendors in your account with name, trade and contact details. Search matches the vendor name. Use the exact name in assign_work_order.

  MCP callappfolio_read → list_vendors

  REST endpointGET https://cotlet.dev/api/v1/appfolio/vendors

  Parameters

  Parameters: list_vendors

  Name	Type	Description
  search string	string	Match on vendor name.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "vendors": [
      {
        "name": "Ortiz Plumbing",
        "trade": "Plumbing",
        "phone": "555-0142"
      }
    ],
    "next_cursor": null
  }

ToolWhat it doesAccess

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

  Returns work orders the way the app lists them: property, unit, issue, status, who it is assigned to and the date created. Filter by status or property. Use work_order_id from here in the other work order tools.

  MCP callappfolio_read → list_work_orders

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

  Parameters

  Parameters: list_work_orders

  Name	Type	Description
  status string	string	Status as named in your AppFolio, for example New or Completed. Default: all open.
  property string	string	Only this property, by name or address as listed in list_properties.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "work_orders": [
      {
        "work_order_id": "WO-1042",
        "property": "Maple Court",
        "unit": "7",
        "issue": "Kitchen sink leaking",
        "status": "New",
        "assigned_to": null,
        "created": "2026-11-02"
      }
    ],
    "next_cursor": null
  }

• get_work_order One work order with its description, vendor, schedule and history. read

  Returns the full work order: description, property and unit, status, assignee, scheduled time and the history of edits the app keeps. Use it to check what was already done before assigning or scheduling.

  MCP callappfolio_read → get_work_order

  REST endpointGET https://cotlet.dev/api/v1/appfolio/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-1042",
    "property": "Maple Court",
    "unit": "7",
    "issue": "Kitchen sink leaking",
    "description": "Water under the sink after each use.",
    "status": "New",
    "assigned_to": null,
    "scheduled": null,
    "history": [
      {
        "at": "2026-11-02T09:10:00Z",
        "event": "Created"
      }
    ]
  }

• create_work_order New work order for a property and unit. writeasks first

  Creates a work order with the issue, property, unit and description you give. It appears in the work order list and can notify the people the app is set to notify. Check list_work_orders first so the same request is not logged twice. By default you confirm each call; you can switch that off for this tool.

  MCP callappfolio_write → create_work_order

  REST endpointPOST https://cotlet.dev/api/v1/appfolio/work-orders

  Parameters

  Parameters: create_work_order

  Name	Type	Description
  property string required	string	Property name from list_properties.
  unit string	string	Unit the issue concerns.
  issue string required	string	Short title.
  description string	string	Details for whoever does the work.

  Example input

  {
    "property": "Maple Court",
    "unit": "7",
    "issue": "Kitchen sink leaking",
    "description": "Water under the sink after each use."
  }

  Example response

  {
    "work_order_id": "WO-1043",
    "property": "Maple Court",
    "unit": "7",
    "issue": "Kitchen sink leaking",
    "status": "New"
  }

• assign_work_order Assign a work order to a technician or a vendor. writeasks first

  Assigns the work order to an in-house technician or a vendor from your account. It hands the job to another person, so the assignee is told as the app is set up to tell them. The response shows the work order after the change. By default you confirm each call; you can switch that off for this tool.

  MCP callappfolio_write → assign_work_order

  REST endpointPOST https://cotlet.dev/api/v1/appfolio/work-orders/{work_order_id}/assign

  Parameters

  Parameters: assign_work_order

  Name	Type	Description
  work_order_id string required	string	Work order ID from list_work_orders.
  assignee string required	string	Technician or vendor name as listed in AppFolio.

  Example input

  {
    "work_order_id": "work_order_8c41d2",
    "assignee": "assignee"
  }

  Example response

  {
    "work_order_id": "WO-1043",
    "assigned_to": "Ortiz Plumbing",
    "status": "Assigned"
  }

• schedule_work_order Put a work order on the calendar for a date and time. writeasks first

  Schedules the work order on the app's calendar for the date and time you give. The assignee and the resident can see the visit, so the call needs your OK. The response shows the scheduled time. By default you confirm each call; you can switch that off for this tool.

  MCP callappfolio_write → schedule_work_order

  REST endpointPOST https://cotlet.dev/api/v1/appfolio/work-orders/{work_order_id}/schedule

  Parameters

  Parameters: schedule_work_order

  Name	Type	Description
  work_order_id string required	string	Work order ID from list_work_orders.
  start string required	string	Local date and time, ISO format.
  duration_minutes integer	integer	Planned length of the visit.

  Example input

  {
    "work_order_id": "work_order_8c41d2",
    "start": "start"
  }

  Example response

  {
    "work_order_id": "WO-1043",
    "scheduled": "2026-11-05T09:00:00",
    "assigned_to": "Ortiz Plumbing",
    "status": "Scheduled"
  }

ToolWhat it doesAccess

• get_tenant_ledger Charges, payments and balance for one tenant. read

  Returns the ledger of a tenant: charges and payments in date order, each with the amount, and the balance at the end. Give the property, unit and tenant name. Use it before calling a tenant about money.

  MCP callappfolio_read → get_tenant_ledger

  REST endpointGET https://cotlet.dev/api/v1/appfolio/tenant-ledger

  Parameters

  Parameters: get_tenant_ledger

  Name	Type	Description
  property string required	string	Property name from list_properties.
  unit string required	string	Unit name.
  tenant string	string	Tenant name, when the unit has more than one.

  Example input

  {
    "property": "property",
    "unit": "unit"
  }

  Example response

  {
    "tenant": "Marcus Hale",
    "property": "Maple Court",
    "unit": "2B",
    "transactions": [
      {
        "date": "2026-11-01",
        "type": "Charge",
        "description": "Rent",
        "amount": "1450.00"
      }
    ],
    "balance": "1450.00"
  }

• list_reports Reports available in your AppFolio Reports menu. read

  Returns the report names your user role can open. Use a name from here in run_report. Which reports appear depends on your role.

  MCP callappfolio_read → list_reports

  REST endpointGET https://cotlet.dev/api/v1/appfolio/reports

  Parameters

  Parameters: list_reports

  Name	Type	Description
  search string	string	Match on report name.

  Example response

  {
    "reports": [
      {
        "name": "Delinquency"
      },
      {
        "name": "Work Order"
      },
      {
        "name": "Rent Roll"
      }
    ]
  }

• run_report Run one report with a property filter and return its rows. read

  Opens the report, applies the property filter you give and returns its rows with the column headings the app shows. Leaving the property out includes all properties. Long reports come back in pages.

  MCP callappfolio_read → run_report

  REST endpointGET https://cotlet.dev/api/v1/appfolio/reports/run

  Parameters

  Parameters: run_report

  Name	Type	Description
  report string required	string	Report name from list_reports.
  property string	string	Only this property, by name or address as listed in list_properties.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "report": "report"
  }

  Example response

  {
    "report": "Delinquency",
    "columns": [
      "Tenant",
      "Property",
      "Unit",
      "Balance"
    ],
    "rows": [
      [
        "Marcus Hale",
        "Maple Court",
        "2B",
        "1450.00"
      ],
      [
        "Rosa Lin",
        "Maple Court",
        "7",
        "320.00"
      ]
    ],
    "next_cursor": null
  }