Skip to main content
Glama
enesjakozh
codefriar

Salesforce CLI MCP Server

by codefriar
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Salesforce CLI MCP Server

Model Context Protocol (MCP) server for providing Salesforce CLI functionality to LLM tools like Claude Desktop.

Overview

This MCP server wraps the Salesforce CLI (sf) command-line tool and exposes its commands as MCP tools and resources, allowing LLM-powered agents to:

  • View help information about Salesforce CLI topics and commands

  • Execute Salesforce CLI commands with appropriate parameters

  • Leverage Salesforce CLI capabilities in AI workflows

Related MCP server: Salesforce CLI MCP Server

Requirements

  • Node.js 18+ and npm

  • Salesforce CLI (sf) installed and configured

  • Your Salesforce org credentials configured in the CLI

Installation

# Clone the repository
git clone <repository-url>
cd sfMcp

# Install dependencies
npm install

Usage

Starting the server

# Basic usage
npm start

# With project roots
npm start /path/to/project1 /path/to/project2
# or using the convenience script
npm run with-roots /path/to/project1 /path/to/project2

# As an npx package with roots
npx -y codefriar/sf-mcp /path/to/project1 /path/to/project2

The MCP server uses stdio transport, which can be used with MCP clients like the MCP Inspector or Claude Desktop.

Configuring in Claude Desktop

To configure this MCP in Claude Desktop's .claude.json configuration:

{
  "tools": {
    "salesforce": {
      "command": "/path/to/node",
      "args": [
        "/path/to/sf-mcp/build/index.js",
        "/path/to/project1",
        "/path/to/project2"
      ]
    }
  }
}

Using the npm package directly:

{
  "tools": {
    "salesforce": {
      "command": "/path/to/npx", 
      "args": [
        "-y",
        "codefriar/sf-mcp",
        "/path/to/project1",
        "/path/to/project2"
      ]
    }
  }
}

Development

# Watch mode (recompiles on file changes)
npm run dev

# In another terminal
npm start [optional project roots...]

Available Tools and Resources

This MCP server provides Salesforce CLI commands as MCP tools. It automatically discovers and registers all available commands from the Salesforce CLI, and also specifically implements the most commonly used commands.

Core Tools

  • sf_version - Get the Salesforce CLI version information

  • sf_help - Get help information for Salesforce CLI commands

  • sf_cache_clear - Clear the command discovery cache

  • sf_cache_refresh - Refresh the command discovery cache

Project Directory Management (Roots)

For commands that require a Salesforce project context (like deployments), you must specify the project directory. The MCP supports multiple project directories (roots) similar to the filesystem MCP.

Configuration Methods

Method 1: Via Command Line Arguments

# Start the MCP with project roots
npm start /path/to/project1 /path/to/project2
# or
npx -y codefriar/sf-mcp /path/to/project1 /path/to/project2

When configured this way, the roots will be automatically named root1, root2, etc., with the first one set as default.

Method 2: Using MCP Tools

  • sf_set_project_directory - Set a Salesforce project directory to use for commands

    • Parameters:

      • directory - Path to a directory containing a sfdx-project.json file

      • name - (Optional) Name for this project root

      • description - (Optional) Description for this project root

      • isDefault - (Optional) Set this root as the default for command execution

  • sf_list_roots - List all configured project roots

  • sf_detect_project_directory - Attempt to detect project directory from user messages

Example usage:

# Set project directory with a name
sf_set_project_directory --directory=/path/to/your/sfdx/project --name=project1 --isDefault=true

# List all configured roots
sf_list_roots

# Or include in your message:
"Please deploy the apex code from the project in /path/to/your/sfdx/project to my scratch org"

Method 3: Claude Desktop Configuration Configure project roots in .claude.json as described below.

Using Project Roots

You can execute commands in specific project roots:

# Using resource URI
sf://roots/project1/commands/project deploy start --sourcedir=force-app

# Using rootName parameter
sf_project_deploy_start --sourcedir=force-app --rootName=project1

Project directory must be specified for commands such as deployments, source retrieval, and other project-specific operations. If multiple roots are configured, the default root will be used unless otherwise specified.

Key Implemented Tools

The following commands are specifically implemented and guaranteed to work:

Organization Management

  • sf_org_list - List Salesforce orgs

    • Parameters: json, verbose

  • sf_auth_list_orgs - List authenticated Salesforce orgs

    • Parameters: json, verbose

  • sf_org_display - Display details about an org

    • Parameters: targetusername, json

  • sf_org_open - Open an org in the browser

    • Parameters: targetusername, path, urlonly

Apex Code

  • sf_apex_run - Run anonymous Apex code

    • Parameters: targetusername, file, apexcode, json

  • sf_apex_test_run - Run Apex tests

    • Parameters: targetusername, testnames, suitenames, classnames, json

Data Management

  • sf_data_query - Execute a SOQL query

    • Parameters: targetusername, query, json

  • sf_schema_list_objects - List sObjects in the org

    • Parameters: targetusername, json

  • sf_schema_describe - Describe a Salesforce object

    • Parameters: targetusername, sobject, json

Deployment

  • sf_project_deploy_start - Deploy the source to an org

    • Parameters: targetusername, sourcedir, json, wait

Dynamically Discovered Tools

The server discovers all available Salesforce CLI commands and registers them as tools with format: sf_<topic>_<command>.

For example:

  • sf_apex_run - Run anonymous Apex code

  • sf_data_query - Execute a SOQL query

For nested topic commands, the tool name includes the full path with underscores:

  • sf_apex_log_get - Get apex logs

  • sf_org_login_web - Login to an org using web flow

The server also creates simplified aliases for common nested commands where possible:

  • sf_get as an alias for sf_apex_log_get

  • sf_web as an alias for sf_org_login_web

The available commands vary depending on the installed Salesforce CLI plugins.

Note: Command discovery is cached to improve startup performance. If you install new SF CLI plugins, use the sf_cache_refresh tool to update the cache, then restart the server.

Resources

The following resources provide documentation about Salesforce CLI:

  • sf://help - Main CLI documentation

  • sf://topics/{topic}/help - Topic help documentation

  • sf://commands/{command}/help - Command help documentation

  • sf://topics/{topic}/commands/{command}/help - Topic-command help documentation

  • sf://version - Version information

  • sf://roots - List all configured project roots

  • sf://roots/{root}/commands/{command} - Execute a command in a specific project root

How It Works

  1. At startup, the server checks for a cached list of commands (stored in ~/.sf-mcp/command-cache.json)

  2. If a valid cache exists, it's used to register commands; otherwise, commands are discovered dynamically

  3. During discovery, the server queries sf commands --json to get a complete list of available commands

  4. Command metadata (including parameters and descriptions) is extracted directly from the JSON output

  5. All commands are registered as MCP tools with appropriate parameter schemas

  6. Resources are registered for help documentation

  7. When a tool is called, the corresponding Salesforce CLI command is executed

Project Roots Management

For commands that require a Salesforce project context:

  1. The server checks if any project roots have been configured via sf_set_project_directory

  2. If multiple roots are configured, it uses the default root unless a specific root is specified

  3. If no roots are set, the server will prompt the user to specify a project directory

  4. Commands are executed within the appropriate project directory, ensuring proper context

  5. The user can add or switch between multiple project roots as needed

Project-specific commands (like deployments, retrievals, etc.) will automatically run in the appropriate project directory. For commands that don't require a project context, the working directory doesn't matter.

You can execute commands in specific project roots by:

  • Using the resource URI: sf://roots/{rootName}/commands/{command}

  • Providing a rootName parameter to command tools (internal implementation details)

  • Setting a specific root as the default with sf_set_project_directory --isDefault=true

Command Caching

To improve startup performance, the MCP server caches discovered commands:

  • The cache is stored in ~/.sf-mcp/command-cache.json

  • It includes all topics, commands, parameters, and descriptions

  • The cache has a validation timestamp and SF CLI version check

  • By default, the cache expires after 7 days

  • When you install new Salesforce CLI plugins, use sf_cache_refresh to update the cache

Troubleshooting Cache Issues

The first run of the server performs a full command discovery which can take some time. If you encounter any issues with missing commands or cache problems:

  1. Stop the MCP server (if running)

  2. Manually delete the cache file: rm ~/.sf-mcp/command-cache.json

  3. Start the server again: npm start

This will force a complete rediscovery of all commands using the official CLI metadata.

If specific commands are still missing, or you've installed new SF CLI plugins:

  1. Use the sf_cache_refresh tool from Claude Desktop

  2. Stop and restart the MCP server

Handling Nested Topics

The Salesforce CLI has a hierarchical command structure that can be several levels deep. This MCP server handles these nested commands by:

  • Converting colon-separated paths to underscore format (apex:log:get → sf_apex_log_get)

  • Providing aliases for common deep commands when possible (sf_get for sf_apex_log_get)

  • Preserving the full command hierarchy in the tool names

  • Using the official command structure from sf commands --json

Nested topic commands are registered twice when possible—once with the full hierarchy name and once with a simplified alias, making them easier to discover and use.

License

ISC

Available Tools

5 tools
sf_cache_clearA

Clear the cached SF command metadata to force a refresh

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates a mutation action ('Clear') that likely affects system state, but does not detail permissions, side effects, or error handling. It adds value by specifying the purpose (force refresh) but lacks depth on behavioral traits like reversibility or impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the action and outcome with no wasted words. It is front-loaded and appropriately sized for a simple tool, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple mutation with no parameters) and lack of annotations or output schema, the description is minimally adequate. It explains what the tool does but does not cover behavioral aspects like effects or usage context in depth. For a mutation tool, more disclosure would be beneficial, but it meets basic requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. Baseline is 4 for zero parameters, as the description focuses on tool purpose without unnecessary parameter repetition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Clear') and the target ('cached SF command metadata'), with the specific outcome of forcing a refresh. It distinguishes from siblings like sf_cache_refresh by emphasizing clearing rather than refreshing, though the distinction could be more explicit. No tautology or vagueness is present.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a refresh of metadata is needed, but does not explicitly state when to use this tool versus alternatives like sf_cache_refresh or other siblings. It provides some context (force a refresh) but lacks explicit guidance on prerequisites, exclusions, or comparisons with other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sf_cache_refreshB

Refresh the SF command cache by re-scanning all available commands

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool refreshes the cache by re-scanning commands, implying a read/write operation that updates cache state, but doesn't specify permissions needed, side effects, performance impact, or error handling. For a tool that likely modifies cache data, this is insufficient behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's action without unnecessary words. It is front-loaded with the core purpose ('Refresh the SF command cache') and adds clarifying detail ('by re-scanning all available commands'). Every part of the sentence contributes meaning, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, no annotations, and no output schema, the description is minimal. While it states what the tool does, it lacks context about why or when to use it, behavioral traits like side effects or performance, and what the output might be. For a cache operation tool, this leaves significant gaps in understanding its role and impact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools. No additional value is required beyond stating the tool's purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Refresh') and resource ('SF command cache'), and specifies the action ('by re-scanning all available commands'). It distinguishes from sibling 'sf_cache_clear' by indicating a refresh rather than a clear operation. However, it doesn't explicitly differentiate from other siblings like project directory tools, keeping it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'sf_cache_clear' or other cache-related operations. It lacks context about prerequisites, timing, or scenarios where this refresh is necessary versus other actions. This leaves the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sf_detect_project_directoryB

Get instructions for setting up Salesforce project directories for command execution

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get instructions,' implying a read-only operation that returns guidance, but it doesn't clarify if this requires specific permissions, what format the instructions are in, or if there are any side effects. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence: 'Get instructions for setting up Salesforce project directories for command execution.' It is front-loaded with the main purpose, has no unnecessary words, and efficiently conveys the tool's intent without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It states what the tool does but lacks details on the instruction format, prerequisites, or how it relates to sibling tools. For a tool that likely provides setup guidance, more context on the output or usage scenarios would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate as the description doesn't introduce confusion about parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get instructions for setting up Salesforce project directories for command execution.' It specifies the action ('Get instructions') and resource ('Salesforce project directories'), though it doesn't explicitly distinguish it from sibling tools like sf_set_project_directory. The purpose is clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing, or relationships with sibling tools such as sf_set_project_directory (which might actually set the directory) or sf_list_roots (which might list available directories). Without such context, the agent lacks clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sf_list_rootsB

List all configured Salesforce project directories and their metadata

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't cover important aspects like whether it's read-only, requires authentication, has rate limits, or what the output format looks like. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description provides basic purpose information but lacks important context about behavior, output format, and usage guidelines. For a tool with no annotations and no output schema, more completeness would be expected to help the agent understand what to expect from the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't add parameter information beyond what's in the schema, maintaining a baseline score of 4 for tools with no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('all configured Salesforce project directories and their metadata'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like sf_detect_project_directory or sf_set_project_directory, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, timing, or comparison to siblings like sf_cache_clear or sf_detect_project_directory, leaving the agent without contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sf_set_project_directoryB

Set a Salesforce project directory for command execution context

ParametersJSON Schema
NameRequiredDescriptionDefault
directoryYesThe absolute path to a directory containing an sfdx-project.json file
nameNoOptional name for this project root
descriptionNoOptional description for this project root
isDefaultNoSet this root as the default for command execution

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions setting a directory for 'command execution context,' which implies configuration/mutation, but doesn't specify whether this persists across sessions, requires specific permissions, or has side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and efficient, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks details on behavioral traits, usage context, and output expectations, which are crucial for a mutation tool in a set of related Salesforce commands.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description adds no additional semantic information about parameters beyond what's in the schema, such as usage examples or constraints. This meets the baseline for high schema coverage but doesn't provide extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Set') and the resource ('Salesforce project directory for command execution context'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like sf_detect_project_directory or sf_list_roots, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an sfdx-project.json file), when not to use it, or how it relates to sibling tools like sf_detect_project_directory. This leaves the agent with minimal context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updatesv1.0.0
    • Changedsf_cache_clear1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsf_cache_refresh1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsf_detect_project_directory1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsf_list_roots1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 5 tool updates
    • First observedsf_cache_clear
    • First observedsf_cache_refresh
    • First observedsf_detect_project_directory
    • First observedsf_list_roots
    • First observedsf_set_project_directory
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: cache_clear and cache_refresh handle metadata caching, detect_project_directory provides setup instructions, list_roots enumerates existing directories, and set_project_directory establishes execution context. The descriptions reinforce these boundaries, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'sf_verb_noun' pattern with snake_case throughout (e.g., sf_cache_clear, sf_detect_project_directory). This predictable naming scheme makes the tool set easy to navigate and understand at a glance.

Tool Count4/5

Five tools is reasonable for a Salesforce CLI server focused on project directory management and cache operations. It's slightly lean but covers core setup and maintenance tasks without feeling bloated or incomplete for its apparent scope.

Completeness3/5

The tool set covers project directory setup, listing, and context setting, plus cache management, but lacks direct Salesforce CLI command execution tools (e.g., running queries or deploying metadata). This creates a notable gap for agents needing to perform actual Salesforce operations, though the provided tools support preparatory workflows.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Salesforce MCP Server

    priyapanigrahy
    A
    license
    Not graded
    quality
    D
    maintenance
    Integrates Claude with Salesforce to enable natural language querying, modification, and management of Salesforce records and metadata. It supports comprehensive operations including object/field management, SOSL searches, and Apex code execution.
    1,965
    1
    MIT

  • Salesforce CLI MCP Server

    perrynet
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to interact with Salesforce organizations through project-based CLI integration, allowing execution of Apex, SOQL queries, object descriptions, and org management using local Salesforce DX project configurations.
    MIT

  • Salesforce MCP Server

    jaworjar95
    A
    license
    A
    quality
    D
    maintenance
    Enables AI tools like Claude Desktop and Cline to interact with Salesforce, providing tools for SOQL queries, Apex execution, metadata management, and more.
    17
    404
    43
    MIT

  • Salesforce CLI MCP Server

    timaw513-emergenit
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to interact with Salesforce orgs through natural language commands, supporting org management, SOQL queries, metadata operations, testing, and more.
    1
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codefriar/sf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server