MCP.Market

Salesforce MCP server

by wyre-technology·io.github.wyre-technology/salesforce-mcp·v1.0.3
No reviews yet

MCP server for Salesforce CRM — Accounts, Contacts, Opportunities, Leads, Cases.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Salesforce yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Salesforce tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Salesforce compares

Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 876 Sales and outbound servers

Install Salesforce in Claude Code, Cursor or VS Code

claude mcp add salesforce-mcp -- docker run -i --rm ghcr.io/wyre-technology/salesforce-mcp:v1.0.3
Add to Cursor

What the publisher says

From the Salesforce repository's README, as published. We do not edit it. Read it on GitHub

salesforce-mcp

MCP (Model Context Protocol) server for Salesforce CRM, scoped to the WYRE Gateway BYOC use case.

A focused HTTP MCP server that exposes a Salesforce org's CRM data surface to Claude (and other MCP clients) through the WYRE MCP Gateway. Built for the multi-tenant gateway pattern: credentials are injected per-request via HTTP headers, no startup secrets are baked into the container.

Scope discipline

This package intentionally ships a narrow tool surface — six CRM data tools — and deliberately omits the Apex code-management / custom-object-creation / EXECUTE_ANONYMOUS surfaces that broader Salesforce MCP servers include. The use case is read/write access to standard CRM objects (Accounts, Contacts, Opportunities, Leads, Cases). Customers who need DX or admin tooling should use the official @salesforce/mcp package instead.

Tools

Run modes

  • http (default): listens on :8080, exposes /mcp (JSON-RPC) + /health. Per-request credentials from X-Salesforce-* headers. This is the gateway deployment shape.
  • stdio: traditional MCP client transport (Claude Desktop / Cursor). Credentials read once from env. Useful for local testing.
# HTTP mode (gateway default)
PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start

# stdio mode (env-baked, local testing)
MCP_TRANSPORT=stdio \
SALESFORCE_AUTH_FLOW=client_credentials \
SALESFORCE_CLIENT_ID=... SALESFORCE_CLIENT_SECRET=... \
SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \
node dist/entry.js

Header contract (gateway mode)

Per-request authentication means the same container instance can service many customers without restart — each MCP tools/call builds a fresh jsforce.Connection from the headers on that request.

Salesforce Connected App setup

For Client Credentials flow (the recommended path):

  1. Salesforce Setup → App Manager → New Connected App.
  2. Under API (Enable OAuth Settings): turn on Enable OAuth Settings and Enable Client Credentials Flow.
  3. Save, wait ~5 minutes for propagation.
  4. Manage → Edit Policies → Client Credentials Flow → set a Run As user (the API calls run with that user's permissions).
  5. Copy the Consumer Key and Consumer Secret from the Connected App into the gateway BYOC fields as clientId and clientSecret.
  6. Set instanceUrl to the customer's My Domain URL (Setup → My Domain).

Build

npm install
npm run build

Container

docker build -t salesforce-mcp:dev .
docker run --rm -p 8080:8080 -e MCP_TRANSPORT=http salesforce-mcp:dev
curl -s http://localhost:8080/health

The published image lives at ghcr.io/wyre-ai/salesforce-mcp with :latest, :sha-, and :v tags.

License

Apache-2.0.

Nothing above is checked by us. What we check is on the safety report.

Salesforce: common questions

Is Salesforce MCP server safe?
Mostly: it is graded B (75/100). Read the Salesforce safety report
How do I install Salesforce?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Salesforce need an API key?
Yes. The registry entry asks for SALESFORCE_CLIENT_SECRET, SALESFORCE_PASSWORD, SALESFORCE_TOKEN.
Is Salesforce maintained?
The last commit was 9 days ago (2026-10-26). The latest release is v1.0.3.
What can I use instead of Salesforce?
Servers from other publishers that do the same job: Cargo MCP server, Customermates MCP server and Vibe Prospecting MCP server.

Alternatives to Salesforce

Same job from other publishers: the closest match first, then the best rated.

  • Cargo
    Find and verify work emails, enrich companies and contacts, score leads and sync to your CRM.
    C
  • Customermates
    Native MCP access to CRM contacts, organizations, deals and tasks with user permissions.
    A
  • Vibe Prospecting
    B2B company and contact data for lead lists, enrichment, research, and outreach. OAuth sign-in.
    A
  • OpenLeads
    Find leads with honest email evidence, then work them: CRM, sequences, tasks, deals. No API keys.
    A
  • Leadbay
    AI lead discovery, qualification, and outreach prep on your Leadbay account.
    A

More from wyre-technology →