HubSpot MCP for AE chat (L3)
AEs ask 'show me my deals slipping past close date with no activity in 14 days' in chat. HubSpot MCP returns the answer. Self-serve ops.
The steps
- 01
Approve the HubSpot connection and least-privilege access
The Model Context Protocol (MCP) allows an AI assistant to read approved HubSpot data. Start with HubSpot's current official MCP setup, not an unreviewed registry package or a token copied into a rep-owned file. • A HubSpot Super Admin or security owner reviews and approves the connection in Connected Apps and App Governance. • Grant only the read access required for deals, contacts, and owners. Do not grant write access for a read-only deal review workflow. • Record the connection owner, approved users, permitted objects, and review date. • Test with a non-sensitive record before opening access to the AE cohort. The owner is the RevOps Admin with IT or security approval. Pitfall: treating one broad private-app token as a shared team credential. That removes per-user accountability and widens the blast radius. Definition of done: the connection is admin-approved, least-privilege, limited to the pilot cohort, and documented in the app inventory. Source: https://developers.hubspot.com/blog/build-with-confidence-app-governance
- 02
Link MCP to Claude Desktop
Connect HubSpot through the approved MCP connection flow in the AI client your company supports. Keep the authorization tied to the individual user or an approved managed identity. Do not distribute a shared private-app token to AE laptops. • Confirm the approved HubSpot connection appears in the client's tool list. • Verify the signed-in user and permitted portal before the first query. • Run one read-only test against a known deal and confirm the response links back to the correct HubSpot record. The owner is IT or RevOps, not the individual AE. Pitfall: a successful connection icon proves authentication, not correct portal access or safe permissions. Definition of done: the pilot user can read one approved deal, cannot perform an unapproved write, and the access is attributable to that user.
- 03
Deploy Starter Prompt Library Deployment
AEs need to know how to phrase requests to get accurate deal hygiene data. You must provide a 'Cheat Sheet' of 10 specific prompts. • Example 1 (The Slip Prompt): 'Look at all my deals in the [Pipeline Name] pipeline. Show me which ones have a Close Date in the past or in the next 7 days, but have zero logged activity in the last 14 days.' • Example 2 (The Gap Prompt): 'Which of my deals over $50k are missing a Next Steps field update since Monday?' • Example 3 (The Context Prompt): 'Give me a summary of the last 3 emails and meeting notes for the [Company Name] account.' Distribute these via a pinned Slack message or a HubSpot Dashboard sidebar. The Owner is the Sales Enablement Manager. Time estimate: 45 minutes. Pitfall: Using technical jargon like 'Property Name' instead of 'Field Name' in prompts. Definition of Done: A PDF or Notion page with 10 tested prompts is shared with the AE team.
- 04
Enable AE Self-Service Workflows
Run a 30-minute training session for the AEs. Show them how to use the 'Slip' prompt to prepare for their 1:1s with managers. • Demo the live query: 'Assistant, show me my deals slipping past close date with no activity.' • Explain that MCP acts as a 'read-only' layer (or constrained write) so they don't accidentally delete data. • Teach them to verify the AI's output by clicking the provided HubSpot record links. • Show them how to 'bulk-check' accounts before a cold-calling block. The Owner is the Sales Manager or RevOps Lead. Time estimate: 30 minutes. Pitfall: AEs may treat the AI as a search bar; remind them it is an 'analyst' that can calculate durations and compare dates. Definition of Done: Every AE has successfully run one 'Slipping Deals' query in their personal Claude instance.
- 05
Establish Security & Audit Logs
The MCP can move CRM data into another interface, so approval and monitoring happen before and after launch. • Use HubSpot Connected Apps and App Governance to keep an approved inventory and control which connections teams may use. • Review connection activity and API-call volume weekly during the pilot. Investigate unusual contact exports or repeated broad queries. • Remove access when a user leaves the cohort, and review scopes whenever the workflow changes. The owner is the RevOps Admin or Security Officer. Pitfall: checking logs without an allow-list or named owner only documents exposure after it happens. Definition of done: the connection is allow-listed, every pilot user is attributable, thresholds are documented, and removal has been tested. Source: https://developers.hubspot.com/blog/build-with-confidence-app-governance
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.