MCP Gateway · Cursor
Connect HubSpot to Cursor
Forms, dashboards and internal tools that read HubSpot data need the right property names and account settings. With HubSpot connected to Cursor through the Speakeasy MCP Gateway, the agent can find them while you edit. Cursor hooks send each tool call to Speakeasy, which allows or denies it, and fail closed if the check can't run.
- Category
- Sales & CRM
- Tools
- 13
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run HubSpot MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every HubSpot call inspected and logged.
Before you start
What HubSpot needs first
A HubSpot user with access to the Development workspace; an account admin for the first connection does the HubSpot side of the setup.
- The remote MCP server is available to all HubSpot accounts.
- You need a user who can open the Development workspace.
- The first connection should be made by an account admin.
In HubSpot
- Open Development > MCP Connectors.
- Create an MCP connector with the Speakeasy redirect URL.
- Copy the Client ID and Client secret.
Set up
Add HubSpot to Cursor in 4 steps
- 01
Add HubSpot from the catalog
An admin finds HubSpot in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
HubSpot uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use HubSpot
Give teams the
mcp:connectscope on the HubSpot server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds HubSpot to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use HubSpot from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
HubSpot needs its own OAuth grant, so each person connects it once. Until they do, HubSpot calls fail while the rest of the gateway keeps working.
From then on, HubSpot's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with HubSpot
Find the property behind a form field
Building a signup form? Ask Cursor to search property definitions by keyword, so the field you post to HubSpot uses the real property name and type.
Format values for the account
Cursor reads the organization's timezone and currency settings, so dates and amounts in your internal tool display the way the HubSpot account expects.
Learn how tools fit together
When it's unclear which HubSpot tool returns what, Cursor asks for usage guidance on a set of tools before writing the code that depends on them.
Tools
13 tools
Each HubSpot tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
search_crm_objects
Searches and retrieves CRM records from HubSpot based on filters and criteria.
submit_feedback
Collects and submits feedback to HubSpot on dissatisfaction or user request.
get_campaign_contacts_by_type
Get paginated contact IDs for a campaign filtered by attribution type.
search_owners
Lists and searches for owners who can be assigned to CRM records.
get_campaign_analytics
Get campaign analytics (METRICS or REVENUE_ATTRIBUTION) for one or more campaigns. Each entry in the request list is a full analytics request. Each response contains the campaignObjectId of the requested campaign.
get_campaign_asset_types
List the asset type names available as campaign assets (e.g. LANDING_PAGE, BLOG_POST). Use the returned names as the assetType parameter in getCampaignAssetMetrics.
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every HubSpot call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the HubSpot tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to HubSpot can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
How does a Cursor team get the HubSpot plugin without GitHub access?
Who should make the first HubSpot connection?
How do Cursor users get HubSpot?
Are HubSpot calls from Cursor logged?
Connect more