CallGrid MCP
Ask your call data anything.
Connect CallGrid to Claude or ChatGPT and ask in plain English. No report builder, no exports, just answers, charts, and optimization plans built from your own numbers.
Trusted by enterprise call buyers and sellers. Read only, so it is safe to share with your team.
What it is
A hosted MCP server for your account.
MCP, the Model Context Protocol, is the open standard that connects AI assistants to outside tools. CallGrid runs a hosted MCP server, so there is nothing to install and no code to write.
Add one URL, authorize your account once with no keys, and ask. Your assistant can now read your live CallGrid data and answer in plain language.
Paste mcp.callgrid.com/mcp into your assistant.
Sign in to CallGrid to connect. Nothing to copy or paste.
Type a question and get answers built from your own data.
Ask in plain language
It keeps context across the conversation.
Ask a question, then refine it. Each answer pulls live from your account. No report builder, just questions.
Last week you ran 30,710 billable calls for $2.41M in revenue and $612K in gross profit.
Cardinal Leads led on revenue at $902K, followed by Summit Leads and Apex Reach.
Bluepeak had the lowest connect rate at 41%, well below your 63% average. Most drop off happened before bid.
No report builder, just questions. Demo data shown.
It builds the report
It does not stop at numbers.
Ask for a campaign optimization brief and the assistant returns a finished analysis: a margin diagnosis, charts, three ranked levers with estimated lift, and a change list. Here is the kind of output it builds, generating itself as you arrive.
ACA Inbound Premium
This campaign earns $2.86M but keeps only 14.8%, the thinnest margin of any major campaign in the account. Most of that gap traces to a single routing decision. Re-tuning three settings could add an estimated $1.07M in annual revenue without buying one new call.
The margin gap
Thirteen buyers bid on this campaign. Twelve pay $34 to $39 per billable call at roughly 22% margin. One, Cardinal Leads, the anchor, pays $32.19 at 11.1% margin, yet receives 64% of every call. The whole margin problem is one dot sitting alone, far to the left.
Lower revenue per billable call on the anchor versus the $36.52 peer blend.
Of all calls route to the anchor, 58,235 billable calls priced below every other buyer.
Margin headroom: peers run ~22% vs the anchor's 11.1% on identical traffic.
Three settings to change
Each lever is independent and reversible. Estimates use this campaign's own observed rates: the peer buyers already bill these exact calls at the higher price.
Move a share of anchor billable volume into the existing 12-buyer pool at their proven $36.52 rate. Source payouts are unchanged, so every dollar of uplift is margin.
All 37 sources run a flat bid today. Conversion ranges from 10% to 39%. Bid up the proven converters and bid down or gate the laggards so premium buyers can raise their caps.
Real inbound calls are lost before a buyer picks up: 3,433 no-connects, plus no-answers, busies, and duplicates. Tighter failover and dedup windows convert a slice of this waste into billable calls.
What it adds up to
Levers 1 and 2 lift price on calls you already win, so they fall almost entirely to profit. Lever 3 adds thin-margin volume on top.
profit
routing
bidding
recovery
profit
Revenue and profit lift figures are estimates built from your own data, not guarantees.
The change list
Concrete settings to adjust, ordered by impact. The first three are the levers above; the last three protect revenue and data quality.
Add a premium-buyer tier above the anchor
Insert the top four peers into the routing waterfall ahead of the anchor, sized to start a 25% volume shift.
Set per-source bid adjustments
Bid up Meridian Media, Vantage Media, and Summit Leads. Bid down or gate the laggards. Replace the blanket flat bid.
Tighten failover and concurrency
Add overflow targets and raise buyer concurrency at peak to claw back part of the 3,433 no-connects.
Remove the demo source from production
A source labeled Demo Source is wired into this revenue campaign. Detach it before it misroutes paid traffic.
Investigate the Riverbend source
Average call 2m 03s vs the campaign's 5m 33s, only 10% conversion. Likely misrouting or low intent. Fix or pause.
Fix the Northstar no-connect rate
27.6% of Northstar calls never connect vs a 3.5% campaign norm, about 212 recoverable calls in one source.
Modeled on a real optimization brief. Account, campaign, buyer, and source names are invented; figures are illustrative.
Prompts to steal
Start with a question that pays for itself.
Click a card to run it in the demo above, or copy it into your own assistant.
Make an HTML report with charts on my top campaign, plus ranked changes with estimated revenue lift for each.
Pull my bid stats for the last 7 days, group the top rejection reasons, and tell me the calls and revenue I am losing to each.
Rank my buyers by conversion and revenue per call, flag the underperformers, and draft renegotiation talking points.
Compare my traffic sources by billable rate and revenue per call in a chart, then tell me which to scale and which to cut.
Show me the funnel from pings to bids to accepted calls and point to the biggest drop off.
Check the webhooks on all my campaigns and flag any missing a postback for converted events.
Read only
Safe to share with your whole team.
Today the CallGrid MCP surfaces and analyzes your data. It does not place calls, create or edit campaigns, move numbers, or change settings. Hand it to anyone who needs answers but should not be editing the account.
Automation
Or let it run on a schedule.
The same read-only MCP connection can run on a schedule and deliver a finished report into Slack, Gmail, Google Sheets, or Notion, with no one logging in to run it. CallGrid stays read only, and the delivery is done by your destination connector.
See MCP AutomationsA finished report writes and delivers itself into the tools your team already uses.
Slack
Gmail
Google Sheets
NotionCallGrid stays read only. The delivery is performed by your destination connector, with the permissions you control in that tool.
Connect
Works in Claude, ChatGPT, and any MCP client.
Add the server, authorize once, and ask. Setup takes about 30 seconds.
- 01Open Settings, then Connectors.
- 02Add a custom connector with the CallGrid server URL.
- 03Authorize your CallGrid account, then ask.
- 01Open Settings, then Connectors.
- 02Add the CallGrid server URL as a new connector.
- 03Authorize your CallGrid account, then ask.
And any MCP client that supports custom connectors.
Where it fits
One source of truth, many ways in.
The MCP reads the same live data as the rest of CallGrid. Use the dashboard, the API, or your assistant.
Reporting
The same numbers, in the dashboard your team already knows.
Real-Time Bidding
Bid and ping data, live, the moment a call comes in.
Webhooks and postbacks
For programmatic access and conversion events.
Scheduled report automations
Have these reports write and deliver themselves into Slack, Gmail, Sheets, or Notion on a schedule.
FAQ
Questions, answered.
A hosted MCP server that connects your CallGrid account to AI assistants like Claude and ChatGPT, so you can ask about your data in plain language and get back charts, reports, and optimization plans.
Claude and ChatGPT today, plus any client that supports the Model Context Protocol.
No. There is nothing to install and no code to write. Add one URL, authorize your account once, and ask.
It reads the same live reporting data you already see in CallGrid. It is read only, so it cannot change anything in your account.
No. The MCP is read only today. It surfaces and analyzes data, and cannot place calls or edit settings.
Add the server URL mcp.callgrid.com/mcp in your assistant, authorize your CallGrid account once, and start asking.
The CallGrid MCP is available to CallGrid customers.
Stop building reports. Start asking.
Connect your account and ask your call data anything.