Recipes / Pre-meeting brief from CRM + web

Pre-meeting brief from CRM + web

HubSpot + Perplexity

Who it's for

AEs and founders who want a one-page brief before every external meeting without opening five tabs.

MCP servers

HubSpot Up · auth
https://mcp.hubspot.com
OAuth 2.1 with PKCE (MCP connector)
Perplexity Up · auth
https://api.perplexity.ai/mcp
OAuth or Bearer API key

Auth setup

HubSpot: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.
Perplexity: Sign in with OAuth, or pass an API key as a Bearer token for headless use.

mcp.json config for Claude Code and Cursor

Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.

{
  "mcpServers": {
    "hubspot": {
      "url": "https://mcp.hubspot.com"
    },
    "perplexity": {
      "url": "https://api.perplexity.ai/mcp"
      // headless alternative: "headers": { "Authorization": "Bearer YOUR_PERPLEXITY_API_KEY" }
    }
  }
}

Step-by-step prompts

Find my next meeting's contact and company in HubSpot. Pull deal stage, amount, last 5 activities and open tasks.
Use Perplexity to get news about the company from the last 30 days, plus anything relevant to our product category. Cite sources.
Write a one-page brief: who they are, where the deal stands, what changed since the last touch, three questions to ask, and risks.
Optionally log the brief as a note on the HubSpot deal, after I approve it.

Gotchas

HubSpot only shows records the connected user can see, so a rep's brief only covers that rep's deals.
HubSpot uses OAuth 2.1 with PKCE. For a scheduled or headless run, do the OAuth once interactively and let the token refresh.
Keep it read-only by default. Logging the note is the only write.

Vendor sites: HubSpot · Perplexity. If we join an affiliate program, these links will be labeled as affiliate links.