@salesforce/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Salesforce CRM workflows

What we know

MCP Server for interacting with Salesforce instances Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

npm exact package downloads 161174 in 2026-09-09..2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions. Reported action classes: create/update CRM records if enabled. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: Salesforce account, leads and CRM records

Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 161.2k package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @salesforce/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T03:38:00Z.

All limitations / Review context

Has @salesforce/mcp changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
Salesforce account, leads and CRM records
Reviewed write actions: create/update CRM records if enabled
Sensitive access: Salesforce account, leads and CRM records
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Original activity observations

npm exact package downloads 161174 in 2026-09-09..2026-10-08

Technical identity

npm/@salesforce/mcp

Exact implementation source: https://www.npmjs.com/package/@salesforce/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@salesforce/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@salesforce/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Salesforce DX MCP; configure Salesforce org access and toolsets per publisher; generic launch alone is not enough.
publisher install or stdio launch · Publisher instructions
npx -y @salesforce/mcp
Configure / authenticate
MCP100 setup guide
Salesforce MCP uses Salesforce DX authenticated org context. Keep destructive org, metadata deploy, or migration tools outside verification.
Check connection
Suggested check
Call published list_all_orgs with connection_status flag (read-only); do not use Salesforce metadata or org write tools.
Remove / uninstall / revoke
MCP100 setup guide
Salesforce DX MCP requires an authenticated Salesforce org. Remove a local Claude Code registration with `claude mcp remove salesforce` only if it was registered with that exact name. This does not remove authenticated orgs or CLI installation.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Salesforce OAuth connected app: users can use personal Settings → Advanced User Details → OAuth Connected Apps → Revoke. Admins use Setup OAuth Connected Apps Usage to revoke app or user sessions. Salesforce documents separate procedures for external client apps. `sf org logout` is not itself proof of remote token revocation.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove salesforce

Official Documentation & Sources

What it does

MCP Server for interacting with Salesforce instances Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Salesforce CRM workflows

Representative uses

Salesforce CRM workflows

Limitations

Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.
Data handling: Salesforce account, leads and CRM records
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.

Access scope and cautions

Write actions: Not verified create/update CRM records if enabled
Sensitive access: Salesforce account, leads and CRM records
Risk level: high
Security notes: Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Salesforce CRM workflows.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: create/update CRM records if enabled. Recorded permission context: Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions.

What data-handling boundary should I consider?

Salesforce account, leads and CRM records Recorded sensitive-access context: Salesforce account, leads and CRM records.

What limitations and risks should I check before use?

Salesforce CRM OAuth access may expose personal records and permit writes, depending on app permissions. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Dated package download count is usage signal, not necessarily a current maintenance release. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.