Salesforce MCP Ts MCP Server

If you want an AI assistant working directly with Salesforce MCP Ts, the salesforce mcp ts mcp server is the bridge. A Model Context Protocol (MCP) server implementation for Salesforce integration in TypeScript.

What Salesforce MCP Ts does

A TypeScript implementation of a Model Context Protocol (MCP) server for Salesforce integration, allowing LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and CRUD operations.

Key capabilities

• 🔐 Simplified Password Authentication — Secure OAuth 2.0 Resource Owner Password Credentials Flow
• 📊 SOQL & SOSL — Execute queries and searches against Salesforce
• 🔍 Metadata Access — Retrieve object fields, labels, and types
• ✏️ CRUD Operations — Create, read, update, and delete records
• 🛠️ Tooling API — Execute Tooling API requests
• ⚡ Apex REST — Execute Apex REST requests
• 🌐 REST API — Make direct REST API calls to Salesforce
• 🐳 Docker Ready — No hardcoded values, fully configurable via environment variables

Tools it exposes

Once connected, the assistant can call these 13 tools directly:

• authenticate_password — Authenticate using username/password with OAuth
• run_soql_query — Execute SOQL queries
• run_sosl_search — Execute SOSL searches
• get_object_fields — Get metadata for Salesforce objects
• get_record — Retrieve specific records by ID
• create_record — Create new records
• update_record — Update existing records
• delete_record — Delete records
• tooling_execute — Execute Tooling API requests
• apex_execute — Execute Apex REST requests
• restful — Make direct REST API calls
• Prerequisites — 1. Create a Connected App in Salesforce: - Go to Setup → Apps → App Manager → New Connected App - Fill in basic information (App Name, API Name, Contact
• Optional — The Optional tool exposed by this server

Installing the salesforce mcp ts mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 8 environment variables: SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_SECURITY_TOKEN, SALESFORCE_ACCESS_TOKEN, SALESFORCE_INSTANCE_URL, SF_CONSUMER_KEY, SF_CONSUMER_SECRET, SF_SECURITY_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

1. Create a Connected App in Salesforce: - Go to Setup → Apps → App Manager → New Connected App - Fill in basic information (App Name, API Name, Contact Email) - Enable OAuth Settings - Set callback URL: http://localhost:8080/callback (required but not used) - Select OAuth Scopes: - Access your basic information (id, profile, email, address, phone) - Perform requests on your behalf at any

Where it fits

Communication servers earn their keep on volume — summarising channels and threads that would otherwise cost you an hour of scrollback. Salesforce MCP Ts sits in that group, and the shape of its toolset — authenticate_password, run_soql_query, run_sosl_search among others — tells you what it is really for. Worth comparing against the other communication servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 13 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Salesforce MCP Ts.
• Maintained by steffensbola, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the salesforce mcp ts mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.