Skip to content
Guide ·

Connecting Fathom, HubSpot and Stripe to your proposal workflow with MCP

A practical guide to wiring call recordings, CRM deals and payments into proposal.here using Model Context Protocol servers and a Stripe restricted key.

YZ 6 min read

In short: proposal.here connects to call recorders (Fathom, Fireflies, Gong) and CRMs (HubSpot, Salesforce, Pipedrive) through their MCP servers: paste the server URL and a token, click connect. Fathom and HubSpot fall back to their REST APIs with the same key, and a transcript can always be pasted directly. Stripe connects with a restricted key that can write Products, Prices and Payment Links; money goes to your Stripe account. Keys are encrypted at rest, never returned by the API, and belong to one workspace.

Why MCP

Model Context Protocol (MCP) is an open standard that lets tools expose their data to AI applications through a uniform interface. Fathom, Fireflies, Gong, HubSpot and others now run remote MCP servers. Instead of building a bespoke integration for each vendor, proposal.here speaks MCP once and discovers each server's tools at connection time.

For you that means: paste a server URL and a token, click connect, done. No OAuth app registration, no webhooks.

Call recording

  1. In proposal.here open Settings → Connections and choose your recorder.
  2. The server URL is pre-filled for Fathom, Fireflies and Gong. For other tools, paste the MCP URL from the vendor's docs.
  3. Create a token in the vendor's settings (Fathom: Settings → Integrations → API; Fireflies: Integrations → API key; Gong: ask an admin to create an MCP integration) and paste it.
  4. Click Connect. proposal.here lists the server's tools and confirms it found a way to list calls and fetch transcripts.

If a vendor's MCP server is unavailable, Fathom connections fall back to Fathom's REST API with the same key. You can also paste a transcript directly when creating a proposal.

CRM

The same flow applies to HubSpot, Salesforce, Pipedrive or any CRM with an MCP server. For HubSpot, create a private app with read access to deals, contacts and companies and paste its access token. proposal.here tries HubSpot's MCP server first and falls back to the CRM REST API, so deal search works either way.

Once connected, the New proposal screen lets you search deals; selecting one fills in the company and contact and stores the deal id on the proposal.

Stripe

Create a restricted key in Stripe with write access to Products, Prices and Payment Links. Paste it under Connections → Stripe. When a proposal has a pricing table, Create payment link turns each line into a Stripe price and generates a payment link that redirects back to the proposal after checkout. Money goes to your Stripe account; proposal.here never touches funds.

Security

Tokens and keys are encrypted at rest and never returned by the API after you save them. Connections belong to your workspace; members of other workspaces cannot see or use them. Owners and admins manage connections; members can use them to create proposals.

Keep reading