[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

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

> AppFolio announced a Realm-X connector for Claude on 9 Jun 2026 (checked 6 Nov 2026), and its pricing page lists an AppFolio API on Plus (read only) and Max (read/write). Cotlet runs 10 AppFolio tools hosted, over MCP for agents and REST for scripts, in your own login: no API credentials, no developer setup, available in ChatGPT and Claude, running 24/7, with one account for many apps.

Your AI agent logs maintenance requests as work orders, dispatches them to vendors once you approve, and pulls the ledgers and reports behind your calls. Sign in to AppFolio once in your own Cloud Browser. No API credentials and no developer setup, and it works inside ChatGPT and Claude.

- Free 7-day trial, no card
- Unofficial, not affiliated with AppFolio
- Page: https://cotlet.dev/integrations/appfolio-api-mcp-server

## What can your AI agent do in AppFolio?

- Log maintenance requests as work orders
- Chase work orders left open too long
- Dispatch work orders to vendors
- Schedule a visit on the calendar
- Read a tenant ledger before a call
- Run reports and rank the balances

## Does AppFolio have an MCP server or an API?

- The Realm-X connector for Claude is an agent-to-agent link: Claude hands a job to Realm-X and AppFolio runs it inside the platform. AppFolio says it exposes "operational jobs", not API endpoints. We found no ChatGPT version.
- AppFolio lists "AppFolio API (read only)" on Plus and "AppFolio API (read/write)" on Max; Core lists none. A System Administrator creates the credentials, and a community MCP server then needs them in a config file.
- The Stack API, with 35 endpoint groups including work orders, vendors and tenant ledgers, is built for AppFolio Stack partners. No Zapier or Make app and no n8n node exist.

| What you need | Realm-X connector | AppFolio API | Cotlet |
|---|---|---|---|
| Read work orders, vendors and properties | Through a Realm-X job | Yes | Yes |
| Create, assign and schedule work orders | Through a Realm-X job | On Max, you build it | Yes, after your OK |
| Run reports and read tenant ledgers | Through a Realm-X job | Yes | Yes |
| Works in ChatGPT | Claude only | Only if you build it | Yes, and Claude |
| What you need first | AppFolio access to the connector | Plus or Max, admin credentials | Your AppFolio login |

Checked 6 Nov 2026. Sources: [AppFolio connects Realm-X to Anthropic's Claude (AppFolio newsroom, 9 Jun 2026)](https://www.appfolio.com/newsroom/appfolio-connects-realm-x-to-anthropics-claude-2026), [AppFolio pricing](https://www.appfolio.com/pricing), [AppFolio Stack API endpoints](https://www.appfolio.com/stack/partners/api), [NightSquawk/appfolio-mcp-server on GitHub](https://github.com/NightSquawk/appfolio-mcp-server)

## How does the AppFolio MCP server work?

1. **Sign in to AppFolio.** Once, in a browser we host for you.
2. **Connect your AI agent.** Paste one address into its settings.
3. **Ask about your properties.** It reads, and asks before it creates or assigns.

We never keep your AppFolio password, and no work order is created, assigned or scheduled before you approve it.

## How to connect AppFolio to your AI agent

1. **Sign in to AppFolio in a Cloud Browser.** Create a Cotlet account, open AppFolio in its Cloud Browser, sign in with your own property manager login, then press Enable for agents.
2. **Add the Cotlet address.** Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
3. **Approve the connection.** Chat apps show a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.

`https://cotlet.dev/mcp/v1` serves every app you enable on Cotlet, AppFolio included. Enable AppFolio after you connect, then refresh the connector to load its tools.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: appfolio_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: appfolio_write
```

## All 10 AppFolio MCP tools

### Properties and vendors

Read only. Use the names these return in the work order tools.

- **List properties** (`list_properties`, read): Properties in your AppFolio account with address and units.
- **List vendors** (`list_vendors`, read): Vendors saved in AppFolio with trade and contact.

### Work orders

The three writes live here. An assignment or a scheduled visit can notify the assignee and the resident, so each one waits for your OK.

- **List work orders** (`list_work_orders`, read): Work orders with property, unit, status, assignee and age, newest first.
- **Get work order** (`get_work_order`, read): One work order with its description, vendor, schedule and history.
- **Create work order** (`create_work_order`, write, asks first): New work order for a property and unit.
- **Assign work order** (`assign_work_order`, write, asks first): Assign a work order to a technician or a vendor.
- **Schedule work order** (`schedule_work_order`, write, asks first): Put a work order on the calendar for a date and time.

### Tenant ledgers and reports

Read only. Which reports you see depends on your AppFolio user role.

- **Get tenant ledger** (`get_tenant_ledger`, read): Charges, payments and balance for one tenant.
- **List reports** (`list_reports`, read): Reports available in your AppFolio Reports menu.
- **Run report** (`run_report`, read): Run one report with a property filter and return its rows.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/appfolio-api-mcp-server#tools

## Who can see my AppFolio session, and how do I revoke it?

- **What we store.** Your signed-in AppFolio browser profile, AES-256-GCM encrypted, in Finland. Never the password.
- **What your agent gets.** The 10 AppFolio tools, never the cookie or the login.
- **What the session sees.** The properties and screens your AppFolio user role opens to you.
- **What no tool touches.** Charges, payments, bills, owner and tenant records, user rights.
- **If AppFolio signs you out.** You get an email with a sign-in link and sign in yourself, 2-step verification included.
- **How to cut access.** Disable for agents, reset the browser or delete the API key.

The Cotlet site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)); there is no SOC 2 report or third-party pentest yet.

## What happens when AppFolio changes?

- **12 h** between tests of the AppFolio work order, vendor, ledger and report reads
- **24 h** between tests of work order writes
- **$0** for a call to an AppFolio tool paused for a fix

AppFolio keeps adding to Realm-X, its own AI layer, and the Claude connector arrived on 9 Jun 2026. When an AppFolio screen changes, we repair the tool and its name stays the same. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Reads the queue.** Open work orders per property, each opened in full with its history.
2. **Checks for duplicates.** A request already logged is not created twice.
3. **Waits for your OK.** Each new, assigned or scheduled work order waits in your Cotlet console until you approve it.
4. **Reports back.** Which work order was created, who got it and when the visit is.

| Action | Undo |
|---|---|
| Create a work order | Cancel or delete it in AppFolio; check first whether anyone was notified |
| Assign a work order | Assign the previous technician or vendor back; the first assignee may have been told |
| Schedule a work order | Move or clear the visit on the calendar; the resident may have seen it |

All 3 write tools ask first, because an assignee or a resident can be told. The other 7 tools only read and run at once. For a scheduled run you can switch the wait off per tool.

MCP call:

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

REST:

```
curl -X POST https://cotlet.dev/api/v1/appfolio/work-orders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"property":"Maple Court","unit":"7","issue":"Kitchen sink leaking","description":"Water under the sink after each use."}'
```

Response:

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

A nightly job or a maintenance form can call the same tools over REST at `/api/v1/appfolio`, with one key and one price. A call your AppFolio user has no rights for returns an error and costs nothing. Each tool row above shows its REST path.

## How much does the AppFolio MCP server cost?

**About $26 a month** for a manager with 3 properties and about 425 units, 4,460 credits. Cotlet needs no particular AppFolio plan; AppFolio itself starts at $1.49 per unit a month on Core.

| Job | Calls | Credits |
|---|---|---|
| Check new work orders, each workday | 6 × 22 | 1,320 |
| Log tenant messages as work orders | 2 × 12 | 240 |
| Dispatch work orders to vendors | 3 × 10 | 300 |
| Stale work orders per property, weekly | 7 × 4 | 280 |
| Delinquency report, weekly | 4 × 4 | 160 |
| Tenant ledger before a collection call | 3 × 22 | 660 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 4,460 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No API credentials, no Stack partner application

The month is our example: 3 properties, a work order check each workday, 12 tenant messages logged, 10 dispatches, weekly stale-order and delinquency runs, and a ledger look-up before each of 22 calls. AppFolio reported 9.4 million units and 22,096 property management customers at the end of 2025, about 425 units each (our division of its 10-K figures). Dollars at the $29 pack rate.

## AppFolio MCP server on GitHub, Realm-X or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| [NightSquawk/appfolio-mcp-server](https://github.com/NightSquawk/appfolio-mcp-server) | 137 reports and 156 Database API endpoints behind 6 tools, AGPL-3.0. 0 stars, last push 31 Oct 2026. | Runs on your computer with Reports and Database API credentials. |
| [CryptoCultCurt/appfolio-mcp-server](https://github.com/CryptoCultCurt/appfolio-mcp-server) | Reporting API only, ISC. 10 stars, last push 13 Sep 2026. | Reports only, and you host it with your own credentials. |
| [swagger3x/appfolio-mcp](https://github.com/swagger3x/appfolio-mcp) | Wraps the AppFolio REST API in 38 tools. 1 star, last push 4 Jul 2026. | Needs API access on your plan and runs on your computer. |
| [AppFolio Realm-X connector for Claude](https://www.appfolio.com/newsroom/appfolio-connects-realm-x-to-anthropics-claude-2026) | AppFolio's own link: Claude hands a job to Realm-X, which runs it inside AppFolio. | Claude only; you ask for a job, not a specific tool call. |

If you want Realm-X to do the job inside AppFolio from Claude, use the connector. If you have Plus or Max and a developer, the API or a community server works. If you want one hosted address for ChatGPT and Claude, with no credentials to manage, Cotlet does that.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the AppFolio tools go to contact@cotlet.dev.

## AppFolio MCP server: questions

### How do I connect AppFolio to ChatGPT or Claude?

Sign up at cotlet.dev, log in to AppFolio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your AppFolio account through Cotlet, in their phone apps too.

### What can ChatGPT do in AppFolio?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in AppFolio: log maintenance requests as work orders; chase stale work orders; dispatch work orders to vendors. You ask in plain words, and anything that reaches other people waits for your OK first.

### How do I get access?

Sign up free at https://cotlet.dev, open AppFolio under Integrations in the console and sign in to AppFolio in its Cloud Browser. The trial starts with your first app and needs no card.

### Do I need to be an AppFolio Stack partner to use Cotlet?

No. AppFolio's Stack API is built for approved Stack partners (appfolio.com/stack/partners/api). Cotlet works in your own AppFolio session, and your agent can do what your AppFolio user role can do.

### Can the agent contact residents or owners?

Only through the actions above. A work order, an assignment or a scheduled visit can notify people as your AppFolio is set up, so each of these waits for your OK by default.

### Does AppFolio have an official MCP server?

AppFolio announced a Realm-X connector for Claude on 9 Jun 2026 (checked 6 Nov 2026). It hands a job to AppFolio's own Realm-X agent. We found no ChatGPT version. Cotlet gives your agent individual AppFolio tools in ChatGPT, Claude, Cursor and n8n.

### Do I need the Plus or Max plan?

Not for Cotlet. AppFolio lists its API on Plus (read only) and Max (read/write). Cotlet works in your own AppFolio login, so your agent does what your user role can do on any plan.

### Is the MCP server different from the REST API?

Only in how you call it. Both expose the same 10 tools with the same inputs, answers, key and price. Agents use MCP; scripts and forms use REST.

### Is Cotlet affiliated with AppFolio?

No. Cotlet is independent and not affiliated with AppFolio, Inc.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
