Sales glossary
What is the Model Context Protocol (MCP)?
The Model Context Protocol (MCP) is an open standard that lets AI assistants such as Claude and ChatGPT connect to outside tools and data, introduced by Anthropic in November 2024.
Why it matters
Before MCP, connecting an AI assistant to a business tool meant a custom integration for every pair. Anthropic open-sourced the protocol in November 2024 (Anthropic, 2024), and it is now supported by Claude, ChatGPT and development tools such as Visual Studio Code and Cursor (modelcontextprotocol.io). A tool that offers an MCP server works in all of them.
For sales teams this means the assistant people already use every day can answer questions from real data: the calls, the transcripts and the scorecards, not a summary someone pasted in. The assistant asks the tool for what it needs, and the tool decides what the person signed in is allowed to see.
Example
On Monday morning a sales director asks Claude: “Which reps skipped the economic buyer this week?” Claude lists the calls from Drummer where the MEDDIC criterion scored low, and quotes one: in a negotiation call, at 23:14, the customer said “our CFO signs off anything above budget”, and the rep moved on. Each quote links to that moment in the call.
How Drummer handles it
Drummer runs an MCP server. Claude, ChatGPT and Claude Code connect to it after an OAuth sign-in, and can then read calls, transcripts and scorecard results, including the reasoning, the metrics and the links to each moment. Access is read-only and follows Drummer’s roles: a rep sees their own calls, a manager sees everyone’s.
What happens to an answer inside Claude or ChatGPT falls under that assistant’s terms, so connect the ones your company has approved. Inside Drummer itself, Ask Drummer answers the same questions with timestamps that jump the player. See Ask Drummer.
Give every rep a day back, starting next week.
Thirty minutes, on your own calls and your own CRM. No migration, nothing for your reps to learn.