Connect Claude (MCP)

Query your calls, transcripts, scripts, campaigns and team from Claude, with your own Paradialer permissions.

Paradialer exposes an MCP server: once connected, Claude (claude.ai, Claude Desktop or Claude Code) can query your Paradialer data — calls, AI summaries and transcripts, contacts, scripts, campaigns, team — in plain language, start the transcription of a call that doesn't have one yet, and fix the outcome of a past call. You connect with your own Paradialer account: Claude sees exactly what you see, no more and no less.

Mostly reading, two possible actions

Claude reads your data; no contact and no campaign is created or modified from Claude. Two actions are possible: starting the transcription of a call, and changing the outcome of a finished call (see below). A manager sees the whole organization; an SDR only sees their own calls.

Connecting

From claude.ai or Claude Desktop

Open Settings → Connectors in Claude.
Click Add custom connector.
Paste the URL: https://app.paradialer.com/api/mcp.
Claude sends you to the Paradialer sign-in page: sign in (with your 2FA code if you've turned it on).
On the Authorize access screen, click Authorize.

The Paradialer connector shows up in Claude with its tools. That's it — once per account.

From Claude Code

claude mcp add --transport http paradialer https://app.paradialer.com/api/mcp

Then /mcp in Claude Code to finish the connection (same sign-in page + authorization).

What you can ask

A few examples, to adapt:

"Summarize my calls from this week."
"Which prospects said yes to a meeting this month?"
"Show me the transcript of my last call with Chrystelle Vivier-Merle."
"Which objections come up the most in the Q4 campaign?"
"Compare each rep's meeting rate over 30 days." (manager)
"What did I promise Serge Mukong last time?"
"Summarize the SaaS campaign script and its objection handling."
"My call yesterday with X was actually a booked meeting: fix the outcome."

Claude chains the tools itself: it finds the contact, lists their calls, then opens the transcript.

What Claude sees

Tool	What it returns
Contacts	Search by name, company, email, phone or HubSpot id; date of the last call.
Calls	The log with its filters (period, agent, campaign, outcome, status, duration…).
Call detail	Contact, outcome, notes, AI summary and transcript (if the call was transcribed).
Transcript	The full transcript and summary of a call; or generates it if it doesn't exist yet.
Campaign stats	Calls, connects, meetings, rates, breakdown by outcome, over a period.
Agent activity	The same metrics per rep (managers).
Campaigns, team	Lists and their main information.
Scripts	The list of scripts and the content of one: text, sections and objections; for a PDF script, the text extracted from the PDF (a scanned PDF has no readable text).
Outcomes	The organization's catalogue of call outcomes (meeting booked, not interested, voicemail…); and changing the outcome of a finished call.

Visibility rules are the app's own: a manager or admin sees the whole organization and can filter by rep; an SDR only sees their own calls and stats — even when they ask for a colleague's.

Generating a transcript from Claude

If a call hasn't been transcribed yet, Claude can start the transcription itself ("transcribe my last call with X"): it's exactly the Transcribe + summarize button on the call page, with the same cost and the same wait (up to 30s). One call at a time — no batch transcription from Claude. See AI transcription.

Changing a call's outcome from Claude

Claude can change the outcome of a finished call ("that call was a booked meeting"), exactly like the outcome edit button on the call page. An SDR only changes their own calls, a manager the organization's. The call's HubSpot activity is updated with the new outcome; the contact's status in the campaign doesn't move. Only calls where a human picked up can be changed from Claude: a call with no answer, a failed one, one abandoned before the answer or one that hit voicemail is refused, so connect stats aren't skewed. For those cases, change the outcome directly in Paradialer.

Removing access

Delete the Paradialer connector in Claude's settings (Connectors → Paradialer → Remove). Claude will no longer have access to your data; you can reconnect it at any time.

If something goes wrong

After signing in, I land on the dialer instead of the "Authorize access" screen — start adding the connector again from Claude; if it persists, contact us.
Claude says "not found" — the call, contact or campaign asked for doesn't exist in your organization, or you're not allowed to see it (another rep's call, if you're an SDR).
The connector won't connect — check that the URL is exactly https://app.paradialer.com/api/mcp and that you're signed in to Paradialer with the right account.