Skip to content
VeraDial
For AI agents & assistants

Your AI assistant, connected to your business line

VeraDial answers your business calls 24/7. Connect the assistant you already use — Claude, ChatGPT, or any MCP-compatible agent — and it can read everything on your line: calls, screening summaries, voicemail transcripts, texts, and your receptionist setup. OAuth with your existing login. Read-only. No API keys.

Remote MCP server

https://api.veradial.com/mcp

Short Answer

VeraDial exposes a remote MCP server at https://api.veradial.com/mcp. Any MCP-compatible assistant can connect over OAuth 2.1 using the customer's existing VeraDial login and read that customer's own account — calls with AI screening summaries, voicemail and call transcripts, SMS threads, contacts, phone lines, receptionist configuration, and usage. Access is read-only, scoped per account, returns no audio, and requires no API keys. Claude and ChatGPT connect self-serve; other MCP clients get a one-time approval.

What your agent can read

Eyes on the whole line

Thirteen read-only tools cover the account. Ask “who called today and what did they want?” and your assistant answers from the actual records — not a guess.

Calls & screening

Recent inbound and outbound calls with the AI receptionist's screening summaries — who called, why, and how urgent — plus full transcripts where a call was recorded and transcribed.

Voicemail transcripts

Every voicemail with its transcript, read state, and caller — so your assistant can triage the inbox for you. Audio recordings are never exposed through the connector.

Text conversations

SMS threads on your VeraDial numbers, including what the AI texting assistant drafted or sent, with per-message direction and timestamps.

Contacts & follow-ups

Contact Memory summaries, interaction stats, and suggested call goals — the raw material for “who should I call back today?”

Lines & receptionist setup

Your phone lines with per-line receptionist and texting-assistant settings, plus the business identity and caller context your receptionist works from.

Plan & usage

Subscription status and remaining AI-call and translation minutes for the current period, so your assistant can answer “how much do I have left this month?”

Setup

Connected in three steps

Step 1

Get your VeraDial line

Build your AI receptionist and pick a business number in the VeraDial app — or hear it answer in the live demo first. The connector reads whatever your receptionist handles, so this is the part that does the work.

Step 2

Add the connector in your AI app

Claude (claude.ai, Desktop, mobile): Settings → Connectors → Add custom connector → paste the server URL.

ChatGPT (web, paid plans): enable Developer mode in settings, then add an app with the server URL and OAuth authentication.

Other MCP clients (Claude Code, Codex CLI, Cursor, …): point the client at the same URL — most accept a remote-server config like:

{
  "mcpServers": {
    "veradial": { "url": "https://api.veradial.com/mcp" }
  }
}

Clients other than hosted Claude and ChatGPT start in a pending state after consent — email support@veradial.com with the client name from the consent screen and we'll approve it, then reconnect once.

Step 3

Sign in and approve

Your AI app opens a browser window. Sign in with your VeraDial login, review the read-only capability list on the consent screen, and approve. That's it — ask your assistant to list your VeraDial numbers to confirm the connection. No API keys at any step.

Security model

Built like an auth boundary, not a demo

OAuth 2.1, audience-bound tokens

Connector tokens are minted specifically for the MCP server and rejected everywhere else — an app-session token can't call the connector, and a connector token can't touch the rest of the API.

Read-only, per-account

Every tool is scoped to the signed-in customer's own account. No write access, no cross-account reads, and rate limits on every call.

Transcripts yes, audio never

Transcript text is the product; audio recordings and raw provider payloads are never exposed through the connector.

Revocable in one step

Disconnect the app in its own settings and access ends; tokens expire automatically. VeraDial can also revoke any client server-side.

Reading this as an agent?

Machine-readable summaries of VeraDial live at /llms.txt and /llms-full.txt, with pricing at /pricing.md. The human step-by-step connection guide is at /help/connect-ai-assistant. Your user needs a VeraDial account to connect; the MCP server itself requires their OAuth consent — there is no anonymous access.

FAQ

Common questions

Is the connector read-only?

Yes — deliberately. The current tool set reads your account: calls, screening summaries, voicemail and call transcripts, texts, contacts, lines, receptionist setup, and usage. It cannot place calls, send messages, or change settings. Action tools are on the roadmap and will ship with explicit confirmation steps.

Which AI apps can connect?

Claude (claude.ai, Desktop, and mobile) and ChatGPT (web, on paid plans with Developer mode) connect self-serve in about a minute. Any other MCP-compatible client — Claude Code, Codex CLI, Cursor, and similar — uses the same server URL after a quick one-time approval by VeraDial.

Does it need an API key?

No. Authentication is OAuth 2.1 with your existing VeraDial login: your AI app opens a browser window, you sign in to VeraDial, review what can be read, and approve. There are no keys to create, copy, or leak.

Are call transcripts really shared with my AI?

Only with the AI app you connected, under your own account, and only when you ask something that needs them — that's the point of the connector. Audio recordings never leave VeraDial, every connection is scoped to your own account, and disconnecting the app in its settings cuts off access.

Does the connector cost extra?

No — it's included with your VeraDial account at no extra charge.

Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI, Inc. VeraDial is not affiliated with, sponsored by, or endorsed by either; names are used only to describe interoperability.

Audio demo

Hear Vera in action.

Play a short sample call, follow the transcript, and move into a personalized live demo when you're ready.

Play the sampleNo download · no form · start the live demo anytime