Skip to main content
Book a demo

Salesforce

MCP server for Salesforce CRM - query, search, and manage records via SOQL and SOSL

Book a demo View documentation

Ways to connect

3 ways to connect Salesforce

Every one of them gets the same identity, policy, scanning, and audit. Pick the delivery and sign-in that fit your workspace.

Runlayer-hosted

Delivery
Built and hosted by Runlayer
Sign-in
Authentication varies
Tools
10
Documentation

Official sObjects server, Salesforce-hosted

Delivery
Hosted by Salesforce
Sign-in
OAuth
Tools
11
Documentation

Official sObjects server, Salesforce-hosted, sandbox or scratch org

Delivery
Hosted by Salesforce
Sign-in
OAuth
Tools
11
Documentation

Tools

21 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

21 tools found.

  • Create record

    Tool name: create_record

    Create a new Salesforce record.

  • Delete record

    Destructive

    Tool name: delete_record

    Delete a Salesforce record by ID.

  • Describe object

    Read only

    Tool name: describe_object

    Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.

  • Get limits

    Read only

    Tool name: get_limits

    Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.

  • Get record

    Read only

    Tool name: get_record

    Retrieve a single Salesforce record by its ID.

  • List objects

    Read only

    Tool name: list_objects

    List all sObjects (standard and custom objects) available in the Salesforce org.

  • Query

    Read only

    Tool name: query

    Execute a SOQL (Salesforce Object Query Language) query.

  • Query more

    Read only

    Tool name: query_more

    Retrieve the next page of results from a SOQL query.

  • Search

    Read only

    Tool name: search

    Execute a SOSL (Salesforce Object Search Language) search across multiple objects.

  • Update record

    Tool name: update_record

    Update an existing Salesforce record.

  • Create sobject record

    Tool name: createSobjectRecord

    Creates a new record.

  • Delete related record

    Tool name: deleteRelatedRecord

    Deletes a child record by navigating from a parent record through a relationship.

  • Delete sobject record

    Tool name: deleteSobjectRecord

    Permanently deletes a record by ID.

  • Find

    Tool name: find

    Executes a text search across multiple objects simultaneously.

  • Get object schema

    Tool name: getObjectSchema

    Returns Salesforce schema information optimized for LLM consumption.

  • Get related records

    Tool name: getRelatedRecords

    Retrieves child records related to a parent record by traversing relationships.

  • Get user info

    Tool name: getUserInfo

    Returns current user's identity, role, and preferences.

  • List recent sobject records

    Tool name: listRecentSobjectRecords

    Returns records of a specific type that the user recently viewed or modified.

  • Soql query

    Tool name: soqlQuery

    Executes a SOQL query to retrieve Salesforce records.

  • Update related record

    Tool name: updateRelatedRecord

    Updates a child record by navigating from a parent record through a relationship.

  • Update sobject record

    Tool name: updateSobjectRecord

    Updates an existing record by ID.

Compatibility

Connect Salesforce to the clients your teams already use

27 AI clients can connect to Salesforce through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaudeClaude CodeClaude CoworkChatGPTWindsurfGooseCodexHermesGumloopRaycastWarpGitHub CopilotGitHub Copilot CLIMicrosoft 365 CopilotGemini CLIZedCline CLIAntigravityOpenCodeCrushGleanLovablePerplexityECAOh My Pi

Why Runlayer

Why connect Salesforce through Runlayer?

One approved path

Approve Salesforce once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions