How to Connect Claude to Salesforce with an MCP Server

No. The Salesforce connection is stored in Noca, and Claude connects to the Noca MCP Server using OAuth sign-in.

Yes, if you enable the Data write permission group. Claude then runs published Noca flows that perform the updates, and you can require approval for each run.

The Noca MCP Server works as a Salesforce MCP server for business processes, and also connects Claude to NetSuite, SAP, Priority and 60+ other systems.

You can connect Claude to Salesforce by adding an MCP server that has access to Salesforce as a custom connector in Claude.

Key points include: Ask Claude for the status of an account and get an answer from live Salesforce data; Generate a quote or contract from an opportunity and send it for e-signature; Turn a won opportunity into an ERP customer and order in NetSuite, SAP or Priority; Summarize open cases for a key customer before a meeting.

1) Connect your Salesforce account in Noca once, so flows and tools can use it 2) In Noca, open Security & Credentials, then MCP Server, turn it on and choose the permission groups 3) Copy the private MCP Server URL 4) In Claude, go to Settings, Connectors, then Add custom connector. Name it, for example “Noca – Prod”, and paste the URL 5) Sign in to Noca when prompted.

Consider the following: Data read for questions about accounts, opportunities and cases; Data write only if Claude should run flows that update Salesforce; Needs approval for any tool that publishes, deletes or changes many records.

Yes. With the Noca MCP Server, ChatGPT, Claude, Grok and other MCP-compatible assistants can run your published Noca flows and use Noca tools for Claude Salesforce MCP, within the permission groups and per-tool approvals you set.

Yes. Noca connects natively to Salesforce, NetSuite, SAP, SAP Business One, Priority ERP, HubSpot, monday.com and 60+ other systems, so Claude Salesforce MCP can use live data from them and update them automatically.

No. In Noca you describe what you need in plain language and Noca builds the forms, apps, flows and documents. Developers can extend any process with REST APIs, OpenAPI definitions and webhooks.

Use least-privilege permissions, require approval for sensitive actions and keep a log of every run. Noca follows the TRAPS framework (Trusted, Responsible, Auditable, Private and Secure), records every flow run in integration logs and lets you control data storage for specific flows.

A first working version can often be built from a prompt and tested quickly. The total time depends on how many systems, approvals and documents are involved and how much testing your team requires before publishing.

Compare cycle time, manual steps, error rates and adoption before and after. Noca integration logs show how often each process runs, how long it takes and where it fails.

Yes. The Noca MCP Server connects ChatGPT, Claude, Grok and other MCP-compatible assistants to your Noca workspace with 80 tools for apps, bots, flows, documents, connections and data.

Tools are grouped into Builder, Data read, Data write and Admin. In your assistant, each tool can be set to always allow, needs approval or blocked, and destructive actions ask for confirmation.

Yes. The read-only query_records tool reads records from Salesforce, Priority, SAP Business One, Microsoft Dynamics 365 and Microsoft SQL Server without building a flow.

Yes, by running published Noca flows with the run_flow tool, which requires the Data write group. The flow keeps your validation and mapping, and you can require approval for each run.

Yes. Noca bots and flows can use external MCP servers such as Notion, GitHub, Stripe, Airtable and Google Workspace services, with an explicit allowlist of tools.

Noca offers 60+ integrations, including Salesforce, NetSuite, SAP, Priority, HubSpot, Microsoft Dynamics 365, monday.com, Zendesk, Slack, Google Workspace, Microsoft 365, DocuSign and Shopify.