Salesforce MCP Servers: Directory and Setup Guide
Salesforce MCP servers connect AI clients to data, actions or developer tools through the Model Context Protocol. The ForceFolks Salesforce MCP Directory compares 8 selected official products and tools. Hosted business access differs from developer access. The local Salesforce DX MCP package reaches end of life on November 2, 2026.
. Product documentation checked October 6, 2026. Publication dates and source checks are separate in the data.
Salesforce MCP at a glance
- Hosted MCP platform
- Generally available since April 2026. Check each server's status.
- Hosted platform eligibility
- Salesforce's GA announcement states Enterprise Edition and above.
- Third-party client access
- External Client App and OAuth. Follow the selected client's current configuration.
- Local DX package
- End of life on November 2, 2026. Salesforce directs users to its skills library.
- Directory scope
- 8 selected official products and tools, not every endpoint or community project.
- Access boundary
- Developer tools, business-data servers and clients have different roles.
Salesforce MCP server directory
This directory separates product purpose, availability and access. An official product is not automatically suitable for every production task. Check its current documentation, permissions and support terms before use.
| Product or tool | Role and audience | Status | Function and access | Official sources |
|---|---|---|---|---|
| Salesforce Hosted MCP Servers | Hosted server family Business users and AI clients | Hosted platform GA since April 2026. Individual server status varies. | Provides approved access to Salesforce data, queries, flows and actions. External Client App and OAuth for third-party clients. Follow client-specific settings. | Salesforce Hosted MCP Servers GA announcement Connecting an MCP Client Create an External Client App Checked October 6, 2026 |
| Salesforce DX MCP Server | Local developer server Developers with existing local DX setups | End of life on November 2, 2026. Package remains installable. | Runs development tasks such as metadata deployment and Apex tests. Explicitly allowed orgs and pre-existing local authentication files. | Local DX MCP end of life: November 2, 2026 Salesforce DX MCP repository Salesforce DX MCP Server and Tools Checked October 6, 2026 |
| Heroku MCP Server | Infrastructure management server Heroku developers and operators | Official sources conflict: GA in the 2025 announcement, early development in the current guide. | Manages Heroku applications, dynos, databases and add-ons. The documented local path uses the current Heroku CLI authentication context. | Heroku MCP Server STDIO Mode Introducing MCP Support Across Salesforce Checked October 6, 2026 |
| MuleSoft DX MCP Server | Developer server MuleSoft developers | Available in current documentation. Check product terms. | Helps design, build, publish and deploy MuleSoft assets. Anypoint connected app with permissions required by the selected tools. | MuleSoft MCP Servers Overview Getting Started with MuleSoft DX MCP Server Checked October 6, 2026 |
| MuleSoft Platform MCP Server | Platform management server Platform and governance teams | Available in current documentation. Check product terms. | Supports service discovery, policy management and traffic monitoring. Platform access and tool-specific permissions. Follow the official setup guide. | MuleSoft MCP Servers Overview Getting Started with MuleSoft Platform MCP Server Checked October 6, 2026 |
| Anypoint Connector for MCP | Runtime connector Integration developers | Available in current documentation. Check compatibility. | Exposes selected Mule application APIs as MCP tools. Can also act as an MCP client. Security and credentials depend on the Mule application and connected resources. | Anypoint MCP Connector Checked October 6, 2026 |
| Slack MCP server | Hosted workspace server Slack users and AI clients | Available to approved supported app types. | Searches Slack content and performs permitted workspace actions. Slack OAuth scopes, app identity and workspace approval. | Slack MCP server overview Checked October 6, 2026 |
| Agentforce Vibes | MCP client Salesforce developers | Available in current documentation. Not a server. | Uses configured MCP servers within a developer workflow. Depends on the server. Platform hosted connections have a documented auto-enabled path. | Agentforce Vibes MCP Servers Connecting an MCP Client Checked October 6, 2026 |
The count includes 1 client and 1 connector. It does not mean Salesforce offers only 8 MCP servers. Hosted products can expose several endpoints with different tools and release stages.
Local DX retirement: Salesforce posted the notice on October 5, 2026. Maintenance and support end on November 2, 2026. The package remains installable, but Salesforce plans no further releases after that date.
The notice directs users to Salesforce's skills library, not to a replacement business-data server. See the official retirement notice.
Heroku status caveat: Salesforce's June 2025 announcement calls the server generally available. Current Heroku documentation calls it early development. This directory preserves both statements. Confirm support expectations with Heroku before a production rollout.
Sources: Salesforce announcement and Heroku Dev Center.
What is the Salesforce MCP server?
MCP is an open protocol for connecting AI applications to tools and data. A client requests a server's tools, then calls a selected tool. The server performs the operation and returns the result. See Salesforce's MCP overview.
The server name alone does not identify its access level. A record-reading tool differs from a deployment tool. A connector that exposes your API differs from an IDE tool that builds that API. Check the operation, target environment and identity for each connection.
Use the ForceFolks directory to identify the product family first. Then inspect the specific tools in the provider's documentation. Confirm whether they read data, change data, deploy code or administer infrastructure. These actions need different review and approval processes.
An AI client can use several servers at once. Each connection adds another data boundary. Review what information can pass between those connections before you provide customer records or production access.
Salesforce Hosted MCP Servers: what changed in April 2026
Salesforce announced general availability of its hosted MCP platform in April 2026. Its announcement states Enterprise Edition and above. Salesforce operates the server infrastructure. Existing user permissions still apply to requests.
Individual server availability and feature entitlements can differ. See the official GA announcement.
Is hosted MCP usage free? Salesforce's current hosted-MCP guide says these servers are intended for customers with Flex Credits and usage may be billed. Confirm the selected server's metering and your contract before rollout. This does not establish a fee for every MCP product or tool.
Standard hosted servers provide selected Salesforce capabilities. Custom servers can expose approved Apex actions, flows and other supported operations. They are not unrestricted access to every API. Choose the smallest set of tools that meets the business need.
For third-party clients, use this setup sequence:
- Select a server and check its availability in Salesforce Setup.
- Activate the server for the intended use.
- Create an External Client App with the documented MCP scopes.
- Match its callback and authentication settings to the client documentation.
- Connect the client and sign in with a limited-access test user.
- Test read operations before you approve write operations.
Salesforce documents OAuth authorization-code access with PKCE for compatible clients. Connected Apps are not supported for hosted MCP authentication. Agentforce Vibes has a documented auto-enabled platform-server path. Do not apply a third-party client's setup steps to every Vibes connection.
Sources: client connection guide and External Client App setup.
Review a hosted endpoint before granting access
The ForceFolks MCP access worksheet records one proposed connection: its purpose, environment, user permissions, approval process and test evidence. Complete a separate copy for each connection. Blank fields mean not reviewed, not approved.
| Server reference | Documented operations | Excluded changes |
|---|---|---|
| SObject Reads | Read records, query, search and inspect schema. | No create, update or delete. |
| SObject Mutations | Read, query and search; create and update records. | No delete. |
| SObject Deletes | Read, query and search; delete records. | No create or update. |
An endpoint's tools do not grant the user new permissions. Salesforce's hosted-MCP best practices also distinguish tool annotations from enforced access controls: a read-only hint or confirmation prompt is not a permission boundary.
- Record the exact server, environment and required operations. Check read access even for a server labelled Mutations or Deletes.
- Document the effective object, field and record access of the test user. Define who reviews proposed writes or deletions.
- Record allowed and denied test cases, log evidence and a revocation check before deciding whether to expand access.
Download the blank MCP access and permission worksheet (CSV). It is an editorial planning aid, not a security certification or an org connection. Keep the completed copy private; do not enter passwords, tokens or customer records.
The original worksheet follows this page's ForceFolks reuse terms. Salesforce documentation retains its own rights. The billing and endpoint checks above are separate from the directory's dated product records.
| Role | Purpose | Status or operation | Access boundary |
|---|---|---|---|
| Hosted Salesforce | Business-data access | GA platform since April 2026 | Select an endpoint and user permissions |
| Local DX package | Developer tooling | End of life: November 2, 2026 | Plan migration to Salesforce skills |
| MuleSoft Connector | Custom API access | Runs within your Mule application | Design tools and secure each operation |
Which Salesforce MCP server should you use?
Start with the action and the system it affects. Do not choose a server only because its name includes Salesforce. ForceFolks groups the following options by their documented role.
| Task | Product or starting point | Important distinction |
|---|---|---|
| Read Salesforce business records or invoke approved actions | Salesforce Hosted MCP Servers | Review the exact endpoint and the signed-in user's access. |
| Maintain an existing local DX MCP setup | Salesforce DX MCP Server | Plan for November 2, 2026 end of life. Review Salesforce's skills migration notice. |
| Manage Heroku applications and resources | Heroku MCP Server | This manages infrastructure. It is not a Salesforce CRM access server. |
| Build or deploy Mule applications | MuleSoft DX MCP Server | Developer workflow, not the runtime connector for your business APIs. |
| Discover and govern services across platforms | MuleSoft Platform MCP Server | Platform management has separate scope from application data access. |
| Expose your own APIs through MCP | Anypoint Connector for MCP | Design the exposed tools and apply security in the Mule application. |
| Search or act in Slack | Slack MCP server | Slack scopes and app approval govern access to workspace data. |
| Use MCP tools within Salesforce development work | Agentforce Vibes | Vibes is a client. Check which servers it connects to. |
For a new developer workflow, read the DX retirement notice before installing the local package. The notice recommends Salesforce skills. Skills and hosted MCP servers solve different problems. A migration needs task-level review, not a server-name substitution.
For MuleSoft, separate development from runtime integration. The DX server helps build and operate MuleSoft assets. The Connector can expose a Mule application's APIs as MCP tools. The Platform server focuses on discovery, policies and monitoring.
See the MuleSoft product overview and MCP Connector documentation.
Salesforce MCP security checklist
Treat this as a planning checklist, not a security certification. A sandbox reduces production impact, but it can still contain sensitive data. Mask test data and restrict access there too.
- Define which records and operations the client needs.
- Use a dedicated test identity with the minimum required permissions.
- Start with read-only tools where the selected server supports them.
- Require review before writes, deployments or changes to user access.
- Restrict the allowed orgs for an existing local DX configuration.
- Keep passwords, tokens and client secrets out of repositories and shared prompts.
- Use the provider's protected credential storage and documented authentication method.
- Check token expiry, app approval and revocation controls.
- Review available logs and record which identity performs each operation.
- Test revocation before expanding access to more users.
The hosted platform uses the authenticated user's permissions. Salesforce's DX documentation describes explicit org allowlisting and local authentication files. Slack documents its own app approvals, OAuth scopes and audit options. These controls are product-specific, not interchangeable.
Sources: hosted access model, DX controls and Slack MCP controls.
Community projects need a separate review. This directory does not audit or endorse them. Check the maintainer, source code, dependencies, credential handling and permissions before testing.
Do not assume a project is safe because it runs locally or supports MCP. Do not assume Salesforce supports third-party code.
Salesforce MCP and Agentforce
MCP and Agentforce are not alternatives. MCP defines how a client communicates with a server. Agentforce provides Salesforce agent capabilities.
Agentforce Vibes is a developer client with MCP connections. A hosted MCP server can make selected Salesforce capabilities available to another client.
Salesforce also documents an API Catalog for managing MCP servers and tools. Client and server roles can exist in the same wider architecture. Avoid the shortcut that MCP only works outside Salesforce while Agentforce only works inside it. See Salesforce's MCP solutions and Vibes MCP documentation.
Plan each connection as a separate integration. Record its owner, data scope, authentication method and permitted actions. For release planning, use the Salesforce release calendar. For deployment work, use the Salesforce implementation checklist.
How ForceFolks builds the Salesforce MCP Directory
The directory uses official Salesforce, MuleSoft, Heroku and Slack documentation. Salesforce's official repositories support the DX retirement and open-source details. Each record has source links and a separate check date. A missing source publication date remains empty.
The dataset compares selected product families, not every server endpoint or extension. It includes the Vibes client and MCP Connector because their roles are easy to confuse with servers. The chart illustrates 3 role boundaries. It is not a count of available products.
When official sources conflict, this page states the conflict. A newer lifecycle notice takes priority over older DX beta labels. The Heroku status note preserves both official descriptions. Availability labels do not promise access under a specific contract or edition.
This is a dated research snapshot, not a live connection to Salesforce. Check the linked documentation before installing, granting access or deploying. This page does not request credentials, connect to an org or execute MCP tools.
Salesforce MCP FAQ
What is the Salesforce MCP server?
The name can refer to several products with different roles. The ForceFolks directory compares 8 selected official products and tools. Hosted business access differs from developer tooling, runtime connectors and clients.
Are Salesforce Hosted MCP Servers generally available?
Salesforce announced general availability of the hosted MCP platform in April 2026. Check each server's documentation because individual features can have different release stages and entitlements.
Which Salesforce edition supports hosted MCP servers?
The GA announcement states Enterprise Edition and above. Check your org, selected server and contract before assuming access. Some capabilities need separate product permissions or entitlements.
How do I connect Claude to Salesforce?
Follow Salesforce's current client connection guide. Activate the intended hosted server, configure an External Client App, then connect with a permitted user. Test read access before approving changes.
Is a community Salesforce MCP server safe?
This directory does not audit community projects. Review code, dependencies, credentials and access before testing. Use masked test data and limited permissions. A sandbox is not a security guarantee.
What happens to the local Salesforce DX MCP Server?
The official notice sets end of life for November 2, 2026. Maintenance and support then stop, although the package remains installable. ForceFolks flags the notice and Salesforce's skills migration direction.
Discuss your Salesforce plans
Describe the build, the systems involved and your target date.