Pharo + Claude MCPLive
Pharo runs a native Model Context Protocol server. Connect it to Claude Desktop or ChatGPT to query live campaign results, run deal inspection prompts, and analyse call objections in natural language — without exporting anything.
Ask “which buyer objections came up most on calls this week?” or “summarise account signals for Nimbus Freight.”
Have Claude read call transcripts and campaign performance together, and suggest script revisions from what actually happened on the calls.
Asked about ramp time for new SDRs. Wants to see it on their own list.
Set from the call disposition.
Connect over standard MCP endpoints in seconds. Nothing is copied into a warehouse first.
pharo mcp add --client claude
A Model Context Protocol server over your Pharo campaigns, call transcripts and account context. Connect it to Claude Desktop, ChatGPT or another MCP client and you can query live results in natural language without exporting anything into a warehouse first.
Campaign results, call transcripts and account context, scoped and read-only by default. Access is granted per client and is revocable per client.
No. That is the point of it — MCP is a standard endpoint the client connects to directly, so nothing is copied anywhere in order to be asked a question.
The orchestration layer runs on Nango, so most of the long tail is configuration rather than engineering. If the one you need is not here, tell us which and it moves up the queue.
Get started
Ready to eliminate dead dials and marked-up credits?
Seven days, 1,000 credits, no credit card. Or thirty minutes with the two people who would do the work.
