Salesforce Interface Connector (Model Context Protocol)

This is an implementation of an MCP (Model Context Protocol) server specifically engineered to bridge the capabilities of Claude with the Salesforce platform, empowering users to manipulate Salesforce constructs—both data records and underlying metadata—using conversational language.

Core Capabilities

• Schema Definition Control: Programmatically devise and revise custom Salesforce objects and their associated fields through plain speech.
• Intelligent Entity Discovery: Locate Salesforce data structures even when only partial identification terms are provided.
• Exhaustive Structure Exposure: Retrieve granular specifics regarding fields and inter-object relationships for any given entity.
• Versatile Data Retrieval: Execute queries against records, supporting complex filtering mechanisms and cross-reference navigation.
• Record Lifecycle Operations: Effortlessly perform creation (Insert), modification (Update), removal (Delete), and combined creation/modification (Upsert) actions on data entities.
• Multi-Entity Exploration: Conduct comprehensive searches spanning several objects concurrently using SOSL capabilities.
• Transparent Feedback System: Receive unambiguous error reporting, specifically detailing issues encountered within the Salesforce environment.

Deployment Guide

Installation is achieved via npm:

bash npm install -g @surajadsul02/mcp-server-salesforce

Configuration Prerequisites

Establishing connectivity to Salesforce requires one of the subsequent authentication mechanisms:

1. Credential-Based Access (Username/Password)

1. Secure your primary access credentials.
2. Obtain your designated security token (available via Salesforce user settings reset).
3. Define the requisite environment parameters as illustrated in the setup sections below.

2. Token-Based Authorization (OAuth2 via Consumer Key/Secret)

1. Establish and configure a Connected Application within your Salesforce organization.
2. Procure the associated Consumer Key and Consumer Secret.
3. Set the required environment variables according to the configuration examples.

IDE Integration Setup

Cursor Environment Configuration

1. Ensure the utility is globally installed: bash npm install -g @surajadsul02/mcp-server-salesforce

2. Modify the Cursor IDE configuration file located at .cursor/mcp.json:

Utilizing Environment Variable Injection (env command)

{ "mcpServers": { "salesforce": { "command": "env", "args": [ "SALESFORCE_USERNAME=your.actual.email@example.com", "SALESFORCE_PASSWORD=YourActualPassword123", "SALESFORCE_TOKEN=YourActualSecurityToken123", "SALESFORCE_INSTANCE_URL=https://login.salesforce.com", "npx", "-y", "@surajadsul02/mcp-server-salesforce" ] } } }

For OAuth2 Provisioning within Cursor

{ "mcpServers": { "salesforce": { "command": "env", "args": [ "SALESFORCE_USERNAME=your.actual.email@example.com", "SALESFORCE_PASSWORD=YourActualPassword123", "SALESFORCE_TOKEN=YourActualSecurityToken123", "SALESFORCE_INSTANCE_URL=https://login.salesforce.com", "SALESFORCE_CONSUMER_KEY=YourConsumerKey", "SALESFORCE_CONSUMER_SECRET=YourConsumerSecret", "npx", "-y", "@surajadsul02/mcp-server-salesforce" ] } } }

Claude Desktop Environment Configuration

1. Global installation verification (if not already done): bash npm install -g @surajadsul02/mcp-server-salesforce

2. Insert the configuration block into your claude_desktop_config.json:

For Username/Password Authentication Method

{ "mcpServers": { "salesforce": { "command": "npx", "args": ["-y", "@surajadsul02/mcp-server-salesforce"], "env": { "SALESFORCE_USERNAME": "your_username", "SALESFORCE_PASSWORD": "your_password", "SALESFORCE_TOKEN": "your_security_token", "SALESFORCE_INSTANCE_URL": "https://login.salesforce.com" } } } }

For OAuth2 Credential Exchange

{ "mcpServers": { "salesforce": { "command": "npx", "args": ["-y", "@surajadsul02/mcp-server-salesforce"], "env": { "SALESFORCE_USERNAME": "your_username", "SALESFORCE_PASSWORD": "your_password", "SALESFORCE_CONSUMER_KEY": "your_consumer_key", "SALESFORCE_CONSUMER_SECRET": "your_consumer_secret", "SALESFORCE_INSTANCE_URL": "https://login.salesforce.com" } } } }

1. Configuration File Paths:
2. macOS Systems: ~/Library/Application Support/Claude Desktop/claude_desktop_config.json
3. Windows Systems: %APPDATA%\Claude Desktop\claude_desktop_config.json
4. Linux Systems: ~/.config/Claude Desktop/claude_desktop_config.json

Essential Environmental Variables

For Credential-Based Login: - SALESFORCE_USERNAME: Salesforce login identifier (email format). - SALESFORCE_PASSWORD: Corresponding user password. - SALESFORCE_TOKEN: Required session security credential. - SALESFORCE_INSTANCE_URL: Target Salesforce endpoint (Optional; defaults to the standard login URL).

For OAuth2 Authorization Flow: - SALESFORCE_USERNAME: Salesforce login identifier (email format). - SALESFORCE_PASSWORD: Corresponding user password. - SALESFORCE_CONSUMER_KEY: The identifier for the registered Connected Application. - SALESFORCE_CONSUMER_SECRET: The secret associated with the Connected Application. - SALESFORCE_INSTANCE_URL: Target Salesforce endpoint (Optional; defaults to the standard login URL).

Illustrative Examples

Entity Probing

"Query for all data structures linked to client Accounts" "Identify entities responsible for managing client service interactions" "What organizational data models are available for handling transactional fulfillment?"

Metadata Inspection

"List the accessible attributes within the Account structure?" "Provide the selection list options for the Case Priority field" "Detail the relational links defined on the Opportunity entity"

Data Retrieval Operations

"Fetch every Account record established within the current calendar month" "Return high-urgency Cases alongside their associated Contact details" "Locate all Opportunities valued above $100,000"

Custom Schema Administration

"Provision a new data structure named 'ClientFeedback'" "Incorporate a numerical field designated 'ReviewScore' into the Feedback structure" "Adjust the access control settings for the SupportTicket entity"

Broad Contextual Searching

"Search across Accounts and Opportunities for the term 'virtualization'" "Detect references to 'system outage' within Cases and internal documentation records" "Scan all pertinent data models for mentions of the client 'TechSolutions Inc.'"

Development Lifecycle

Source Code Compilation

bash

Repository acquisition

git clone https://github.com/surajadsul02/mcp-server-salesforce.git

Navigate into project root

cd mcp-server-salesforce

Install dependencies

npm install

Execute build scripts

npm run build

Troubleshooting Common Issues

1. Authorization Failures
2. Double-check all entered authentication values for correctness.
3. For credential access: Confirm the security token validity.

4. For OAuth2: Validate the Consumer Key/Secret pair.

5. Connectivity Problems

6. Verify the configured Salesforce instance URL.
7. Assess local network access to Salesforce endpoints.

8. Confirm the integrated Salesforce user possesses necessary API access rights.

9. Cursor IDE Debugging

10. Relaunch Cursor following any modifications to the MCP configuration file.
11. Utilize the integrated Developer Tools (accessible via Help menu) to monitor runtime exceptions.

12. Confirm the global installation status of the package.

13. Claude Desktop Debugging

14. Validate the exact path used for the configuration file.
15. Review file system permissions for read/write access.
16. Restart the Claude Desktop application after configuration file updates.
17. Ensure operating system environment variables are correctly propagated.

Collaboration Policy

We welcome external contributions. Please submit proposed enhancements or fixes via a Pull Request.

Licensing Information

This software is distributed under the terms of the MIT License. See the accompanying [LICENSE] file for comprehensive details.

Support Channels

Should you encounter bugs or require assistance, please initiate an issue report directly on the corresponding GitHub repository.

WIKIPEDIA: Business management tools encompass the entire ecosystem of systems, applications, regulatory controls, computational methodologies, and strategies employed by organizations to effectively navigate evolving market dynamics, maintain competitive superiority, and systematically enhance operational output.

== High-Level Summary == Management resources can be functionally categorized according to specific organizational departments and operational aspects—such as strategic planning, process orchestration, record-keeping, human capital management, decision support, and performance monitoring. A functional taxonomy typically encompasses these universal elements:

Resources dedicated to initial data capture and verification across all business units. Systems designed for the oversight and refinement of operational workflows. Platforms used for aggregating information and facilitating executive choices. Contemporary management apparatus has undergone profound technological transformation over the last decade, accelerated by rapid technological progress, making the selection of optimal business resources for any given scenario exceptionally challenging. This complexity stems from persistent pressures to reduce expenditures while simultaneously expanding revenue streams, the imperative to deeply understand evolving client requirements, and the necessity of delivering goods or services conforming precisely to those demands. Within this environment, leadership must adopt a strategic posture regarding business management instruments rather than defaulting to the newest available product. Over-reliance on unmodified, off-the-shelf solutions often results in systemic instability. Consequently, corporate assets must be chosen judiciously and subsequently tailored to align with the organization's distinct operational requirements, reversing the typical adoption sequence.

== Predominant Instruments == In 2013, a comprehensive assessment by Bain & Company charted the global usage patterns of business instruments, revealing how their derived value addressed regional necessities amid varying market conditions. The top ten instruments identified included:

Strategic planning frameworks Customer Relationship Management (CRM) suites Employee sentiment measurement programs Competitive benchmarking analysis Balanced Scorecard implementation Core competency identification Outsourcing strategies evaluation Organizational transformation programs Supply Chain Optimization (SCO) Formalized Mission and Vision statements Market segmentation analysis Total Quality Management (TQM) methodologies

== Commercial Software Applications == Software, defined as a collection of programmed instructions utilized by personnel to execute diverse enterprise functions, is commonly termed business software or an enterprise application. These applications are leveraged to elevate productivity levels, quantify performance metrics, and execute various corporate mandates with precision. The progression began with foundational Management Information Systems (MIS), advanced into comprehensive Enterprise Resource Planning (ERP) frameworks, subsequently incorporated Customer Relationship Management (CRM) modules, and has now migrated toward cloud-based enterprise management solutions. Although a measurable correlation exists between Information Technology investments and corporate efficacy, two elements are crucial for generating demonstrable added value: the efficiency of the deployment process and the rigorous selection and customization of the chosen resources.

== Tools Tailored for Small and Medium Enterprises (SMEs) == Resources specifically targeting SMEs are vital as they furnish mechanisms for cost containment and operational scaling...