AI Assistants (MCP)
Connect Aura to Claude and ChatGPT so you can ask your assistant about your calls, pipeline, and revenue
AI Assistants (Claude and ChatGPT)
Connect Aura to Claude or ChatGPT and ask about your own data in plain language. "Prep me for my 2pm", "how did we do this week", "why are we losing deals" get answered from your live Aura account, without you opening the dashboard and reading a screen.
This uses MCP (Model Context Protocol), the open standard both Anthropic and OpenAI support for connecting apps to assistants.
The connector is read-only. It can look at your data and answer questions about it. It cannot book, cancel, reschedule, or reassign a call, and it cannot change anything in your account. See What it cannot do.
Connecting
You need an Aura account. Any team member can connect their own assistant, and they will see exactly what they can see in Aura, no more.
Open your assistant's connector settings
In Claude, go to Settings → Connectors → Add custom connector.
In ChatGPT, turn on Developer mode under Settings → Security and login, then add the server from Plugins. Custom connectors in ChatGPT need a Business, Enterprise, or Edu workspace.
Both assistants move these menus from time to time. If what you see does not match, their own guides are authoritative: Claude custom connectors and ChatGPT developer mode and MCP.
Enter the Aura server URL
Paste:
https://mcp.aura-app.aiThat is the whole URL. There is no path to add and no API key to copy.
Sign in to Aura
Your assistant opens an Aura sign-in page. Sign in as you normally would and approve access. Your assistant never sees your password.
Pick your organisation
If you belong to more than one Aura organisation, the connector asks which one rather than guessing. If you belong to exactly one, it selects it for you.
What you can ask
The connector is built around questions people actually ask, so most of these are answered in a single step rather than the assistant fetching a dozen things and stitching them together.
| Ask | What comes back |
|---|---|
| "Prep me for my next call" | The lead, their booking-form answers, their history with you, and what happened on any previous call |
| "How did we do this week?" | Booked, showed, closed, and revenue for the period, compared to the one before |
| "Why are we losing deals?" | The objections and loss reasons recorded on lost calls, grouped and ranked |
| "Which campaigns are actually paying?" | Spend against revenue by campaign, using the attribution Aura tracks from ad click through to payment |
| "How is the team doing this month?" | A per-rep scorecard for the period |
| "What is in the pipeline right now?" | Open opportunities and where they sit |
| "Show me everything on this lead" | The full lead or call record, by name, email, or from a previous answer |
You can follow up conversationally. The assistant keeps the thread, so "and the month before?" or "just Sarah's calls" work without repeating yourself.
What it cannot do
The connector is read-only, permanently, by design.
It will not book, cancel, reschedule, or reassign a call. Those actions send real calendar invites and emails to real prospects, and nothing un-sends an email. If an assistant could be talked into doing them, a confused or manipulated conversation would reach your customers.
It also cannot create webhook subscriptions. The connector returns text written by other people (lead notes, booking-form answers, quotes captured from prospects on calls), and a write capability combined with that text is a route for instructions hidden in a note to act on your account. Read-only means the worst case is an assistant telling you something inaccurate, rather than doing something on your behalf.
To take an action, use Aura.
What it can see
Your assistant sees what you see in Aura, resolved fresh on every request.
- Your organisation only. Every request re-checks your membership rather than trusting a saved answer, so access changes take effect immediately rather than when a session expires.
- Your role's limits apply. If your role only shows you your own leads and calls in Aura, that is what your assistant gets.
- Naming an organisation you are not in returns an error, not an empty result. "You have no calls" would be a misleading answer to a question about someone else's workspace.
Good to know
Large results are summarised, and the connector says so. If you ask something that spans hundreds of calls, it returns a manageable slice and states plainly that it did, pointing at the aggregate figure instead. That way a total is never quietly computed from a partial list.
Heavy use is throttled. There is an hourly allowance per connection and a daily one per organisation. Repeated questions stay cheap because they come from cache, so normal conversation will not reach it. If you do, the connector says so rather than failing silently, and lighter questions keep working.
Your conversations are not stored by Aura. The connector answers a request and returns the data. What your assistant retains is governed by Anthropic's or OpenAI's policies, not ours.
Troubleshooting
The connector will not connect. Check the URL is exactly https://mcp.aura-app.ai, with no trailing path. If your assistant reports an authentication error, disconnect and reconnect to restart the sign-in.
It says you are not a member of an organisation. You asked about an organisation your Aura account does not belong to. Ask "which organisations can I see?" and the connector lists the ones you can.
Answers look out of date. Period summaries are cached for a few minutes so repeated questions stay fast. Individual leads and calls are never cached. If a number looks stale, ask again shortly.
It refuses to book or change something. Working as intended. See What it cannot do.
Getting help
Ask in the chat bubble in the bottom right of any page in Aura, and say which assistant you are using and roughly what you asked. Do not send screenshots containing lead details unless you are comfortable sharing them.