- “Create an inbound receptionist that books appointments.”
- “Show me why my last campaign call failed.”
- “Add three leads to my follow-up campaign and start it.”
It’s a remote MCP server secured with OAuth 2.0. You connect once, sign in to approve, and
every action stays scoped to your own Autocalls account — the connector only ever sees and
changes your data.
What you can do
Build & refine assistants
Inbound and outbound: system prompt, voice, language, model and call behaviour. Attach
knowledgebases (your documents) and mid-call tools (live API lookups during a call).
Run outbound campaigns
Create campaigns, add and manage leads, and start, pause or resume them.
Review & improve
List calls, read full transcripts and post-call evaluations, then update the assistant or its
tools — a complete build → review → improve loop.
Manage your account
Knowledgebases & documents, phone numbers & SIP trunks, WhatsApp senders & templates,
conversations, folders, labels, API keys and your blacklist.
Before you start
- An Autocalls account at app.autocalls.ai — or your white-label provider’s domain.
- An active plan for the features you use (some actions consume call minutes or chat credits).
Your connection link
This is the secure address Claude and ChatGPT use to reach your account. Copy it — you’ll paste it during setup, then sign in to approve.White-label customers: use your provider’s domain instead —
https://{your-domain}/mcp.
The branding follows the domain, so you only ever see your provider’s brand.Add the connector
- Claude
- ChatGPT
Add a custom connector
Click the + button in the top-right of the Connectors panel, then choose Add custom
connector.

Name it and paste your link
Type any name (e.g. Autocalls), paste your connection link into Remote MCP server URL,
leave the OAuth fields empty, then click Add.

Try it
Start a new chat in Claude or ChatGPT and ask, for example:Build
“Create an inbound receptionist for my dental clinic that books appointments and answers FAQs.”
Improve
“Read my last 5 calls and tell me what my assistant got wrong.”
Integrate
“Create a mid-call tool that looks up an order by number from our API.”
Run
“Set up an outbound campaign for this week’s leads and start it.”
Security & privacy
- OAuth 2.0 with a branded consent screen — no API key is ever pasted into the chat client.
- Scoped to your account — the connector can only see and change your own data.
- Secrets masked — auth tokens stored on your tools are never returned in plain text.
- No chat-history harvesting — the connector acts only on your Autocalls resources.
- Privacy policy: autocalls.ai/privacy-policy.
FAQ
Which AI apps can I use it with?
Which AI apps can I use it with?
This guide covers Claude and ChatGPT. The connector is a standard remote MCP server, so it
also works with any other MCP-compatible client (for example Cursor or VS Code) — the setup is the
same: add a custom connector and paste your connection link.
Do I need an API key?
Do I need an API key?
No. Connection is handled by OAuth — you simply sign in to your Autocalls account and approve.
No key is pasted into the chat app.
Is it safe to connect?
Is it safe to connect?
Yes. Every tool is scoped to your own authenticated account, write and destructive actions ask for
confirmation, and any integration secrets you’ve stored are masked in responses.
Will it spend my balance?
Will it spend my balance?
Only when you explicitly ask it to place a call or send an SMS/WhatsApp — and it confirms first.
Building and editing assistants, reading calls, and managing your account don’t place calls.








