MCP server intelligence profile

Salesforce MCP Server

An MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata

Local Onlyusama-dtc
Awaiting current scanNpm · 0.0.2

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
7Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install @surajadsul02/mcp-server-salesforce from npm

Version 0.0.2 declares 1 executable entrypoint.

npm install --save-exact @surajadsul02/mcp-server-salesforce@0.0.2
npx -y -p @surajadsul02/mcp-server-salesforce@0.0.2 @surajadsul02/mcp-server-salesforce
MCP client configuration example
{
  "mcpServers": {
    "@surajadsul02/mcp-server-salesforce": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@surajadsul02/mcp-server-salesforce@0.0.2",
        "@surajadsul02/mcp-server-salesforce"
      ]
    }
  }
}

Identity

Canonical slugsalesforce-mcp-server-c253942dDeploymentLocal Only
Canonical packagenpm:@surajadsul02/mcp-server-salesforceRepositoryusama-dtc/salesforce_mcp
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npm@surajadsul02/mcp-server-salesforce0.0.21Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npm@surajadsul02/mcp-server-salesforce0.0.2CurrentSep 5, 20267 toolsSucceeded · 0 resources · 0 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2024-11-05Negotiated protocol
salesforce-mcp-serverServer-reported name
1Capability groups
Aug 18, 2026Observed

Tools 7

ToolCategoryAnnotationsRisk
salesforce_describe_objectGet detailed schema metadata including all fields, relationships, and field properties of any Salesforce object. Examples: 'Account' shows all Account fields including custom fields; 'Case' shows all Case fields including relationships to Account, Contact etc.
Input schema
{
  "type": "object",
  "properties": {
    "objectName": {
      "type": "string",
      "description": "API name of the object (e.g., 'Account', 'Contact', 'Custom_Object__c')"
    }
  },
  "required": [
    "objectName"
  ]
}
——
salesforce_dml_recordsPerform data manipulation operations on Salesforce records: - insert: Create new records - update: Modify existing records (requires Id) - delete: Remove records (requires Id) - upsert: Insert or update based on external ID field Examples: Insert new Accounts, Update Case status, Delete old records, Upsert based on custom external ID
Input schema
{
  "type": "object",
  "properties": {
    "operation": {
      "type": "string",
      "enum": [
        "insert",
        "update",
        "delete",
        "upsert"
      ],
      "description": "Type of DML operation to perform"
    },
    "objectName": {
      "type": "string",
      "description": "API name of the object"
    },
    "records": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Array of records to process"
    },
    "externalIdField": {
      "type": "string",
      "description": "External ID field name for upsert operations",
      "optional": true
    }
  },
  "required": [
    "operation",
    "objectName",
    "records"
  ]
}
——
salesforce_manage_fieldCreate new custom fields or modify existing fields on any Salesforce object: - Field Types: Text, Number, Date, Lookup, Master-Detail, Picklist etc. - Properties: Required, Unique, External ID, Length, Scale etc. - Relationships: Create lookups and master-detail relationships Examples: Add Rating__c picklist to Account, Create Account lookup on Custom Object Note: Changes affect metadata and require proper permissions
Input schema
{
  "type": "object",
  "properties": {
    "operation": {
      "type": "string",
      "enum": [
        "create",
        "update"
      ],
      "description": "Whether to create new field or update existing"
    },
    "objectName": {
      "type": "string",
      "description": "API name of the object to add/modify the field"
    },
    "fieldName": {
      "type": "string",
      "description": "API name for the field (without __c suffix)"
    },
    "label": {
      "type": "string",
      "description": "Label for the field",
      "optional": true
    },
    "type": {
      "type": "string",
      "enum": [
        "Checkbox",
        "Currency",
        "Date",
        "DateTime",
        "Email",
        "Number",
        "Percent",
        "Phone",
        "Picklist",
        "MultiselectPicklist",
        "Text",
        "TextArea",
        "LongTextArea",
        "Html",
        "Url",
        "Lookup",
        "MasterDetail"
      ],
      "description": "Field type (required for create)",
      "optional": true
    },
    "required": {
      "type": "boolean",
      "description": "Whether the field is required",
      "optional": true
    },
    "unique": {
      "type": "boolean",
      "description": "Whether the field value must be unique",
      "optional": true
    },
    "externalId": {
      "type": "boolean",
      "description": "Whether the field is an external ID",
      "optional": true
    },
    "length": {
      "type": "number",
      "description": "Length for text fields",
      "optional": true
    },
    "precision": {
      "type": "number",
      "description": "Precision for numeric fields",
      "optional": true
    },
    "scale": {
      "type": "number",
      "description": "Scale for numeric fields",
      "optional": true
    },
    "referenceTo": {
      "type": "string",
      "description": "API name of the object to reference (for Lookup/MasterDetail)",
      "optional": true
    },
    "relationshipLabel": {
      "type": "string",
      "description": "Label for the relationship (for Lookup/MasterDetail)",
      "optional": true
    },
    "relationshipName": {
      "type": "string",
      "description": "API name for the relationship (for Lookup/MasterDetail)",
      "optional": true
    },
    "deleteConstraint": {
      "type": "string",
      "enum": [
        "Cascade",
        "Restrict",
        "SetNull"
      ],
      "description": "Delete constraint for Lookup fields",
      "optional": true
    },
    "picklistValues": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "label": {
            "type": "string"
          },
          "isDefault": {
            "type": "boolean",
            "optional": true
          }
        }
      },
      "description": "Values for Picklist/MultiselectPicklist fields",
      "optional": true
    },
    "description": {
      "type": "string",
      "description": "Description of the field",
      "optional": true
    }
  },
  "required": [
    "operation",
    "objectName",
    "fieldName"
  ]
}
——
salesforce_manage_objectCreate new custom objects or modify existing ones in Salesforce: - Create: New custom objects with fields, relationships, and settings - Update: Modify existing object settings, labels, sharing model Examples: Create Customer_Feedback__c object, Update object sharing settings Note: Changes affect metadata and require proper permissions
Input schema
{
  "type": "object",
  "properties": {
    "operation": {
      "type": "string",
      "enum": [
        "create",
        "update"
      ],
      "description": "Whether to create new object or update existing"
    },
    "objectName": {
      "type": "string",
      "description": "API name for the object (without __c suffix)"
    },
    "label": {
      "type": "string",
      "description": "Label for the object"
    },
    "pluralLabel": {
      "type": "string",
      "description": "Plural label for the object"
    },
    "description": {
      "type": "string",
      "description": "Description of the object",
      "optional": true
    },
    "nameFieldLabel": {
      "type": "string",
      "description": "Label for the name field",
      "optional": true
    },
    "nameFieldType": {
      "type": "string",
      "enum": [
        "Text",
        "AutoNumber"
      ],
      "description": "Type of the name field",
      "optional": true
    },
    "nameFieldFormat": {
      "type": "string",
      "description": "Display format for AutoNumber field (e.g., 'A-{0000}')",
      "optional": true
    },
    "sharingModel": {
      "type": "string",
      "enum": [
        "ReadWrite",
        "Read",
        "Private",
        "ControlledByParent"
      ],
      "description": "Sharing model for the object",
      "optional": true
    }
  },
  "required": [
    "operation",
    "objectName"
  ]
}
——
salesforce_query_recordsQuery records from any Salesforce object using SOQL, including relationship queries. Examples: 1. Parent-to-child query (e.g., Account with Contacts): - objectName: "Account" - fields: ["Name", "(SELECT Id, FirstName, LastName FROM Contacts)"] 2. Child-to-parent query (e.g., Contact with Account details): - objectName: "Contact" - fields: ["FirstName", "LastName", "Account.Name", "Account.Industry"] 3. Multiple level query (e.g., Contact -> Account -> Owner): - objectName: "Contact" - fields: ["Name", "Account.Name", "Account.Owner.Name"] 4. Related object filtering: - objectName: "Contact" - fields: ["Name", "Account.Name"] - whereClause: "Account.Industry = 'Technology'" Note: When using relationship fields: - Use dot notation for parent relationships (e.g., "Account.Name") - Use subqueries in parentheses for child relationships (e.g., "(SELECT Id FROM Contacts)") - Custom relationship fields end in "__r" (e.g., "CustomObject__r.Name")
Input schema
{
  "type": "object",
  "properties": {
    "objectName": {
      "type": "string",
      "description": "API name of the object to query"
    },
    "fields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of fields to retrieve, including relationship fields"
    },
    "whereClause": {
      "type": "string",
      "description": "WHERE clause, can include conditions on related objects",
      "optional": true
    },
    "orderBy": {
      "type": "string",
      "description": "ORDER BY clause, can include fields from related objects",
      "optional": true
    },
    "limit": {
      "type": "number",
      "description": "Maximum number of records to return",
      "optional": true
    }
  },
  "required": [
    "objectName",
    "fields"
  ]
}
——
salesforce_search_allSearch across multiple Salesforce objects using SOSL (Salesforce Object Search Language). Examples: 1. Basic search across all objects: { "searchTerm": "John", "objects": [ { "name": "Account", "fields": ["Name"], "limit": 10 }, { "name": "Contact", "fields": ["FirstName", "LastName", "Email"] } ] } 2. Advanced search with filters: { "searchTerm": "Cloud*", "searchIn": "NAME FIELDS", "objects": [ { "name": "Account", "fields": ["Name", "Industry"], "orderBy": "Name DESC", "where": "Industry = 'Technology'" } ], "withClauses": [ { "type": "NETWORK", "value": "ALL NETWORKS" }, { "type": "SNIPPET", "fields": ["Description"] } ] } Notes: - Use * and ? for wildcards in search terms - Each object can have its own WHERE, ORDER BY, and LIMIT clauses - Support for WITH clauses: DATA CATEGORY, DIVISION, METADATA, NETWORK, PRICEBOOKID, SNIPPET, SECURITY_ENFORCED - "updateable" and "viewable" options control record access filtering
Input schema
{
  "type": "object",
  "properties": {
    "searchTerm": {
      "type": "string",
      "description": "Text to search for (supports wildcards * and ?)"
    },
    "searchIn": {
      "type": "string",
      "enum": [
        "ALL FIELDS",
        "NAME FIELDS",
        "EMAIL FIELDS",
        "PHONE FIELDS",
        "SIDEBAR FIELDS"
      ],
      "description": "Which fields to search in",
      "optional": true
    },
    "objects": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "API name of the object"
          },
          "fields": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Fields to return for this object"
          },
          "where": {
            "type": "string",
            "description": "WHERE clause for this object",
            "optional": true
          },
          "orderBy": {
            "type": "string",
            "description": "ORDER BY clause for this object",
            "optional": true
          },
          "limit": {
            "type": "number",
            "description": "Maximum number of records to return for this object",
            "optional": true
          }
        },
        "required": [
          "name",
          "fields"
        ]
      },
      "description": "List of objects to search and their return fields"
    },
    "withClauses": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "DATA CATEGORY",
              "DIVISION",
              "METADATA",
              "NETWORK",
              "PRICEBOOKID",
              "SNIPPET",
              "SECURITY_ENFORCED"
            ]
          },
          "value": {
            "type": "string",
            "description": "Value for the WITH clause",
            "optional": true
          },
          "fields": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Fields for SNIPPET clause",
            "optional": true
          }
        },
        "required": [
          "type"
        ]
      },
      "description": "Additional WITH clauses for the search",
      "optional": true
    },
    "updateable": {
      "type": "boolean",
      "description": "Return only updateable records",
      "optional": true
    },
    "viewable": {
      "type": "boolean",
      "description": "Return only viewable records",
      "optional": true
    }
  },
  "required": [
    "searchTerm",
    "objects"
  ]
}
——
salesforce_search_objectsSearch for Salesforce standard and custom objects by name pattern. Examples: 'Account' will find Account, AccountHistory; 'Order' will find WorkOrder, ServiceOrder__c etc.
Input schema
{
  "type": "object",
  "properties": {
    "searchPattern": {
      "type": "string",
      "description": "Search pattern to find objects (e.g., 'Account Coverage' will find objects like 'AccountCoverage__c')"
    }
  },
  "required": [
    "searchPattern"
  ]
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

Salesforce MCP Server questions

How do I install Salesforce MCP Server?

Install the selected package version with: npm install --save-exact @surajadsul02/mcp-server-salesforce@0.0.2

What tools does Salesforce MCP Server provide?

Salesforce MCP Server exposed 7 tools during independent protocol observation, including salesforce_describe_object, salesforce_dml_records, salesforce_manage_field, salesforce_manage_object, salesforce_query_records, salesforce_search_all, salesforce_search_objects.

Is Salesforce MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Company and product intelligence

These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.

Associated company landscape

Salesforce intelligence →

Association is based on retained identity fields; it does not by itself prove first-party publication.

Salesforce 107 matches

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.