serversSoftwareApplication

Salesforce MCP Server

Deploy and configure the Salesforce MCP server with authentication, use cases, security notes, and India-ready hosting guidance.

Quick Answer / TL;DR

The Salesforce MCP server exposes Salesforce capabilities to AI clients through scoped tools, resources, and JSON-RPC calls, using Salesforce OAuth Credentials for authentication.

Key Takeaways

Authentication: Salesforce OAuth Credentials.
Category: Productivity.
Best first use case: Extract corporate lead metrics.
Use environment variables and least-privilege scopes for production.

Integration overview

Connect enterprise-level customer relationships databases, running SOQL queries and updating records inside workflows.

Use this connector when an AI assistant such as Claude, Cursor, or a custom agent needs a governed path into Salesforce. Keep the server focused on the approved workflows instead of exposing a whole account or admin surface.

For Indian teams, deploy the connector near the users and the data source, then add request IDs, redaction, and audit logs before connecting production data.

Field	Value
Connector	Salesforce MCP Server
Category	Productivity
Authentication	Salesforce OAuth Credentials
Production route	/servers/salesforce-mcp-server/

Features and use cases

Salesforce is most useful when the agent has a narrow job to complete and the server can validate every argument before execution.

Start with read-only or low-risk tools. Add write operations only after approval prompts, scoped credentials, and logging are working.

Capability	Recommended guardrail
SOQL execution	Allow with scoped read access
Lead tracking	Allow with scoped read access
Case management	Require approval and audit logging
Account updates	Allow with scoped read access

Local and hosted configuration

Configure Salesforce with credentials stored in environment variables. Do not hardcode tokens in prompts, repositories, screenshots, or browser-visible code.

The local configuration pattern works for a single developer. Hosted deployments should add TLS, bearer-token authentication, health checks, and monitoring.

{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-salesforce"],
      "env": {
        "SALESFORCE_TOKEN": "${SALESFORCE_TOKEN}"
      }
    }
  }
}

Security and permissions

Protect Salesforce OAuth Credentials credentials with least privilege, rotation, and separate environments for development, staging, and production.

Review every tool output for sensitive data before letting it enter model context. For regulated Indian workflows, add DPDP-aware redaction and retention controls.

{
  "server": "salesforce-mcp-server",
  "auth": "Salesforce OAuth Credentials",
  "policy": {
    "leastPrivilege": true,
    "redactSecrets": true,
    "requireApprovalForWrites": true,
    "auditToolCalls": true
  }
}