HubSpot MCP can expose permitted CRM records and activities to an authorized AI client. Finta adds a relationship-intelligence layer by comparing HubSpot's recorded pipeline state with the relationship evidence surrounding an investor, partner, or deal.
That comparison can reveal a stale deal, a missing follow-up, an unsupported next step, or a conflicting owner. This page is publishable as an evidence-bounded setup and workflow guide, but it must not claim that HubSpot sign-in through Aurora has been proven. HubSpot requires a registered MCP Auth App, exact redirect URL, client credentials, and OAuth 2.1 with PKCE, while Finta's current catalog records the connector as oauth_dynamic.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Catalog MCP |
| Official server | https://mcp.hubspot.com |
| Official transport | Streamable HTTP |
| HubSpot authentication requirement | Registered MCP Auth App with client ID, client secret, exact redirect URL, and PKCE |
| Current Finta catalog auth mode | oauth_dynamic |
| Repository endpoint configuration | Aligned with the official base endpoint on August 22, 2026 |
| Authenticated HubSpot connection | Pending auth-model reconciliation |
| Live tools/list receipt | Pending |
| Known HubSpot record read | Pending |
| Controlled CRM write and rollback | Pending |
The endpoint is aligned, but the authentication model is not yet proven. HubSpot's official setup requires an MCP Auth App. Finta's current generic OAuth flow uses dynamic registration unless connector configuration supplies a pre-registered client ID and secret.
Do not describe the public Connect button as a working HubSpot sign-in until a production Auth App, callback, token exchange, tools/list response, and safe read have been captured.
The expected production callback derived from Finta source is https://finta.ai/api/connectors/hubspot/callback, but the deployment callback base must be checked before it is registered in HubSpot.
What is documented and what Finta verified
The entries below come from HubSpot's current first-party remote MCP documentation. Exact machine names, account-specific availability, and enabled write tools must be taken from a live Finta tools/list receipt after authentication succeeds.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| get_user_details | Return connected user and portal context | Provider-documented; live Finta discovery pending |
| get_crm_objects | Retrieve supported CRM records | Provider-documented; live Finta discovery pending |
| search_crm_objects | Search supported CRM records | Provider-documented; live Finta discovery pending |
| manage_crm_objects | Create or update supported CRM records | Provider-documented write capability; keep disabled until controlled verification |
| get_properties | Retrieve supported object properties | Provider-documented; live Finta discovery pending |
| search_properties | Search object-property definitions | Provider-documented; live Finta discovery pending |
| search_owners | Search CRM owners | Provider-documented; live Finta discovery pending |
| get_campaign_contacts_by_type | Retrieve campaign contacts by type | Provider-documented; live Finta discovery pending |
| get_campaign_analytics | Retrieve campaign analytics | Provider-documented; live Finta discovery pending |
| get_campaign_asset_types | List campaign asset types | Provider-documented; live Finta discovery pending |
| get_campaign_asset_metrics | Retrieve campaign asset metrics | Provider-documented; live Finta discovery pending |
| search_conversations | Search conversations allowed by user rights and settings | Provider-documented; Sensitive Data settings can restrict results |
| get_conversation_channel_metadata | Retrieve conversation-channel metadata | Provider-documented; live Finta discovery pending |
| Get marketing email analytics | Official rendered label for email analytics | Exact machine name requires live tools/list |
| Manage marketing email | Official rendered label for draft-management operations | Exact machine name and write behavior require live tools/list and controlled testing |
| submit_feedback | Submit feedback about the MCP server | Provider-documented; live Finta discovery pending |
Setup and proof path
- Before exposing a user-facing HubSpot sign-in claim, create an MCP Auth App in HubSpot's developer platform.
- Set the app redirect URL to the exact callback generated by the production Finta deployment. Source currently derives it from MCP_OAUTH_CALLBACK_BASE_URL or NEXT_PUBLIC_SITE_URL plus /api/connectors/hubspot/callback.
- Store the HubSpot client ID and client secret in Finta's secret-managed deployment configuration. Never place the secret in CMS content or browser state.
- Update the connector configuration so Finta uses the pre-registered client credentials instead of assuming HubSpot supports dynamic client registration.
- Confirm the requested HubSpot scopes are the narrowest ones required for the intended read workflow.
- In Finta, open Aurora, select the plus control, choose Connect App, and select HubSpot.
- Complete HubSpot's PKCE authorization and choose the intended HubSpot account.
- Run get_user_details first and verify the returned portal and user before searching business records.
- Capture the complete tools/list response and compare it with the provider documentation on this page.
- Disable write-capable tools before the initial safe-read proof.
- Read one known non-sensitive contact and associated deal, then reconcile record IDs, owner, stage, and recent permitted activity directly in HubSpot.
- If a controlled write is later authorized, use a reversible test record, capture the before and after state, and verify the rollback in HubSpot itself.
Flagship workflow
Stalled investor deal to evidence-backed intervention
The differentiated job is not generic CRM search. Aurora compares the activity recorded in HubSpot with Finta's relationship evidence so the user can decide whether a deal is actually stalled and what should happen next.
- Confirm the connected HubSpot portal and user before loading records.
- Search investor-related deals in a user-selected stage and time window.
- Retrieve the associated contact, company, deal owner, recorded next step, and permitted recent activities.
- Retain the HubSpot record IDs and source links behind each statement.
- Match the people and firm with Finta CRM and relationship context without claiming continuous synchronization between the systems.
- Separate recorded HubSpot facts from Finta evidence and Aurora inference.
- Flag stale activity, a missing next step, conflicting owners, timing evidence, and unsupported assumptions.
- Recommend one relationship-aware action and explain the evidence and timing behind it.
- Prepare a proposed task or CRM change only when the required write tool appears in the live tool list.
- Stop before mutation until the user approves the target record, owner, due date, note, and complete change set.
Sample prompts
In HubSpot, find investor deals in the selected stage with no permitted activity in the last fourteen days. Return the source records, owner, last activity, and recorded next step. Compare them with Finta relationship context. Do not update anything.Load the selected contact and associated company, deal, and permitted activity from HubSpot. Compare them with Finta relationship context, flag conflicting fields, and prepare a briefing with sources.Prepare one follow-up task for the selected deal. Show the proposed owner, due date, note, target record, and evidence. Do not create it until I approve the exact change.
Expected output
The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.
| Output field | Expected evidence |
|---|---|
| Connected account | HubSpot portal, authorized user, and access context |
| Source records | Contact, company, deal, owner, record IDs, and HubSpot links |
| Recorded pipeline state | Stage, next step, last permitted activity, and timestamp |
| Finta relationship evidence | Relationship owner, prior interaction, path, timing, and relevant commitments |
| Evidence boundary | HubSpot facts, Finta facts, and Aurora inference shown separately |
| Conflict or gap | Stale activity, owner mismatch, missing next step, or unsupported assumption |
| Recommended next move | One relationship-aware action with timing rationale |
| Proposed HubSpot write | Operation, target, fields, before value, proposed value, and rollback plan |
| Approval state | Disabled or pending explicit approval until write verification is complete |
| Completed writes | None in an illustrative output or read-only run |
| Limitations | Scope, permission, Sensitive Data, association, or missing-source caveat |
Permissions and limitations
- HubSpot access follows the installing user's permissions and the scopes granted to the MCP Auth App.
- HubSpot's Sensitive Data setting can prevent activities and conversation data from being returned through MCP.
- HubSpot uses CRM search rather than semantic vector search, so query coverage depends on supported object search and record properties.
- The documented surface spans contacts, companies, deals, tickets, activities, content, campaigns, and other supported objects, but availability varies by account, rights, scopes, and current server version.
- A provider-documented tool is not proof that the tool appeared in Finta's connected tools/list response.
- Tool updates can require reauthorization or reinstalling the app.
- Do not claim continuous full-database synchronization between HubSpot and Finta.
- Do not claim that every HubSpot object, association, property, conversation, or marketing record is available to every account.
- External CRM write tools should remain disabled until a reversible write and rollback have been source-checked in a controlled portal.
- A prepared mutation is not an executed mutation. The output must show the target and complete proposed change before approval.
- HubSpot authentication remains unverified in Finta until the registered Auth App flow succeeds end to end.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | HubSpot remote MCP and Auth App documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta endpoint, callback construction, OAuth service, and catalog auth mode inspected | Complete, August 22, 2026; auth mismatch identified |
| Level 2 | Registered HubSpot MCP Auth App configured with the production callback | Pending |
| Level 3 | Authenticated HubSpot OAuth and PKCE receipt | Pending |
| Level 4 | Connected portal confirmed with get_user_details | Pending |
| Level 5 | Exact tools/list names and descriptions captured | Pending |
| Level 6 | One known contact and associated deal returned and reconciled | Pending |
| Level 7 | Write-capable tools disabled for the initial connection | Pending |
| Level 8 | One reversible test write completed and rolled back in a controlled portal | Pending |
| Level 9 | Public page, metadata, image, and responsive rendering | Complete, August 22, 2026 |
Sources and related Finta guidance
Primary provider sources
Related Finta guidance
- Investor follow-up workflow
- Meeting preparation workflow
- Finta CRM
- Aurora
- Finta MCP security
- Official Finta apps
- All Finta integrations
Use Aurora to find the relationship evidence behind the deal