Salesforce

io.github.wyre-technologyPublished by GitHub account wyre-technologyv1.0.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDatabasesBusiness & Commerce

Overview

AI-generated overview

Salesforce CRM MCP server that lets an assistant search, describe, query and modify Accounts, Contacts, Opportunities, Leads and Cases in a Salesforce org.

What you can do
  • Find standard and custom objects by partial name and read their full schema, including fields, picklists and relationships
  • Run SOQL queries with relationship traversal, plus aggregate queries using GROUP BY, COUNT, SUM, AVG, MIN and MAX
  • Search across objects with SOSL
  • Insert, update, upsert and delete records on standard CRM objects
When to use it
Use it when an assistant needs read or write access to standard Salesforce CRM data — looking up accounts and contacts, reporting on opportunities, or updating leads and cases. It is deliberately narrow; for Apex, custom-object creation or admin tooling the README points to the official Salesforce package instead.
Requirements
Runs as a local process (stdio) or as an HTTP container. Needs a Salesforce Connected App with Client Credentials Flow (SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL), or username-password credentials (SALESFORCE_USERNAME, SALESFORCE_PASSWORD, SALESFORCE_TOKEN). Set AUTH_MODE=env for local stdio use. HTTP mode requires CONDUIT_S2S_SECRET and X-Gateway-S2S signing.
Before you install
Holds Salesforce credentials: the client secret, password and security token are secrets, and the Connected App's Run As user determines what the assistant can reach. The DML tool can insert, update, upsert and delete CRM records, so writes are real. HTTP mode refuses to start without a real CONDUIT_S2S_SECRET; never commit it, and avoid MCP_ALLOW_INSECURE_DEV outside local development.

Installation

In SourceWeft

  1. Open Salesforce in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

ToolPurpose
salesforce_search_objectsFind standard + custom objects by partial name.
salesforce_describe_objectFull schema (fields, picklists, relationships) for an object.
salesforce_query_recordsExecute SOQL with relationship traversal.
salesforce_aggregate_querySOQL GROUP BY / COUNT / SUM / AVG / MIN / MAX.
salesforce_dml_recordsInsert / update / delete / upsert records.
salesforce_search_allCross-object SOSL search.

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. HTTP refuses to start unless CONDUIT_S2S_SECRET is a real secret.
  • stdio: traditional MCP client transport (Claude Desktop / Cursor). Credentials read once from env. The stdio transport does not use CONDUIT_S2S_SECRET.

Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.

VariableRequiredDescription
SALESFORCE_CLIENT_ID / SALESFORCE_CLIENT_SECRET / SALESFORCE_INSTANCE_URLFor stdio and AUTH_MODE=envClient Credentials flow.
SALESFORCE_USERNAME / SALESFORCE_PASSWORD / SALESFORCE_TOKENFor username-passwordUsed when SALESFORCE_AUTH_FLOW=username_password. The token is optional if the org uses IP allowlisting.
MCP_TRANSPORTNohttp (default) or stdio.
AUTH_MODENogateway (image and Compose default) or env. Gateway mode requires the X-Salesforce-* headers on each /mcp request and never falls back to SALESFORCE_*. env uses those variables only after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. HTTP logs an error and exits non-zero when this is empty or a known placeholder (changeme, placeholder, your-s2s-secret, secret, password, test, an unresolved ${...} template, and the other stand-ins in src/s2s-verify.ts). Never commit a real value.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not check X-Gateway-S2S, and listens on 127.0.0.1 only. A non-loopback MCP_HTTP_HOST is ignored and the override is logged. A known placeholder secret still refuses to start.
MCP_HTTP_HOSTNoBind address when a usable CONDUIT_S2S_SECRET is set. When unset, a configured secret keeps HOST (default 0.0.0.0). Without a usable secret the listener is 127.0.0.1. The container image sets 0.0.0.0.
PORTNoHTTP port. Defaults to 8080.
HOSTNoFallback bind address when MCP_HTTP_HOST is unset and a secret is configured. Defaults to 0.0.0.0.

/health stays unauthenticated and does not read credentials.

bash
# HTTP mode (exits unless CONDUIT_S2S_SECRET is a real secret)CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start
# Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)MCP_ALLOW_INSECURE_DEV=1 MCP_TRANSPORT=http npm start
# stdio mode (env-baked, local testing; no S2S secret)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)

Every /mcp request must include a valid X-Gateway-S2S header when CONDUIT_S2S_SECRET is set. Gateway mode also requires the credential headers for the chosen flow. A request missing them returns 401 and does not fall back to SALESFORCE_* in the process environment.

HeaderRequired?Notes
X-Gateway-S2SYes when the S2S secret is sett=<unix seconds>,v1=<hex hmac-sha256>. See X-Gateway-S2S signing.
X-Salesforce-Auth-Modeoptionalclient_credentials (default) or username_password.
X-Salesforce-Client-Idfor client_credentialsConnected App consumer key.
X-Salesforce-Client-Secretfor client_credentialsConnected App consumer secret.
X-Salesforce-Instance-Urlfor client_credentialsCustomer's My Domain URL (e.g. https://acmecorp.my.salesforce.com).
X-Salesforce-Usernamefor username_passwordSalesforce user.
X-Salesforce-Passwordfor username_passwordSalesforce password.
X-Salesforce-Tokenfor username_passwordSecurity token (required unless IP allowlisted).

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.

X-Gateway-S2S signing

v1 is HMAC-SHA256, hex-encoded, of the ASCII string t=<unix seconds> (the same t= prefix that starts the header), keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns HTTP 401. The secret is never written to logs or the response body.

bash
t=$(date +%s)v1=$(printf 't=%s' "$t" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" | awk '{print $NF}')curl -sS http://127.0.0.1:8080/mcp \  -H "content-type: application/json" \  -H "accept: application/json, text/event-stream" \  -H "X-Gateway-S2S: t=${t},v1=${v1}" \  -H "X-Salesforce-Client-Id: ..." \  -H "X-Salesforce-Client-Secret: ..." \  -H "X-Salesforce-Instance-Url: https://yourorg.my.salesforce.com" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

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

bash
npm installnpm run build

Container

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Salesforce credentials arrive on each request as headers; they are not read from the environment.

bash
docker build -t salesforce-mcp:dev .docker run --rm \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  salesforce-mcp:devcurl -s http://127.0.0.1:8080/health

Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject SALESFORCE_*:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses SALESFORCE_*:

bash
docker run --rm \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e SALESFORCE_AUTH_FLOW=client_credentials \  -e SALESFORCE_CLIENT_ID=your-value \  -e SALESFORCE_CLIENT_SECRET=your-value \  -e SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \  -p 127.0.0.1:8080:8080 \  salesforce-mcp:dev

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

License

Apache-2.0.

Source: README.md at commit a2a8ebb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.