A coding agent such as Codex or Cursor queries HubSpot deals through the MCP server, writes a forecast in Markdown, and saves it to Notion for the sales lead to review.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For checking deal-stage forecast assumptions.
Separate seller-confirmed facts from probabilities and model suggestions. Choose one for analysis of a reviewed data extract; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Inspectable calculations come before narrative convenience. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Record export date, filters and units; save calculations with the result. The source ledger still needs reconciliation.
Reviewed 2026-10-21. This page applies a shared comparison for “analysis of a reviewed data extract” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
The sales lead owns the final forecast.
Watch out for
CRM stages lag reality. Treat the forecast as a draft for the sales lead to correct, and check that the agent can read only the deals it should see.
Starter prompt
Read open deals from HubSpot with stage, amount and close date. Write this week's forecast in Markdown: committed, best case and at risk, what changed since last week, and the three deals that most need attention. Save it to our Notion forecasts page as a draft. I will review and adjust it before it goes to the team.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini
To verify
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
HubSpot: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Notion: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked
HubSpot’s remote MCP server reads deals, companies, contacts and activities, and every action respects the connected user’s HubSpot permissions. Use explicit stage, close-date and owner filters, and verify the available actions for your account. Notion MCP can create the page only in an authorized workspace and destination where the connected user has write permission. The sales lead owns the final numbers.
Set it up
Connect HubSpot’s remote MCP server as a user who can see the whole pipeline, and Notion MCP for the output page.
Write the forecast rules down once: which stages count as commit, best case and pipeline, and how to treat deals past their close date.
Save a dated snapshot and compare it with the previous snapshot. If the earlier state is unavailable, say so; a current deal list alone cannot establish changes since last week. Flag missing amounts, currencies and close dates.
The sales lead reviews and adjusts the numbers before sharing.
Deals outside the connected user’s scope will be missing, so show coverage and exclusions in the report. Treat forecast categories as documented business rules, not model guesses. Use an approved draft destination and require review before broader sharing. This combined workflow has not been executed.
Sources
HubSpot MCP · HubSpot · official · accessed 2026-10-16