Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect AppFolio to Claude Code

Make Claude create work orders and update units in AppFolio. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect AppFolio to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect AppFolio, you add a AppFolio MCP server: a small hosted service that exposes AppFolio's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own AppFolio account. No API keys pasted into config files.

claude mcp add --transport http appfolio https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in AppFolio once connected?

Full read-write AppFolio access lets Claude create a work order against the right unit, assign it to a team member, create or update an owner record, and attach a file once you approve. The portfolio admin that used to mean re-keying between tabs happens inside the unit where the work already lives.

  • Create a work order against a specific unit with description and priority
  • Assign a work order to a team member through its assigned users field
  • Attach a file to a work order or unit to record supporting documents
  • Update owner contact fields after an inquiry
  • Create a new owner record from the details you provide
  • Draft a maintenance request follow-up for your review before it sends

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same AppFolio access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the AppFolio API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when AppFolio changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build AppFolio connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same AppFolio connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own AppFolio account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on AppFolio's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to AppFolio?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the AppFolio account it signs in with. Revoking access is one click in AppFolio.

More on the AppFolio connector

AppFolio connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us