MCP Integration Beta
Use earningscalls.dev as a Model Context Protocol connector inside Claude Desktop or claude.ai. Ask Claude natural-language questions about any of 17,000+ earnings call transcripts — Claude fetches the data automatically and answers with source citations.
What you get
Once connected, Claude can answer questions like:
- "What did NVIDIA's CFO say about data center growth in their last call?"
- "Compare guidance from MSFT and GOOGL's most recent calls. Where do they diverge?"
- "Which Fortune 500 companies mentioned agentic AI in their Q1 calls?"
- "Read me the Q&A section of TSLA's last call where analysts pushed back on production guidance."
No browser tabs, no copy-paste, no API client. Just questions and answers with primary-source quotes.
Setup — choose your path
Three ways to connect Claude, in order of simplicity:
Claude Desktop with Personal Connector URL
Generate a URL once from your dashboard. Paste it into Claude Desktop's config file. Done — no API key handling, fully revocable.
- Open your Dashboard → Claude Connectors
- Click Generate URL (give it a name like "MacBook" or "Team")
- Copy the URL — it looks like
https://earningscalls.dev/u/mct_xxx/mcp - Claude Desktop → Settings → Developer → Edit Config → paste as the
urlfield - Save, fully quit Claude Desktop (Cmd+Q on Mac), reopen. The 🔌 icon shows the tools.
Edit claude_desktop_config.json directly
If you prefer to use your raw API key instead of a connector URL, paste this block into your config file (Settings → Developer → Edit Config):
{
"mcpServers": {
"earningscalls": {
"url": "https://earningscalls.dev/mcp",
"headers": {
"X-API-Key": "ec_your_key_here"
}
}
}
}
Fully quit Claude Desktop (Cmd+Q on macOS), then reopen. Look for the 🔌 hammer icon in the chat input — that's your tools menu.
Add custom connector — Pro / Team accounts
In claude.ai, open Settings → Connectors → Add custom connector:
- Name:
EarningsCalls - Remote MCP server URL:
https://earningscalls.dev/mcp - Leave OAuth Client ID and Client Secret empty
- Click Add → a consent popup opens on earningscalls.dev
- Paste your connector URL or
ec_API key → Authorize Claude - Popup closes → start a new chat to see the 🔌 icon with tools
Available tools
Claude can invoke any of these when relevant to your question:
search_transcriptsFull-text search across 17K+ callsget_latest_callMost recent earnings call(s) by tickerget_call_transcriptFull text of a specific callget_speakersSpeaker-by-speaker segments (CEO, CFO, analysts)get_call_summaryAI summary: highlights, topics, metricsget_call_componentsStructured call sections + participantsget_company_infoSector, industry, exchange + all callsget_upcoming_earningsCalendar of upcoming reportslist_earningsCross-company filter by sector/date/industrylist_companiesBrowse companies by sector / exchange / namelist_sectorsAll 11 GICS sectors with countslist_industries100+ industries, optionally per sectorcount_mentions_by_tickerAggregate counts per ticker (F500 / S&P 500 analysis)Cost & usage
MCP tool-calls count 1:1 against your monthly API budget — same as direct REST API requests. A typical research session uses 3-5 tool-calls.
Requires an active subscription — any paid tier (Pro, Ultra, or Enterprise) unlocks the full tool set.
FAQ
Where is my API key stored?
If you use the connector URL, your API key never leaves earningscalls.dev — the URL embeds an opaque token that we resolve server-side. If you use the header-based config, Claude Desktop keeps the key locally; claude.ai stores it encrypted on Anthropic's backend.
What happens if I lose my laptop / leak a connector URL?
Revoke just that connector from your dashboard. The token is invalidated immediately (with up to 5 minutes of cache latency on the MCP server). Your API key stays unchanged — no need to rotate it.
Can I generate multiple connector URLs?
Yes — generate one per device or workspace. Each shows up in the dashboard with name, creation date, and "last used" timestamp. Useful for tracking which device a token is being used from before revocation.
Does this work with Cursor, Cline, or other MCP clients?
Yes. Any MCP-compatible client can use the same URL or header configuration. We test on Claude Desktop and claude.ai officially, but the protocol is standardized.
Why is it labeled Beta?
The hosted MCP server is in active development. Tool signatures and the auth flow may evolve over the next 1-2 months as MCP-spec details solidify. We'll announce any breaking changes via email to existing users before deploying them.
Get started in 60 seconds
Already a subscriber? Generate your URL now. Otherwise grab a Pro plan and connect.