AppFolio Realm-X MCP server icon

AppFolio Realm-X

by AppFolio Realm-X

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Productivity1 tool

Run AppFolio property management work from an AI agent. Anthropic lists exactly one tool, chat, and AppFolio confirms it dispatches natural language into Realm-X server-side. The tool count bounds nothing. OAuth sign-in, one application scope, per-company selection.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect AppFolio Realm-X via MCP

https://mcp.appfolio.com

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

AppFolio Realm-X Tools & Capabilities (1)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The tool count tells you nothing about capability. One dispatcher named chat fronts Realm-X. Any risk assessment built on enumerating tool names fails here by construction, and no client-side allowlist can narrow what a single approved call reaches.
  • AppFolio publishes no enumeration of Realm-X operations. This is the "no vendor enumeration" case in its strongest form: there is no second list to diff Anthropic's single name against, so we cannot report a clean listing — only that nothing exists to check it with. The eight Flow templates and four Realm-X components on this page are a floor assembled from product marketing, not a specification.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here. We did not authenticate.
  • The human-confirmation step is a vendor commitment, not an enforceable control. AppFolio documents a confirmation card for actions that change data, and we have no reason to doubt it. It is prose on a help page, not a machine-readable annotation, and its exact scope is undefined.
  • Flow steps can run without a person, and AppFolio says so. Its Flows article states some tasks "can be completely automated — like sending outbound communication to residents". Whether triggering such a Flow from Claude raises one card, a card per step, or none is not documented.
  • Whether Realm-X can move money is unresolved. No AppFolio page documents a payment action, and its terms say Realm-X cannot assist in consequential financial-services decisions — a statement about reliance, not about refusal. Collections templates exist. We did not test it.
  • One application scope, portfolio-wide. af.property:any does not separate read from write, even though AppFolio's own identity realm defines af.cube.read and af.cube.write separately. The finer vocabulary exists and this connector does not use it.
  • af.property:any appears in no realm scope list we could read. The resource descriptor advertises it; the Keycloak realm's 28 advertised scopes do not include it. We could not resolve that discrepancy without authenticating.
  • The RFC 9728 descriptor is served from a catch-all. Every .well-known/oauth-protected-resource path we probed, including a deliberately invented one, returned a byte-identical document. The www-authenticate challenge — AWS-remapped to x-amzn-remapped-www-authenticate — names the /mcp descriptor specifically, which is what establishes the document as genuine rather than an interpolating catch-all.
  • AppFolio's public knowledge base holds almost nothing else. Its only public collection contains one other article, about logging in to see the rest. The Claude connector article is effectively the entire public documentation set; deeper material sits behind an AppFolio login.
  • Plan-gated at Plus or Max, and the plan you hold changes what else you have: Realm-X Flows starts at Plus, and the read/write REST API only at Max.
  • Both a bare host and a /mcp path answer. Anthropic's copy-paste command and AppFolio's own resource descriptor disagree about the endpoint. Both 401 identically; we could not test which one an authenticated session prefers.

Frequently asked questions

One, named chat, and that number bounds nothing. AppFolio's help article tells you to type /chat, and its announcement says AppFolio exposes “jobs to be done” rather than API endpoints. A dispatcher routes natural language server-side into Realm-X, so the reachable operation count is the size of Realm-X, not one.

No AppFolio page documents Realm-X posting a payment, and its terms cut against it: Realm-X “cannot assist in making consequential decisions regarding financial services”. But money-shaped work sits inside its reach — Flows ships Rent Collection, Debt Collection and Delinquencies templates. Treat it as undocumented rather than as a proven boundary.

Yes — this is the clearest write path on the connector. AppFolio lists among Realm-X Assistant's abilities: “Draft personalized communications and send them en masse”. Realm-X Messages contacts residents through text and email, and a Flow step can send outbound resident communication with no person in the loop. Send is explicit, not inferred.

Four scopes, of which three are identity claims. The resource descriptor advertised openid, profile, email and af.property:any on 2026-08-22. Only the last is an application scope, and its :any suffix reads as portfolio-wide rather than narrowed. No scope separates reading a delinquency report from triggering a collections workflow.

AppFolio says it shows a confirmation card first. Its help article states that when Claude drafts an action changing AppFolio data, “nothing is submitted until you approve it”, and its announcement adds that every action stays “under human supervision”. That is a vendor commitment described in prose, not an annotation any MCP client can enforce.

Plus or Max, per AppFolio's help article. That matters beyond billing: AppFolio's pricing page puts Realm-X Flows in Plus and its read/write REST API in Max only. So a Plus customer whose direct API access is read-only still reaches write-shaped work through this connector, because the boundary sits in the API tier rather than in Realm-X.

Whatever your AppFolio login already sees, scoped to one company. AppFolio states Claude “cannot see properties, residents, or financial data outside your authorized scope” and that Claude inherits your permissions. For a property manager that ordinarily includes resident contact details, lease terms, ledgers and maintenance history — so tenant personal data enters the agent's context by design.

One, chosen during sign-in. AppFolio's help article says you pick the company database it calls a vhost at connect time, and that you can reconnect later to switch. If the wrong company appears, AppFolio's documented fix is to disconnect the connector and reconnect choosing the correct one. The selection is a real boundary between companies.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Resources

Server Info

Category
Productivity
Developer
AppFolio Realm-X
Tools
1
Domain
mcp.appfolio.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Similar MCP Servers for Productivity

Asana logo

Asana

by Asana

Coming Soon
Productivity42 tools
View detailsConnect
Atlassian logo

Atlassian

by Atlassian

Coming Soon
Productivity25 tools
View detailsConnect
ClickUp logo

ClickUp

by ClickUp

Coming Soon
Productivity9 tools
View detailsConnect

Related Resources

Browse All MCP ServersClaude & ChatGPT Setup GuideBrowse AI Skills