Skip to main content
Back to the Salesforce Platform MCP server

MCP Gateway · Cursor

Salesforce Platform icon

Connect Salesforce Platform to Cursor

Building a feature that reads from Salesforce is easier when the editor can see real CRM data. In Cursor, the agent reaches Salesforce Platform through the Speakeasy MCP Gateway while you write the code that uses it. Every Cursor hook event carries the user's email, and hooks can deny a call before Cursor runs it.

Category
Sales & CRM
Authentication
OAuth
Cursor
Editor and terminal

Behind the MCP Gateway

Run Salesforce Platform MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Salesforce Platform call inspected and logged.

Deploy on MCP Gateway

Before you start

What Salesforce Platform needs first

A Salesforce System Administrator does the Salesforce Platform side of the setup.

  • You need System Administrator credentials for an API-enabled production or sandbox org.
  • Salesforce documents Hosted MCP Servers for Enterprise Edition and above.
  • Scratch orgs are not covered.
  • Installing Speakeasy's app still needs Speakeasy support to finish OAuth.

In Salesforce Platform

  1. Open Setup and confirm Hosted MCP Servers are available.
  2. Either install Speakeasy's Salesforce app, or create an External Client App.
  3. For your own app, enable OAuth with the Speakeasy callback and the mcp_api and refresh_token scopes.
  4. Copy the Consumer Key.
  5. Enable the chosen MCP server under API Catalog > MCP Servers.
Full Salesforce Platform setup guide in the docs

Set up

Add Salesforce Platform to Cursor in 4 steps

  1. 01

    Add Salesforce Platform from the catalog

    An admin finds Salesforce Platform 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.

    Salesforce Platform 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.

  2. 02

    Choose who can use Salesforce Platform

    Give teams the mcp:connect scope on the Salesforce Platform server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Salesforce Platform to their gateway on the next call, and removing it takes it away.

  3. 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.

  4. 04

    Sign in and use Salesforce Platform from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Salesforce Platform needs its own OAuth grant, so each person connects it once. Until they do, Salesforce Platform calls fail while the rest of the gateway keeps working.

    From then on, Salesforce Platform'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 Salesforce Platform

Shape types from real records

Ask Cursor to read a few Salesforce accounts and opportunities, then generate the TypeScript types or data classes your application uses to handle them.

Wire a button to a platform action

When your app needs to trigger a Salesforce process, Cursor invokes the platform action to learn its inputs and response, then writes the call in the file you have open.

Explain odd data in a bug report

When a screen shows the wrong customer value, Cursor reads the CRM record behind it so you can tell a code bug from a data problem.

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 Salesforce Platform call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Salesforce Platform tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Salesforce Platform 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

Which Salesforce orgs work with Cursor through Speakeasy?
API-enabled production and sandbox orgs where Hosted MCP Servers are available. Salesforce documents them for Enterprise Edition and above, and scratch orgs are not covered.
Do Salesforce hooks run in Cursor Cloud agents?
Cursor Cloud agents need a checked-in .cursor/hooks.json, and session and MCP-specific hooks don't run there.
How do Cursor users get Salesforce Platform?
An admin adds Salesforce Platform from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Salesforce Platform tools their access allows.
Are Salesforce Platform calls from Cursor logged?
Yes. Salesforce Platform calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Salesforce Platform in other clients

AI everywhere.

Control here.