AppFolio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPFOLIO_VHOST | No | Your AppFolio database name (the subdomain in {vhost}.appfolio.com). Required for Reporting API. | |
| APPFOLIO_CLIENT_ID | No | Reports API Client ID. Required for Reporting API. | |
| APPFOLIO_DB_CLIENT_ID | No | Database API Basic Auth Client ID. Required for Database API. | |
| APPFOLIO_CLIENT_SECRET | No | Reports API Client Secret. Required for Reporting API. | |
| APPFOLIO_DB_DEVELOPER_ID | No | Your AppFolio Developer ID (Admin > Developer ID). Required for Database API. | |
| APPFOLIO_DB_CLIENT_SECRET | No | Database API Basic Auth Client Secret. Required for Database API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reportsA | List the available AppFolio reports (slug, name, category, required filters). Optionally filter by category. Use this to discover which report to run, then call describe_report for its parameters and run_report to execute it. |
| describe_reportA | Get the full parameter specification for a single AppFolio report: required and optional filters, types, enums, defaults, nested attributes, and response columns. Call this before run_report to know exactly which parameters to pass. |
| run_reportA | Run an AppFolio report and return its rows. Validates the report name, required filters, and parameter names against the report catalog before calling AppFolio. Use describe_report first to learn the exact filter keys for the report. |
| list_endpointsA | List the available AppFolio Database API endpoints (operationId, method, path, category, description). Optionally filter by category, resource, method, or reads-only. Use this to discover which endpoint to use, then call describe_endpoint for its parameters and call_endpoint to execute it. This is the AppFolio v0 Database API (records/CRUD), distinct from the Reporting API (list_reports/run_report). |
| describe_endpointA | Get the full specification for a single AppFolio Database API endpoint: HTTP method, path and path params, query filters (GET), request body schema with nested attributes (writes), response fields, and a request sample. Call this before call_endpoint to know exactly which parameters to pass. |
| call_endpointA | Call an AppFolio Database API endpoint and return its JSON response. Validates the operationId and required path params against the catalog before calling AppFolio, then executes (GET reads are auto-paginated; POST/PATCH/PUT/DELETE writes execute live against your AppFolio database). Use describe_endpoint first to learn the exact params and body. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NightSquawk/appfolio-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server