6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Run AppFolio property management from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The AppFolio Realm-X MCP server connects an AppFolio property management company to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists exactly one tool, chat, which forwards natural language into Realm-X, AppFolio's in-product AI layer. That single name reaches leasing, maintenance, accounting and resident communications. Sign-in is OAuth against your AppFolio account.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.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..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./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.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.
__NEXT_DATA__ payload; a plain text extraction of this Intercom-hosted page returns almost nothing. · retrieved 2026-08-22llms.txt (retrieved 2026-08-22) · retrieved 2026-08-22initialize returning 401, RFC 9728 metadata at https://mcp.appfolio.com/.well-known/oauth-protected-resource/mcp, authorization server metadata at https://mcp.appfolio.com/.well-known/oauth-authorization-server, and the Keycloak realm configuration at https://account.appfolio.com/realms/property/.well-known/openid-configuration (2026-08-22) · retrieved 2026-08-22Connect AppFolio Realm-X once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.