SyncOnAI360

Claude connector

Ask Claude about your Salesforce org, and get answers from the org itself.

Connect Claude Desktop, or any Claude client that speaks Model Context Protocol, to your connected orgs in about two minutes. Claude can read; it cannot change anything.

Start freeSalesforce MCP overview

Claude Desktop

Connected to SyncOnAI 360 · read only

Read only

In the production org, what uses Account.Rating?

  • List orgs3 orgs this token can read
  • Where usedAccount.Rating: 4 components
  • Audit findingsLatest assessment: 37 open findings

Four components use Account.Rating: two Flows, one report and a validation rule. This covers every component this token can see.

3 calls recorded in your workspace activity log

In one paragraph

The SyncOnAI 360 Claude connector lets Claude read your connected Salesforce orgs through a Model Context Protocol server. Claude can list the orgs a token allows, search their metadata, look up a component and everything that depends on it, and read health findings. Access is read-only, scoped per token, logged and revocable immediately.

To connect Claude Desktop
2 minTo connect Claude Desktop
Write actions available to Claude
0Write actions available to Claude
Calls a minute allowed per token
120Calls a minute allowed per token
Call logged with its tool and token
EveryCall logged with its tool and token

01The problem

Why Claude on its own gets Salesforce questions wrong

Claude knows Salesforce in general. It does not know your org: which fields exist, which Flows run on Case, what a validation rule checks. Without that, it answers confidently about an org it has never seen.

  1. 01

    Generic answers

    Claude describes how Salesforce usually works, not how your org is built.

  2. 02

    Copy and paste

    People paste metadata into the conversation, which is slow, partial and leaves no record of what was shared.

  3. 03

    Too much access

    Giving an AI client a Salesforce login hands it the power to change the org, which few teams want.

  4. 04

    No accountability

    Nobody can say afterwards which AI tool read what, or when.

02what

What can Claude do with your Salesforce org?

Through the connector, Claude can list the orgs its token may see, search their metadata, look up a component and everything that depends on it, and read the findings of a health assessment. Ask in production org, what uses the Account object, and Claude answers from the synced repository rather than from general knowledge.

Every answer says how much of the org it was based on. If a search hit its limit, or the token can see only some orgs, Claude is told, so a negative answer like nothing uses this field can be trusted or questioned for the right reason.

  • List orgs and search metadata
  • Look up dependencies
  • Read assessment findings
  • Coverage stated with answers

Claude Desktop

Connected to SyncOnAI 360 · read only

Read only

In the production org, what uses Account.Rating?

  • List orgs3 orgs this token can read
  • Where usedAccount.Rating: 4 components
  • Audit findingsLatest assessment: 37 open findings

Four components use Account.Rating: two Flows, one report and a validation rule. This covers every component this token can see.

3 calls recorded in your workspace activity log

03readonly

Why is the Claude connector read-only?

Changes to an org go through a proposal in SyncOnAI 360, where they are checked against the org and approved before they deploy. A token held by an AI client has none of those checks behind it, so it is never given the ability to write.

Claude can create, edit, deploy and delete nothing in a Salesforce org. When an answer leads to a change, make it in SyncOnAI 360, where it becomes a proposal with named checks, validation and approval.

  • No write actions at all
  • Changes go through proposals
  • Approval stays with your admins

Proposal: Case intake fault handling

Acme Production

Checks passed
  • Validated against the org without changing it
  • No component outside the change is modified
  • Apex tests pass, coverage 81%
  • No freeze window in effect
  • Policy: production requires a second admin

Blast radius

  • 2 Flows read Case.Priority
  • 1 report filters on it
  • Case_Intake_Route assigns from it

Risk: medium

04setup

How do you connect Claude Desktop to Salesforce?

In Settings, under Integrations, create an access token, name it after where it lives, and choose which orgs it may read. Copy it straight away; only a one-way digest of it is stored, so it cannot be shown again.

In Claude Desktop, open Settings, then Developer, then Edit Config, and add the SyncOnAI 360 server address with the token as a bearer header. Restart Claude Desktop and the connector appears in the tools menu. Any other Claude client that speaks Model Context Protocol over HTTP connects the same way.

  • Create a scoped token
  • Add one block to the config
  • Restart and ask

Claude Desktop

Connected to SyncOnAI 360 · read only

Read only

In the production org, what uses Account.Rating?

  • List orgs3 orgs this token can read
  • Where usedAccount.Rating: 4 components
  • Audit findingsLatest assessment: 37 open findings

Four components use Account.Rating: two Flows, one report and a validation rule. This covers every component this token can see.

3 calls recorded in your workspace activity log

05control

How do you control and audit Claude's access?

Each token is scoped to the orgs you choose and can be revoked in Settings, where it stops working immediately. Use one token per client, so revoking a lost laptop's token does not disturb anyone else.

Every call Claude makes is written to the activity log with the tool it used and the token it used, and the settings page shows when each token was last used. The arguments are not recorded, so the log is accountability for access rather than a second copy of your org.

  • Tokens scoped per org
  • Instant revocation
  • Every call logged
  • Last used shown per token

Workspace security

Settings · Security

  • Configuration onlyMetadata and code. CRM records stay in Salesforce.
  • Isolated per customerEnforced by the database and tested every release.
  • Keys in Google Cloud KMSCredentials encrypted under a per-customer key.
  • Second admin for productionThe author can never approve their own change.
  • Hosted in the United StatesEvery subprocessor listed with its region.

06inside

How does this differ from the AI inside SyncOnAI 360?

The chat inside SyncOnAI 360 reads the same org and can also draft changes, which become proposals with checks and approval. The Claude connector is for people who prefer to work in Claude and want their org available there, read-only.

Both read the same synced copy of the org, so an answer in Claude and an answer in the workspace agree with each other.

  • Same synced org behind both
  • Drafting changes stays in the workspace
  • Read-only in Claude

SyncOnAI 360

AI architect for Salesforce

Ask SyncOnAI to build flows, rules, Apex, or SOQL...

07How it works

Connecting Claude

About two minutes from token to first answer.

  1. 01

    Create a token

    Name it and choose the orgs it may read.

  2. 02

    Add the server

    Paste the address and token into Claude's config.

  3. 03

    Restart

    The connector appears in Claude's tools menu.

  4. 04

    Ask

    Which orgs can you see? Then something real.

08Before and after

Claude and Salesforce, pasted versus connected

Without

With SyncOnAI 360

Metadata pasted into a conversation

Claude reads the synced org directly

General answers about Salesforce

Answers about your org, with coverage stated

A login that could change the org

Read-only access by design

No record of what was read

Every call logged with tool and token

Access hard to take back

Revoke a token and it stops at once

09Who uses it

Who connects Claude

Salesforce architectsExplore an org's structure and dependencies in a long Claude conversation, with every answer drawn from the org itself.Salesforce adminsAsk what uses a field or what an org contains without leaving the Claude window you already work in.ConsultantsGive Claude read access to a client's org, scoped to that org only, and revoke it when the engagement ends.IT and security leadsLet people use Claude on Salesforce with read-only, scoped and logged access instead of pasted extracts.

10Questions

Frequently asked questions

No. The connector is read-only. Changes go through a proposal in SyncOnAI 360, where they are checked and approved.

Claude Desktop, and any Claude client that speaks Model Context Protocol over HTTP.

The orgs its token allows: their metadata, the components that depend on each other, and health findings. Not CRM records.

No. SyncOnAI 360 keeps org metadata, not CRM records, and that is all the connector can read.

Choose the orgs when creating the token. Leave every box unticked to allow all of them, or tick specific orgs.

Revoke it in Settings and it stops working immediately. Creating a replacement takes seconds.

Yes. Every call is recorded with the tool and the token used. The arguments are not recorded.

120 calls a minute per token, well above what one question needs.

Yes. Every plan includes every feature.

11Keep exploring

Related

Salesforce MCPClaude, Cursor and any MCP client, read onlyCursorYour org beside your code in CursorAnthropicClaude models behind the chat and agentsMetadata RepositoryYour org's configuration and source, searchableDependency GraphEvery relationship, traced to evidencePricingEvery feature on every plan

Start in 5 minutes. No card required.

Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.

Start free, connect my orgBook a demo with SyncOnAI
  • Anthropic
  • OpenAI