The Axela Clients MCP connects your AI assistant to the collection data you already have in Axela. Ask about a unit, a balance, or your community's collection policy in plain language and get answers grounded in your real account data.
Works with Claude, ChatGPT, and any assistant that supports MCP connectors.
MCP (Model Context Protocol) is an open standard that lets AI assistants read data from other systems. This server is Axela's MCP endpoint for clients: it gives your assistant read-only access to the same account data you see in your Axela portal.
You sign in with your regular Axela account. Your assistant only sees the communities tied to that account, and it can look things up but never change anything.
Board meetings have a familiar pause: someone asks how much is outstanding, and the answer is "let me pull a report and get back to you." This closes that gap. Ask during the meeting, answer during the meeting.
In your AI assistant, add a custom connector (sometimes called a remote MCP server) and paste this URL:
https://clients-mcp.axela.tech
Your browser opens the Axela sign-in page. Use the same email and password as your Axela portal. No separate account, no extra password.
Try a simple one to confirm everything works:
"List all my communities."
In Claude, the option is under Settings › Connectors › Add custom connector. Other assistants keep it under their connector or integration settings.
Ten capabilities, all limited to the communities on your account. Everything is read-only except support tickets, which your assistant can open or reply to when you ask. The examples below are real prompts you can copy as they are.
Search by unit code, address, owner name, email, or phone. Returns the account status, amount owed, collection stage, payment plans, disputes, and any liens on record.
"What's the status of unit ABCD-1234?""Find the account for the owner at 4155 Palm Avenue."Payment history, late fees, and a line-by-line balance breakdown for any unit you have access to.
"Break down the balance for ABCD-1234.""What payments has this unit made this year?"A quick list of the associations tied to your account, with activity and contract status.
"List all my communities.""Which of my communities are active?"The collection picture for one association: units in collection, disputes, payment plans, and balances.
"How many units are delinquent at ABCD?""How is collection activity trending at Willow Creek?"Your association's governing documents and collection policy, fetched and summarized on demand.
"What does our collection policy say about payment plans?""Summarize the governing documents for ABCD."Guides and general information from Axela's client knowledge base: products, the collections process, policies, and terminology, answered from published documentation.
"How does the collections process work?""What happens after a payment plan is approved?"Calls, emails, SMS, and letters for a unit, plus a sentiment summary and the Willingness to Pay Score (0 to 100) for the account.
"Summarize outreach to ABCD-1234 over the last 60 days.""Has the owner of ABCD-1234 been responsive?"The checks sent to your association, with amount totals by status: cashed, pending, processing, and returned. The check-by-check list is included for ranges of 45 days or less, or when you name a community.
"Show disbursements to ABCD in the last 90 days.""How much has been disbursed to Willow Creek this year?"Invoices billed to your community or a specific unit, with totals grouped by status: sent, paid, canceled, returned, and rejected.
"List the sent invoices for ABCD.""Which invoices were paid at Willow Creek this quarter?"The one thing this server writes, and only when you ask: your assistant can open a support ticket about a unit or community, list your open tickets, and reply to or close one. Your assistant will confirm the message with you before sending anything.
"Open a ticket about ABCD-1234: the mailing address needs an update.""Show my open tickets and reply to the latest one."ABCD-1234, and the first four letters are the community code.Authentication runs through Axela SSO. There is no separate password to manage, and when your Axela access ends, this access ends with it.
Every data lookup is read-only and none can change your account. The only write action is the support ticket flow: opening a ticket or replying to one, always at your request.
The server checks your account's community access on every request. Data from other associations never reaches your assistant.
Each user gets up to 4 requests every 12 seconds. It keeps the service responsive for everyone and is plenty for normal conversation.
Any assistant that supports remote MCP connectors. Claude and ChatGPT both do.
It cannot change your account data. The one exception is support tickets: when you ask, it can open a ticket or reply to one of yours. Every other capability just looks things up.
The server only shows communities tied to your Axela account. If one is missing, ask your management company or your Axela representative to review your portal access.
From the same data behind your Axela portal, fetched at the moment you ask. Your assistant phrases the answer; the numbers come from your account data.