Cursor + Revenue Force
Add the Revenue Force gateway to your Cursor MCP config and work your workspace from your editor.
Works the motion through your AI, on your permissions
Bring your AI into the workflow with scoped, permissioned access. Through the gateway, Cursor can read your workspace, propose actions, and carry out the ones your permissions allow: import an audience, enroll contacts, review and approve drafts, always inside the same guardrails as the console. It works your motion; it does not run your business.
Cursor in, execution under your rules, outcomes back to you.
Reads your workspace
Proposed first, carried out only on your permissions.
What flows in
Into Cursor through the gateway MCP: a read-only view of your campaigns, approvals, and contacts, scoped to your workspace.
- Cursor reads campaigns, approvals, and contacts via the MCP server
- Query performance or approvals without leaving your editor
What flows back
From Cursor back into Revenue Force: permissioned actions, proposed first and governed by the same permissions as the console.
- Run permissioned actions from Cursor: import, enroll, approve
- Governed by the same workspace permissions as the console
Connected in a couple of minutes.
A standard MCP server entry in Cursor, workspace-scoped and permission-governed like every other client.
Add the Revenue Force gateway to your Cursor MCP server config
Authorize your workspace over OAuth
Work your pipeline from Cursor
Your account. Your workspace. Your call.
Cursor connects over OAuth and operates strictly inside your console permissions: it reads what you allow, proposes actions, and carries out only what you have permitted. The connection is scoped to your workspace and revocable in one click.
It acts only on your permissions
Your AI reads what you allow and proposes actions first. It carries out only what your console permissions permit, nothing more, and every action is logged.
Scoped to your workspace only
Your account, your token, your data. A connection lives in one workspace and is never shared across tenants.
Disconnect in one click
Change your mind anytime. Disconnect and the stored credential is cleared immediately. No email, no waiting.
Human approval is the default starting point. Revenue Force proposes, you review, and autonomy increases only when you choose, connection by connection. You set the pace.
Everything a careful buyer should ask.
How do I connect Cursor?
Add the Revenue Force gateway to your Cursor MCP server configuration and authorize your workspace over OAuth.
What can I do from Cursor?
Anything your console permissions allow: import, review approvals, enroll, and check performance, all from your editor.
Is it scoped to my workspace?
Yes. Workspace-scoped, governed by console permissions, disconnect any time.
Ready to run Revenue Force on Cursor?
Book a revenue audit to see how Cursor works your motion through the gateway: what it can read, what it can propose, and which actions stay behind approval.