Audelo

Audelo for AI assistants

Run your phone line
from your assistant

Ask what your AI receptionist handled while you were out. Have it ring a supplier. Text a customer back. On your own account, with a key you control.

Paste this into your assistant

Set up Audelo from audelo.ai/connect

Your assistant reads this page and walks you through it — or follow the steps yourself below.

12 tools Your API key Nothing stored our side
Grok Available now

Grok

Add Audelo as a custom connector. About a minute, and no approval needed.

Set up Grok →

Claude Available now

Claude

Add it as a custom connector on any paid plan. Same endpoint, same key.

Set up Claude →

Grok Bot Not yet

Grok Bot

xAI's AI teammates take connectors as Marketplace plugins rather than a custom MCP URL, so Audelo can't be added by hand the way it can in Grok.

Grok on the web works today →

Muse In review

Muse

Submitted to Meta's Muse connector directory. This turns on the moment it's approved.

Not yet available

Before you start

Two things, both from your Audelo dashboard.

An account with an agent set up

Any plan works — there's no plan gate on the API. You'll need at least one agent, and a phone number assigned to it if you want your assistant to place calls or send texts.

An API key, from API Keys

Tick only the scopes you want your assistant to have. Start read-only and add write access later if you want it to act.

agents:read calls:read analytics:read numbers:read calls:write · optional sms:write · optional

Shown once. Scopes are fixed at creation — to change them, make a new key.

Every setup below uses the same two values.

Server URL
https://mcp.audelo.ai/mcp
Auth header
Authorization: Bearer cgk_…
Grok

Set up Grok

Available now

Choose New Connector, then Custom.
Paste the server URL above.
Add the Authorization header using your key.
Save — Grok discovers the tools and they're live in conversation.
Claude

Set up Claude

Available now

Open Settings → Connectors.
Choose Add custom connector.
Paste the server URL above.
Add the Authorization header using your key.

Custom connectors need a paid Claude plan. Audelo isn't in Anthropic's directory yet, so add it as a custom connector rather than searching for it.

What you can ask

Once it's connected — in plain language.

“Ask my Audelo receptionist what came in while I was out — who called, what they wanted, and anything urgent.”

Read only

“Read me the transcript of this morning's call about the Henderson job.”

Read only

“How many calls did we take last week, and how long was the average?”

Read only

“Which of my agents is handling the most calls?”

Read only

“Have Audelo ring the supplier and ask when the order ships.”

Acts in the real world — needs a write scope

“Text that customer from my business number to say I'm running 15 minutes late.”

Acts in the real world — needs a write scope

What it can and can't do

Worth knowing before you hand an assistant your phone line.

Your key decides

The connector can only do what the key's scopes allow. A read-only key summarises what your agents handled and nothing more — asking it to place a call returns a clean refusal.

We store nothing

Your key travels with each request and is used only for that request. It is never written to disk on our side, and the connector holds no credentials of its own.

Acting costs money

Tools that dial or text reach real people and are metered against your prepaid balance. They are marked as acting in the real world, and refused when the balance runs out.

Compliance doesn't move

AI-disclosure and call-recording announcements are enforced our side and can't be switched off through the API. Personal opt-outs are suppressed unconditionally.

Full endpoint reference