Get the FREE Ultimate OpenClaw Setup Guide →

mcp-salesforce

🚀 Complete MCP (Model Context Protocol) server for Salesforce integration with Claude Desktop. Provides seamless OAuth authentication, universal CRUD operations on any Salesforce object.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio aiondadotcom-mcp-salesforce npx @aiondadotcom/mcp-salesforce

How to use

This MCP server provides a seamless integration with Salesforce via OAuth-based authentication, enabling AI assistants to interact with any Salesforce organization through a generic, secure interface. It supports full CRUD operations on Salesforce records, dynamic schema discovery, context-aware suggestions, and a comprehensive backup/history system. The server handles the OAuth flow automatically through a secure browser-based setup, stores tokens and credentials in a user-safe location, and analyzes your Salesforce configuration to tailor responses and suggestions to your org. When using Claude or similar assistants, you can invoke Salesforce tools such as setup, learn, and record operations without manual authentication steps, as the server transparently manages token refresh and session validity.

To use the tools, first perform the interactive setup via the salesforce_setup utility exposed by the MCP server. This will prompt you for the Salesforce Connected App details (Client ID, Client Secret, and Instance URL). Once configured, Claude can automatically trigger authentication when needed and perform actions like querying objects, creating or updating records, inspecting schema, and backing up data. You can also trigger the learning component with salesforce_learn to analyze your org’s objects, fields, and relationships, enabling more accurate suggestions and faster context-aware interactions.

How to install

Prerequisites:

  • Node.js 18+ installed on your machine
  • macOS recommended for secure credential storage (per README guidance)
  • A Salesforce Connected App configured for OAuth (Consumer Key and Consumer Secret)

Option 1: NPX usage (no permanent installation)

  1. Ensure Node.js is installed on your system.
  2. Use the MCP configuration snippet below in your project or Claude configuration to run the server via NPX:

Configuration snippet (mcp_config.json): { "mcpServers": { "salesforce": { "command": "npx", "args": ["@aiondadotcom/mcp-salesforce"] } } }

  1. Run the server via your MCP client (e.g., Claude Desktop) which will invoke npx @aiondadotcom/mcp-salesforce.

Option 2: Development/setup from source

  1. Clone the repository and install dependencies:
git clone https://github.com/AiondaDotCom/mcp-salesforce.git
cd mcp-salesforce
npm install
  1. Configure credentials when prompted using the salesforce_setup tool, which stores tokens securely (default path is ~/.mcp-salesforce.json).
  2. Start the server locally (example using Node directly if you have a start script):
node src/index.js
  1. Add the local server to Claude Desktop or your editor as shown in the Configuration section of the README.

Prerequisites recap:

  • Node.js 18+ installed
  • Salesforce Connected App with OAuth configured
  • Access to the internet for NPX or local build tooling

Additional notes

Tips and notes:

  • Credentials are stored in the user’s home directory with restricted permissions (commonly ~/.mcp-salesforce.json and ~/.mcp-salesforce-cache/). Ensure proper file permissions (600) to protect sensitive data.
  • The MCP server supports automatic token refresh and OAuth-based authentication, reducing manual setup.
  • If you encounter OAuth authorization prompts, ensure your Connected App is configured with the correct callback URL (as per the readme, typically http://localhost:8080/callback).
  • For development, you can point your local Claude or editor configuration to a local Node path to run a custom index.js, useful for debugging or customizing behavior.
  • The server exposes features like salesforce_setup, salesforce_learn, and full CRUD operations; consult the README for exact command names and usage examples.
  • Cross-platform support is mentioned; on Windows, ensure the CLI is accessible and file paths follow Windows conventions.

Related MCP Servers

Sponsor this space

Reach thousands of developers