Sales Meeting Prep with MCP: A Step-by-Step Playbook

Meeting prep is the 20 minutes before a sales call when a rep checks the calendar invite, the CRM record, the last call and recent emails. Most reps skip half of it when the day is full. With MCP, one AI assistant can read those sources in one request and hand back a short brief, with links back to each source.

This playbook is almost entirely read-only. The only write is a follow-up email saved as a draft, which a person reviews and sends.

What you need

Pick the servers that match your stack. Each one below has a published tool list.

• Calendar. Google's Calendar MCP server (list_events, get_event, search_events) is part of the Google Workspace MCP servers, in Developer Preview as of October 2026. If meetings are booked through Calendly, its supported tools list includes meetings-list_events, meetings-get_event and meetings-list_event_invitees.
• CRM. HubSpot's integration guide lists search_crm_objects, get_crm_objects and search_owners. See the HubSpot MCP server profile.
• Conversation history. The Gong MCP server has three tools: ask_account, ask_deal and generate_brief.
• Email. The Gmail MCP server lists search_threads, get_thread and create_draft.
• Public news. A web search server such as Exa (web_search_exa, web_fetch_exa).
• An AI client that every server supports. Check each profile; for example, Google lists Claude Enterprise, Pro, Max or Team plans for its Workspace servers.

The workflow

1. Find the meeting. Ask the assistant to call list_events (Google Calendar) or meetings-list_events (Calendly) for tomorrow, then get_event or meetings-list_event_invitees for attendee names and emails.
2. Match attendees to the CRM. Use HubSpot's search_crm_objects on the attendee emails and company domain. Pull the deal, stage, amount, owner and last activity. HubSpot returns up to 200 results per page.
3. Pull conversation insight. Call Gong's generate_brief for the account or deal. Gong's help center says it returns "a structured, multi-category summary (brief) for an account, deal, or contact." Use ask_deal for one focused question, such as open objections.
4. Ask for sources. Gong's includeSources parameter adds links to the calls and emails used. Gong says it turns on automatically when your prompt asks for sources.
5. Scan recent email. Use Gmail's search_threads with the prospect's domain and a date range, then get_thread on the most recent threads. Ask for open questions and promises made, not a full summary.
6. Check public news. Run web_search_exa for the company name plus the last 30 days. Keep only items with a source URL.
7. Assemble a one-page brief. Fixed sections: who is attending, deal status, what they care about, open risks, what we promised, suggested agenda, questions to ask. Each line carries its source.
8. After the call, draft the follow-up. Gmail's create_draft saves a draft. Google's Workspace MCP guide has no send tool for Gmail; the rep reviews and sends from Gmail.

Example prompts

• "List my calendar events for tomorrow with external attendees. For each, give attendee emails and the meeting title. Read only."
• "For the 10am meeting, search HubSpot for the attendees' company and open deals. Show stage, amount, close date and last activity."
• "Use Gong generate_brief for that deal and include sources. Then use ask_deal: what objections are still open?"
• "Search Gmail threads with that company's domain from the last 30 days. List any questions we have not answered and anything we promised to send."
• "Build my one-page brief in the standard format. Mark any line you could not source as unverified."

Guardrails

• Keep it read-only. Gong says its server "does not create, update, or delete data in Gong or the CRM." Do the same with other servers: turn off or require approval for CRM write tools during prep. Our lesson on MCP permissions and approvals shows how.
• Personal access. Gong's enablement guide tells admins to choose Personal access, which it says "means each team member connects with their own Gong credentials." Each rep should connect their own accounts for every server.
• Watch email content. Google's guide warns that untrusted data can carry an "indirect prompt injection attack." Prospect emails are untrusted. Keep create_draft as the only email write, and review every draft.
• Limit cross-tool leaks. When Gmail, CRM and web servers share one session, sensitive deal data could be passed to another tool. The MCP Security Center covers this cross-server leakage pattern.
• Private calls stay private. Gong says "private calls are excluded from all results." Do not work around that by pasting transcripts into the chat.
• Keep judgment human. The brief suggests questions. The rep decides the agenda and the ask.

What to measure

• Share of meetings with a brief generated before the call.
• Rep rating of each brief (useful, partly useful, not useful), collected in one click after the call.
• Errors found in briefs: wrong attendee, wrong deal stage, unsourced claim.
• Time from meeting end to follow-up sent, before and after rollout.
• Whether stage progression or next-step rates change for prepared meetings. Compare like with like, and treat early results as directional.

Next step

Start with one rep, two sources (calendar and CRM) and a fixed brief template. Add Gong and email once the basics are accurate. More task guides are in the MCP playbooks hub. If you want a prep workflow built into Claude Code for your sales team, see Claude Code consulting.

Frequently asked questions