What the agent gets
- CRM reads across standard and custom object types, by search, by SQL, or by ID.
- Schema and property discovery, so the agent can find the right object type and internal property names without being told.
- Conversation reads from HubSpot inboxes, including ticket transcripts and support case messages.
- Marketing analytics: campaign attribution, content performance, and marketing email results.
- Campaign, landing page, and marketing email writes, if you enable the write tools.
Setup
HubSpot does not let Rippit register itself as an OAuth client, so an admin creates an MCP auth app in HubSpot once and pastes its credentials into Rippit. Both steps are one-time and apply to the whole organization.1
Create an MCP auth app in HubSpot
In your HubSpot account, create an MCP auth app following HubSpot’s own instructions. Add the redirect URI Rippit shows in the connect dialog, copied exactly rather than typed.The scopes you grant the app decide what the agent can reach. A scope the app does not have is a tool HubSpot will not offer.
2
Connect in Rippit
Paste the app’s client ID and client secret into Rippit, then authorize. HubSpot asks you to choose the account to connect and to confirm the permissions.
Identity and scope
The connection acts as the HubSpot user who authorized it, with the permissions that user has in that portal. A record the account cannot see is a record the agent cannot see. For an organization-wide connection, authorize with an account whose HubSpot permissions suit everyone who will use the agent, including scheduled runs.Tools
The tools HubSpot offers depend on the scopes on your auth app and on the hubs in your portal, so your connection’s list may be shorter than the one below. Manage tools on the connection card shows exactly what your portal exposes.
The sixteen read tools are enabled by default.