Skip to main content
Book a demo

Connect HubSpot to Cursor

Give Cursor governed access to HubSpot’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add HubSpot to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 1

    Approve HubSpot in Runlayer

    Add HubSpot from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, HubSpot’s 30 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to HubSpot

    Sign in the way HubSpot requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use HubSpot from Cursor

    HubSpot’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

30 HubSpot tools in Cursor

Runlayer policy decides which of these Cursor users can call. 16 read data only and 5 can change or delete data.

  • Discover HubSpot schema

    Searches HubSpot schema to discover available data types or look up known types directly.

  • Get AEO metrics

    Portal-level AEO analytics: brand visibility, mentions, citations, competitor share-of-voice, and per-assistant breakdowns for a date window.

  • Get campaign attribution reports

    REQUIRED FIRST STEP: before your first call, invoke tool_guidance for "get_campaign_attribution_reports" and follow it.

  • Get content analytics report

    Run a content analytics report across landing pages, website pages, and blog posts in the portal.

  • Get conversation channel metadata

    List inboxes, channels, and channel instances in this portal.

  • Get CRM objects

    Fetches multiple CRM objects of the same object type in a single request.

  • Get marketing email analytics

    Provides analytics data for marketing emails based on sends in the given date range.

  • Get organization details

    Get organization-wide teams, job titles (roles), seats, and account info (timezone, currency, account type, portal name).

See all 30 HubSpot tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every HubSpot call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination