- To connect Cursor to Salesforce, add any Salesforce MCP server through Cursor’s Settings UI or, for team-shared setups, an mcp.json file.
- You’ll need Cursor, a Salesforce MCP server and its connector URL, and Salesforce System Administrator access.
- These steps work with any Salesforce MCP server. Cirra AI is used for the example below and covered in detail at the end.
What You Need
- Cursor, with MCP support enabled (on by default in current versions).
- A Salesforce MCP server and the connector URL it gives you.
- Salesforce System Administrator access, or a user with the specific permissions you want Cursor to operate under.
Connect Cursor to Salesforce Through an MCP Server
Open Cursor Settings (Cmd/Ctrl + ,) and go to Tools & MCP.
Click “+ Add New MCP Server.”
Enter a Name and the Server URL your Salesforce MCP server gives you, choosing HTTP/SSE as the transport for a remote server.
Save. Cursor shows the server with a status indicator once it connects.
Complete the Salesforce authorization flow if prompted.
Start a new chat and describe a Salesforce task to confirm the connection is live.
Prefer a config file?
For a team-shared setup you can version control, add the same details to .cursor/mcp.json instead of using the UI. Both methods produce the same result.
Example mcp.json entry (replace the URL with the one your server provides):
{ "mcpServers": { "salesforce": { "url": "<your-mcp-server-url>" } } }
Verify the Connection
Ask Cursor something specific to your org, such as “What custom objects exist in my Salesforce org?” If it returns your org’s actual custom objects, the connection is working. If it gives a generic answer, the connection did not initialize. Re-check the Server URL in Settings → Tools & MCP (or mcp.json, if you used the config file) and restart Cursor.
What Cursor Can Do Once Connected
This depends entirely on which Salesforce MCP server you connect, not on Cursor itself. An operational-only server lets Cursor read and update records and run SOQL queries. A server with metadata write access lets Cursor also create objects and fields, build Flows, and manage permission sets, directly from chat, alongside your regular coding work.
Troubleshooting
Server doesn’t appear as connected. If you used the UI, confirm the URL and transport type are correct in Settings → Tools & MCP. If you used mcp.json, check the JSON syntax for a missing comma or bracket, then restart Cursor.
Cursor gives generic answers instead of org-specific ones. Confirm the server shows a connected status in Settings → Tools & MCP and start a new chat.
Authorization fails during setup. Confirm you’re authorizing with a Salesforce user that has the permissions the connector needs.
Frequently Asked Questions
Does Cursor have a UI for adding MCP servers?
Is my Salesforce org safe when connected to Cursor through an MCP server?
Using Cirra AI as Your Salesforce MCP Server
Cirra AI is the Salesforce MCP server used in the example above. Unlike Salesforce’s own hosted MCP server, the Cirra AI Salesforce Admin MCP Server writes to the metadata layer directly in conversation: creating objects and fields, building Flows, and managing permission sets and page layouts.
Governance is built into every connection: granular, category-level access controls plus an exportable audit trail mean you stay in control of what Cirra AI can touch. If your team manages more than one Salesforce org, a multi-team hierarchy lets you connect and switch between them from a single setup, rather than reconfiguring per project.
A free plan is available with no credit card required. Connecting your first org takes under 10 minutes.
For the full picture of what’s available across Salesforce MCP servers, see the Salesforce MCP Server guide. If your team uses Claude instead, see connecting Claude to Salesforce.