Skip to content

Connect your AI assistant to your Axela data.

The Axela MCP Connector lets AI assistants like Claude and ChatGPT read your Axela data. You sign in with your Axela account, and your assistant sees only what you can see in your portal.

Ask about a unit, a community, or your whole portfolio. Get the answer as a summary, a CSV file, a chart, or a Board report.

Works today with Claude and ChatGPT. One-click directory listings are on the way.

What is an MCP, and why does it matter?

MCP, short for Model Context Protocol, is a standard way for AI assistants to connect to the software and data you already use. Think of it as USB-C for AI.

Before USB-C, every device needed its own plug, and USB-C gave them all the same one. AI has the same problem: without a standard, three assistants and three systems need nine custom links. With MCP, each one connects once, through the standard.

Without a standard

Before USB-C, every device needed its own plug.

  • Claude
  • ChatGPT
  • Other assistants
  • Axela
  • Accounting
  • Email and files

AI has the same problem. Each assistant needs its own link to each system. If nobody built the link for yours, it can't reach your data.

With a standard

USB-C gave every device the same plug.

  • Claude
  • ChatGPT
  • Other assistants
MCP
  • Axela
  • Accounting
  • Email and files

MCP does the same for AI. Axela connects once, and any assistant that supports MCP can use that connection.

One connector, your choice of assistant

Use Claude today and ChatGPT tomorrow. The same Axela MCP Connector works with both, and we'll add other assistants as we test them.

Only when you ask

Nothing is copied into your assistant ahead of time. It looks up your Axela data only when you ask a question.

The same rules, whoever asks

Whichever assistant you use, it sees only what you can see in your Axela portal, never more.

How is it different from Axela AI?

Both give you your Axela data in plain conversation. The difference is whose assistant you talk to. Axela AI is ours, built into the portal. The Axela MCP Connector brings the same data to yours, the assistant that already knows how you work.

Your Axela data feeds two assistants. Axela AI, in your portal, answers a quick question in Axela's format. Your own assistant, through the Axela MCP Connector, turns the same data into a Board report with your own branding.
Axela AI In your Axela portal

How is Willow Creek doing this quarter?

Here's where Willow Creek stands today.

Willow Creek

Axela AI
In collection
14 units
Outstanding
$86,400.00
Disbursed this quarter
$31,200.00

Quick answers while you work in Axela

Open the portal and ask. There's nothing to set up.

Your AI assistant

Claude or ChatGPT

Make our October Board report for Willow Creek with the latest Axela numbers.

Your logo

Willow Creek

14

In collection

$86.4K

Outstanding

$31.2K

Disbursed

Your data, in your own reports and workflows

Ask for a Board report, and it comes back in your format, ready to share.

Your Axela data

The same data and the same permissions, whichever assistant asks.

It already knows how you work

Your assistant knows your routines, your templates, and your brand. Now it can work with your Axela data too.

Reports in your own format

Turn Axela numbers into a Board report, an owner update, or a summary that looks like yours.

Axela data in your workflow

Use it alongside the files and tools your assistant already works with, instead of switching between systems.

Connect your assistant

Setup is copy and paste. You add two values to your assistant, then sign in with your usual Axela account.

The two values you'll paste

They're the same for every assistant, and neither one is a password. One says which server to talk to, the other which connector is asking. You still sign in on Axela's page, in your browser.

Server URL
https://clients-mcp.axela.tech
OAuth Client ID
axela_clients_mcp_id

Client secret: leave it empty. This connector doesn't use one, so there's no third value to hunt down and nothing extra to keep safe.

Follow the steps for your assistant

Claude and ChatGPT are below. If you use another assistant, open a support ticket from your Axela portal, and we'll check whether it can connect.

New to Claude? Create a free account at claude.ai. Custom connectors work on every Claude plan, and the free plan allows one. The steps below are the same on the web and in the desktop app.

  1. Step 1: Open your connector settings

    Click on your initials and go to Settings › Connectors. Open the Add dropdown and choose Custom connector.

  2. Step 2: Name it and paste the Server URL

    Name the connector Axela and paste this into the URL field:

    https://clients-mcp.axela.tech
  3. Step 3: Add the Client ID

    Open Advanced settings and paste this as the OAuth Client ID:

    axela_clients_mcp_id

    Leave OAuth Client Secret empty, then click Add. This step looks technical, but it's just copy and paste.

  4. Step 4: Connect and sign in

    Click Connect next to the new connector. Your browser opens Axela's sign-in page, where you sign in just as you do in your Axela portal. You may then see a screen asking you to approve the connection. That's expected. Allow it and you're done.

ChatGPT adds custom MCP servers through developer mode, which you switch on once, and lists them under Plugins.

  • Developer mode is available on Plus and Pro. On Business, Enterprise, and Edu plans, a workspace admin turns it on.
  • ChatGPT issues its own callback URL. It's already registered on Axela's side for this connector, so step 4 is usually a quick check.
  1. Step 1: Turn on developer mode

    Open Settings › Security and login and scroll down to Developer mode. Switch it on. The Elevated risk label next to it is there because developer mode lets you add any MCP server, including ones OpenAI has never reviewed. You only do this once.

  2. Step 2: Start a new plugin

    Open Plugins in the left sidebar and click the + button at the top right. In the New Plugin panel, name it Axela. Add a short description such as My Axela collection data. Leave Connection set to Server URL, not Tunnel. Then paste this as the URL:

    https://clients-mcp.axela.tech
  3. Step 3: Fill in the OAuth settings

    Set Authentication to OAuth, then open Advanced OAuth settings. Set Registration method to User-Defined OAuth Client and paste this as the OAuth Client ID:

    axela_clients_mcp_id

    Leave OAuth Client Secret empty, set Token endpoint auth method to none, and check that mcp:tools is selected under Default scopes. ChatGPT will report DCR and CIMD as unavailable for this server, which is expected: this connector uses the Client ID you pasted instead.

  4. Step 4: Check the callback URL, then create it

    In that same panel, Callback URL shows the address ChatGPT will send you back to. For this connector, it's almost always the value below. That one is already registered on Axela's side, so there's nothing for you to do:

    https://chatgpt.com/connector/oauth/S8etgPPS5cUv

    If ChatGPT shows you anything different, email it to marcos@axela-tech.com and you'll hear back once it's registered. Until it is, signing in stops with an error about the redirect URI. Either way, finish by checking I understand and want to continue, which unlocks the Create button, and click Create.

  5. Step 5: Connect and sign in

    The Axela plugin now appears in your list. Choose Connect on it, and Axela's sign-in page opens in your browser, where you sign in just as you do in your Axela portal. Approve the connection when asked.

  6. Step 6: Switch it on in the chat

    Start a new chat, open the + menu in the message box, and turn on Axela. Unlike Claude, ChatGPT needs it switched on in every new conversation.

Coming soon One-click setup. The Axela MCP Connector is on its way to the Claude and ChatGPT directories, a bit like an app going through App Store review. Until it's listed, add it by hand with the steps above. Nothing changes for you when the listing goes live.

Ask your first question

“List my communities” proves the connection works, and that's all it proves. Try this instead, with one of your own addresses or unit codes. Naming the connector tells your assistant where to look, and naming each piece of data tells it what to look up.

“Using the Axela MCP Connector, review the account for 123 Main St. Look up the unit and its collection status, pull the balance breakdown and payment history, then pull the full outreach history including the Willingness to Pay Score. Put it together as a one-page summary I can bring to the Board.”

Your assistant looks up the unit, its balance and payments, and its outreach history, then writes the summary.

Tip: you don't need the unit code. Your assistant can also find a unit by its address, the owner's name, email, or phone number, or the account number in your accounting system.

What you can ask

Ask about anything in your Axela data, in your own words. Get a quick reply, a CSV file, a chart, or a summary for the Board. When someone at a Board meeting asks what's outstanding, you can answer on the spot.

Units and accounts

What's the status of 123 Main St?

123 Main St is current on its payment plan.

123 Main St

Willow Creek
Balance
$4,282.00
Collection stage
Collection notice
Payment plan
Active, on track
Disputes
None
Liens
None

Also try

  • Break down the balance for 123 Main St.
  • What payments has this unit made this year?

Your communities

How are we doing at Willow Creek this quarter?

Here's Willow Creek so far this quarter.

Willow Creek, this quarter

  • 14 units in collection, $86,400 outstanding
  • 4 on active payment plans, 1 open dispute
  • $31,200 disbursed to the association this quarter
  • Needs attention: 88 Oak Ln payment plan lapsed, 4155 Palm Ave dispute open since July 8

Also try

  • How many units are delinquent at Bayside Commons?
  • Which of my communities does Coastal Property Management oversee?

Your whole portfolio

What are the 5 largest balances in collection across my portfolio?

Here are your 5 largest balances in collection.

  1. 11200 Bay RdBayside Commons$18,940.00
  2. 277 Elm CtWillow Creek$15,310.00
  3. 34155 Palm AveWillow Creek$12,880.00
  4. 49 Harbor LnCoral Pointe$11,402.50
  5. 5315 Pine StBayside Commons$9,975.00

Also try

  • How many units do I have in collection across my portfolio, and how much do they owe?
  • Across my communities, which have the highest outstanding balances right now?

Money in and out

Show disbursements to Bayside Commons in the last 90 days.

Three checks in the last 90 days, $16,335.00 in total. Two are cashed, and the October 14 one is still processing.

Disbursements to Bayside Commons in the last 90 days
DateCheckAmountStatus
Oct 14#10482$6,240.00Processing
Sep 12#10391$4,980.00Cashed
Aug 9#10307$5,115.00Cashed

Also try

  • Which invoices were paid at Willow Creek this quarter?
  • How much has been disbursed to Willow Creek this year?

Documents and policies

What does the Willow Creek collection policy say about payment plans?

Here's what Willow Creek's collection policy says.

From your collection policy

  • Payment plans of up to 12 months
  • Each plan is approved by the Board
  • A missed payment ends the plan

Source: Willow Creek collection policy, section 4

Also try

  • What do the Willow Creek governing documents say about rentals?
  • How does the collections process work?

Outreach and tickets

Open a ticket about 123 Main St: the mailing address needs an update.

Here's the ticket I'll open. Should I send it?

New support ticket

About
123 Main St, Willow Creek
Message
The mailing address on file needs an update.

Also try

  • Summarize outreach to Jane Doe over the last 60 days.
  • Has Jane Doe been responsive?

Sample answers, just to show the format. Your assistant reports what's actually in your Axela data.

Tips for better answers

Name the connector once

Start with “Using the Axela MCP Connector” so your assistant uses your account, not general knowledge.

Say what you want back

A summary, a ranking, a draft, or a one-pager. Naming the result turns data into something you can use.

Give a time window

For money and outreach questions, say “the last 30 days” or “since January.”

Double-check the numbers

An assistant can misread a figure, so check the numbers that matter in your Axela portal before the Board sees them.

Is my data safe?

Yes. It works like a “Sign in with Google” button. You sign in on Axela's own page, and your assistant gets a limited pass instead of your password.

  • Only what you can see

    Your assistant sees only the data you can already see in your Axela portal.

  • Read-only, with one exception

    Your assistant can look things up but can't change your account. The one exception is support tickets: it can open one, or reply to or close one of yours, after you confirm.

  • You can disconnect anytime

    Remove the connector in your assistant, and it can no longer reach your Axela data. The pass also expires on its own.

  • Axela never sees your chats

    Your chat history stays with your assistant's provider, and Axela doesn't use your questions to train any AI model.

  • Encrypted and logged

    Every request travels encrypted and is logged against the account that made it. Per-user limits slow down any attempt to pull data in bulk.

For your IT team The standard behind each measure.
You sign in on Axela's page, never inside your assistant
OAuth 2.0 authorization code flow with PKCE
Your assistant holds a limited pass, not your password
Expiring JWT access token, mcp:tools scope
This server accepts only passes issued for it
Token audience validated on every request (RFC 8707)
Your assistant finds the sign-in page on its own
Protected resource metadata (RFC 9728)
Access never goes beyond your Axela portal access
Same identity provider, per-user authorization on every call
Lookups can't change anything
MCP tool annotations: lookups are read-only, the two ticket tools are marked as writes
Nothing travels in the clear
TLS on every request, HTTPS only
No shared secret exists to leak
Public client, no client secret issued
Limits slow down any attempt to pull data in bulk
Per-user rate limiting: up to 100 requests in a burst, refilling at five per second

Common questions

Quick answers about setup, cost, privacy, and access. For anything else, open a support ticket from your Axela portal.

Is this the same as Axela AI?

No. Axela AI is the assistant built into your Axela portal. The Axela MCP Connector lets your own assistant, like Claude or ChatGPT, read the same data with the same permissions. See how the two differ.

Which AI assistants work with this?

Claude and ChatGPT, the two we've tested. Claude supports custom connectors on every plan, and the free plan allows one. ChatGPT supports them through developer mode on Plus and Pro, and on Business, Enterprise, and Edu once a workspace admin turns it on. Other assistants are adding support for MCP connectors, and we'll add their steps here once we've tested them.

What does it cost?

Axela doesn't charge anything extra. The Axela MCP Connector is part of your Axela client access. You do need an assistant that supports it: Claude's free plan works, and ChatGPT needs Plus or a higher plan.

Should I wait for one-click setup?

No. Listings in the Claude and ChatGPT directories are on the way, and a connection you add today keeps working when they go live. It's the same connector either way.

Do I need a client secret?

No. The Server URL and the Client ID are the only values you paste, and neither is secret. Signing in always happens in your own browser, on Axela's sign-in page.

Why can't I see one of my communities?

Your assistant sees only the communities tied to your Axela account. If one is missing, ask your management company or your Axela representative to review your portal access.

Where do the answers come from?

From the same data behind your Axela portal, fetched when you ask. Your assistant writes the wording, and the numbers come from your account. Before you share a figure that matters, check it in your portal.

Is my data used to train AI models?

Not by Axela. Axela doesn't train AI models on your questions, and it never hands your Axela data to an AI provider in advance. Your assistant looks up your data only when you ask a question. Whether your conversations are used for training is up to your assistant's provider and your settings there.

Who can see my questions and the answers?

Your conversation stays with your assistant's provider, Anthropic for Claude or OpenAI for ChatGPT, under their privacy terms and your settings. That includes the owner names, contact details, and balances your assistant looks up. Axela never sees the conversation. It only receives the lookups your assistant runs, tied to your account the same way your portal activity is.

How do I disconnect?

In Claude, go to Settings › Connectors and remove or disconnect Axela. In ChatGPT, open Plugins and remove Axela. Nothing in your Axela account changes, and you can reconnect anytime.