Connect Sumble to Cursor
Give Cursor governed access to Sumble’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sumble to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Add Sumble to Runlayer
Sumble isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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, Sumble’s 38 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to Sumble
Sign in the way Sumble requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Sumble from Cursor
Sumble’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
38 Sumble tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Add contacts to list
Add people to an existing contact list.
Add organizations to list
Add organizations to an existing list.
Create contact list
Create a new contact list (people list).
Create organization list
Create a new organization list.
Find match and enrich jobs
The primary jobs tool: look up jobs by id or search the jobs corpus, and return exactly the attributes you ask for, with optional related people.
Find match and enrich organizations
Find, match, and enrich organizations in one call.
Find match and enrich people
The primary people tool: resolve people and return exactly the attributes you ask for, with optional related people and contact reveals.
Find match and enrich teams
Find the teams inside an organization and return selected attributes, related people, and job postings.
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 Sumble 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