Skip to main content
Book a demo

Connect Harmonic to Cursor

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

Book a demo Cursor setup guide

Set up

Add Harmonic to Cursor in four steps

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

  1. 1

    Add Harmonic to Runlayer

    Harmonic isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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, Harmonic’s 47 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Harmonic

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

  4. 4

    Use Harmonic from Cursor

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

Tools

47 Harmonic tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Add companies to list

    Add companies to an existing company list.

  • Add people to list

    Add people to an existing people list.

  • Create company list

    Create a new company list.

  • Create company list custom field

    Create a custom field (column) for a company list.

  • Create global custom field

    Create a new global custom field for companies or people.

  • Create list

    Create an empty company, person, or investor list in the workspace's shared project.

  • Create list custom field

    Create a custom field on any company, person, or investor list.

  • Create list entries

    Add Harmonic companies, people, or investors to an existing list by creating list entries from their URNs.

See all 47 Harmonic 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 Harmonic 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