Salesforce

This Salesforce MCP server allows natural language interfaces to interact with your Salesforce data and metadata. It exposes tools for discovering objects, inspecting object schemas, querying data (including related records), retrieving picklist values, filtering fields by type, exploring relationships, and managing debug logs and validation rules. You can use these capabilities through a code editor integration or any MCP client that speaks the MCP protocol, enabling Claude, GitHub Copilot, or similar assistants to perform Salesforce operations using everyday language. Typical workflows include searching for objects by partial names, describing an object's fields and relationships, querying records with filters and relationships, and retrieving advanced metadata directly from the API. The server is designed to work with OAuth2 client credentials flow for authentication, so ensure your connected app is configured accordingly and the required domain URL is provided. Tools available include: search_objects, describe_object, describe_object_with_api, describe_relationship_fields, query_records, get_fields_by_type, get_picklist_values, get_validation_rules, and manage_debug_logs. Use these tools via prompts such as “Find all objects related to Accounts”, “Describe the Account fields”, or “Query Accounts where Industry equals Manufacturing and include related Contacts.”

Prerequisites:

• Docker installed and running on your machine or host.
• Salesforce OAuth2 credentials (Client ID, Client Secret, and Domain URL) with Client Credentials flow enabled for your connected app.

Installation steps:

1. Pull the MCP server image from Docker Hub: docker pull suraj20028/salesforce-mcp-server

2. Run the server container with your Salesforce credentials as environment variables. Replace the placeholders with your actual values: docker run -i --rm
   -e SALESFORCE_CLIENT_ID="<your-client-id>"
   -e SALESFORCE_CLIENT_SECRET="<your-client-secret>"
   -e SALESFORCE_USERNAME="<your-username>"
   -e SALESFORCE_PASSWORD="<your-password>"
   -e SALESFORCE_DOMAIN_URL="https://yourdomain.my.salesforce.com"
   suraj20028/salesforce-mcp-server

3. Verify the server starts and is accessible by your MCP client. Ensure network access to the container and that the Salesforce connected app is configured for client credentials flow.

4. Optional: If using VS Code integration, you can add the provided JSON block to your user settings or workspace .vscode/mcp.json (without the mcp key in the workspace file) to define the server configuration.

Tips and notes:

• The container requires Salesforce OAuth2 credentials and a domain URL. Ensure the connected app is configured for Client Credentials Flow and that an execution user is selected.
• If you encounter Docker permission errors, ensure your user is in the docker group or run with appropriate privileges.
• Environment variable placeholders in the MCP config example are intended to be filled by your MCP client interface (e.g., VS Code prompts, UI inputs).
• The server exposes a rich set of tools; start with search_objects and describe_object to understand the data model, then move to query_records for real data retrieval. For metadata, use describe_object_with_api and describe_relationship_fields.
• When using query_records, you can leverage relationships by including related object fields in the response and using where filters for precise results.
• If you need to adjust log verbosity or enable/disable debug logs, use manage_debug_logs with actions like enable, disable, or retrieve.