CallVault - MCP Server That Injects Live Sales Call Context into Claude
Your AE is on a Zoom call with a prospect while Claude sits open doing nothing useful because it has no idea who the prospect is, what they said last time, or what deal stage they are in. CallVault is an MCP server that exposes your CRM deal history, call transcripts, and prospect LinkedIn data as tools Claude can query mid-conversation.
Difficulty
intermediate
Category
MCP & Integrations
Market Demand
High
Revenue Score
7/10
Platform
MCP Server
Vibe Code Friendly
No
Hackathon Score
🏆 9/10
What is it?
Sales reps using Claude in April 2026 copy-paste CRM notes manually before every call like it is 2014. CallVault is a Model Context Protocol server that connects to HubSpot and Gong, exposing three tools: get_deal_context, get_call_transcript_summary, and get_prospect_signals. When an AE opens Claude Desktop during a call prep session, Claude can pull the last three call summaries, current deal stage, and recent LinkedIn activity without the rep touching anything. This transforms Claude from a generic chatbot into a contextual sales copilot. Buildable right now because the MCP SDK is stable, HubSpot and Gong both have public REST APIs, and Claude Desktop supports local MCP servers as of late 2024.
Why now?
Claude Desktop MCP support went stable in late 2024 and the April 2026 vibe-coding wave means thousands of developers are building MCP servers monthly — the Anthropic MCP directory is actively surfacing new servers to early adopters right now.
- ▸get_deal_context tool that fetches HubSpot deal stage, owner, and last activity for a named company.
- ▸get_call_transcript_summary tool that pulls the last three Gong call summaries and key objections.
- ▸get_prospect_signals tool that returns recent deal notes and next steps from CRM.
- ▸Claude Desktop config snippet auto-generator so setup takes under five minutes.
Target Audience
B2B AEs and SDRs at SMB SaaS companies using Claude Desktop, ~300k such reps in the US.
Example Use Case
Marcus, an AE at a 60-person SaaS company, opens Claude Desktop before a renewal call, asks 'what did we discuss last time and what is their current deal stage' and Claude returns a summary pulled live from HubSpot and Gong in four seconds.
User Stories
- ▸As a B2B AE, I want Claude to pull my HubSpot deal context automatically, so that I stop spending 10 minutes copy-pasting CRM notes before every call.
- ▸As a sales manager, I want my reps using Gong transcript summaries in Claude, so that follow-up emails are grounded in what prospects actually said. As an SDR, I want Claude to surface deal objections from the last call, so that I can tailor my outreach without re-listening to recordings.
Acceptance Criteria
get_deal_context: done when Claude returns current HubSpot deal stage and last activity for a named company within 5 seconds. get_call_transcript_summary: done when Claude returns summarized last 3 Gong calls with key objections listed. Auth: done when HubSpot OAuth token is stored locally and refreshed automatically without user re-auth. Pro Gate: done when Gong tool returns error message with upgrade link when no valid Stripe license key is present.
Is it worth building?
$19/month x 150 seats = $2,850 MRR at month 4. $19/month x 500 seats = $9,500 MRR at month 9.
Unit Economics
CAC: $0 via organic GitHub and r/sales. LTV: $228 (12 months at $19/month). Payback: immediate. Gross margin: 94%.
Business Model
One-time license or $19/month SaaS per seat.
Monetization Path
Free tier: HubSpot only, 10 deal queries/day. Pro at $19/seat/month: Gong transcripts, unlimited queries, Slack deal alerts.
Revenue Timeline
First dollar: week 2 via first Pro seat. $1k MRR: month 3. $5k MRR: month 7.
Estimated Monthly Cost
Vercel (license validation): $10, Stripe fees: $15, HubSpot API: free tier. Total: ~$25/month at launch.
Profit Potential
Side income to full-time at $5k-$15k MRR with team licenses.
Scalability
High — add Salesforce, Outreach, and Apollo integrations, expand to team license model.
Success Metrics
Week 1: 30 installs via GitHub. Month 1: 15 paid seats. Month 3: 80 paid seats.
Launch & Validation Plan
Post GitHub repo in r/sales and Claude MCP Discord, get 50 stars before adding Stripe paywall.
Customer Acquisition Strategy
First customer: post a 60-second demo video on LinkedIn showing Claude pulling live deal context mid-call-prep, DM 10 AEs who comment asking how to install it. Ongoing: r/sales, Anthropic MCP directory listing, ProductHunt, LinkedIn content.
What's the competition?
Competition Level
Low
Similar Products
Gong Engage (full platform, not Claude-native), HubSpot AI (in-app only, not MCP), Chorus.ai (call recording only, no Claude integration).
Competitive Advantage
No existing MCP server targets sales call context specifically — this is a direct workflow integration that generic AI tools cannot match without custom dev work.
Regulatory Risks
CRM data processed locally via MCP server — GDPR risk low if no data stored server-side. HubSpot OAuth scopes must be minimal and documented.
What's the roadmap?
Feature Roadmap
V1 (launch): HubSpot deal context, Gong transcript summary, Claude Desktop MCP config. V2 (month 2-3): Salesforce integration, Slack deal alert tool, Pro license tier. V3 (month 4+): team admin dashboard, Apollo prospect enrichment tool, usage analytics.
Milestone Plan
Phase 1 (Week 1): MCP server ships with HubSpot and Gong tools, published to npm. Phase 2 (Week 2-3): Stripe Pro gate, README with install GIF, 30 GitHub stars. Phase 3 (Month 2): 80 paid seats, Salesforce integration in beta.
How do you build it?
Tech Stack
MCP SDK (TypeScript), HubSpot REST API, Gong REST API, Claude Desktop as host, Node.js, Stripe for license — build with Cursor for MCP server logic.
Suggested Frameworks
MCP SDK TypeScript, axios, zod
Time to Ship
1 week
Required Skills
MCP SDK TypeScript, HubSpot and Gong REST APIs, OAuth token handling.
Resources
MCP SDK docs, HubSpot CRM API docs, Gong API docs, Claude Desktop MCP integration guide.
MVP Scope
src/index.ts (MCP server entry), src/tools/deal-context.ts, src/tools/transcript-summary.ts, src/tools/prospect-signals.ts, src/hubspot-client.ts, src/gong-client.ts, src/auth.ts (OAuth token store), README with install gif, package.json.
Core User Journey
Clone repo -> add HubSpot API key to claude_desktop_config.json -> ask Claude about a deal -> see live CRM data in response -> upgrade to Pro for Gong transcripts.
Architecture Pattern
Claude Desktop sends tool call -> local MCP server receives request -> HubSpot or Gong REST API called with stored OAuth token -> response formatted and returned to Claude -> Claude generates context-aware response for AE.
Data Model
No server-side storage in V1. Local config stores HubSpot and Gong OAuth tokens. Tool responses are ephemeral and returned directly to Claude context.
Integration Points
MCP SDK for Claude Desktop tool exposure, HubSpot REST API for deal and contact data, Gong REST API for call transcript summaries, Stripe for Pro license validation, local JSON for OAuth token storage.
V1 Scope Boundaries
V1 excludes: Salesforce integration, team admin dashboard, mobile support, automated call scheduling, any server-side data storage.
Success Definition
An AE at a company the founder has never contacted installs CallVault, uses it on a real sales call, and upgrades to Pro without any onboarding help.
Challenges
MCP server distribution is still niche — most AEs do not know Claude Desktop supports plugins, so education is the biggest GTM barrier, not the build.
Avoid These Pitfalls
Do not build a web dashboard before validating the MCP tool workflow converts users to paid. Do not store CRM data server-side in V1 — it adds GDPR complexity that kills the launch. Finding first 10 paying AEs takes 3x longer than building the server.
Security Requirements
OAuth tokens stored locally via keytar OS keychain, no server-side token storage in V1, Stripe license key validated via HTTPS endpoint, input validation on all tool parameters via zod schemas.
Infrastructure Plan
No server hosting needed for free tier MCP, single Vercel serverless function for Pro license validation, GitHub for distribution, Stripe for billing.
Performance Targets
Tool response under 5 seconds including HubSpot and Gong API calls. No DAU targets at launch — measure npm weekly downloads and GitHub stars.
Go-Live Checklist
- ☐HubSpot OAuth flow tested end-to-end
- ☐Stripe license validation tested
- ☐No server-side CRM data stored confirmed
- ☐Custom domain for landing page live
- ☐Privacy policy published
- ☐5 beta AEs tested on real deals
- ☐Rollback plan via npm version revert
- ☐Demo video recorded
- ☐GitHub README and ProductHunt draft ready.
How to build it, step by step
1. Run npx @modelcontextprotocol/create-server callvault and select TypeScript template. 2. Install axios, zod, and keytar for secure token storage. 3. Build src/hubspot-client.ts with getDeal and getContacts methods using HubSpot REST API. 4. Build src/gong-client.ts with getCallTranscripts method using Gong REST API. 5. Build src/tools/deal-context.ts as MCP tool with zod schema for company name input. 6. Build src/tools/transcript-summary.ts as MCP tool returning last 3 call summaries. 7. Register all tools in src/index.ts MCP server entry point. 8. Write README with exact claude_desktop_config.json snippet and animated install GIF. 9. Add Stripe license key validation as middleware that gates Gong tool behind Pro check. 10. Publish to npm, post GitHub link in r/sales and Anthropic MCP Discord with demo video.
Generated
April 4, 2026
Model
claude-sonnet-4-6