Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.semwalajay83-sem/salesforce-metadata-mcp

NPM · SALESFORCE-METADATA-MCP · SCANNED AUG 3

The only Salesforce MCP with Agentforce, OmniStudio & DevOps Center tools — 222 total.

+22 this week 65 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security83
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.17, reached via @modelcontextprotocol/sdk > @hono/node-server. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (107 of 111), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 38003 tokens (~171/item across 222 items; 222 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability check failed: the tool surface changed between 2.7.0 and 2.8.7: 0 tool removals, 1 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · salesforce-metadata-mcp

# add to Claude Code
claude mcp add semwalajay83-sem-salesforce-metadata-mcp -- npx -y salesforce-metadata-mcp
# add to Codex CLI
codex mcp add semwalajay83-sem-salesforce-metadata-mcp -- npx -y salesforce-metadata-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "semwalajay83-sem-salesforce-metadata-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "salesforce-metadata-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add semwalajay83-sem-salesforce-metadata-mcp --command npx --arg -y --arg salesforce-metadata-mcp
# ~/.hermes/config.yaml
mcp_servers:
  semwalajay83-sem-salesforce-metadata-mcp:
    command: "npx"
    args: ["-y", "salesforce-metadata-mcp"]
// mcp.json
{
  "mcpServers": {
    "semwalajay83-sem-salesforce-metadata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +39
    • Known CVEs: unverified → fail security
    • Stability: unverified → fail security
    • Malware scan: unverified → pass security
    • Schema quality: unverified → excellent functional
    • MCP protocol: unverified → pass functional
    • Dependency health: unverified → partial functional
  • 1 Aug 26 −9
    • Known CVEs: fail → unverified security
    • Dependency health: partial → unverified functional
  • 31 Jul 26 +20
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +7
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Security disclosure: unverified → fail functional
    • Dependency health: partial → unverified functional
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Licence: MIT functional
  • 29 Jul 26 −16
    • Malware scan: pass → unverified security
    • Security disclosure: fail → unverified functional
    • Dependency health: unverified → partial functional
    • Package version: 2.7.0 → 2.8.0 functional
  • 28 Jul 26 −19
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 43

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-frvp-7c67-39w9 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
Dependencies 107 packages

107 packages in the resolved dependency tree · 107 deprecated · 39 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 222 exposed · ~38,003 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
sf_create_matching_rule ~132

Creates a Matching Rule used by Duplicate Rules to detect potential duplicate records. Define which fields to match on and which matching algorithm to use (Exact, FirstName, LastName, Company, Email, Phone, etc.). Must be created before creating a Duplicate Rule that references it.

NameTypeReqDescription
descriptionstringDescription
labelstringyesDisplay label
matchingRuleItemsarrayyesFields and methods used for matching
objectNamestringyesObject API name, e.g. 'Lead', 'Contact', 'Account'
ruleNamestringyesMatching rule developer name

No output schema declared.

No examples provided.

sf_create_mcp_server ~187

Generates a complete, working MCP server project structure on disk targeting a Salesforce org. Creates package.json, tsconfig.json, src/index.ts entry point, .env.example, and README.md. The generated server uses the MCP SDK and includes a sample 'hello_world' tool. Provide an outputDirectory (absolute path) where the files will be written. After generation, run 'npm install' then 'npm run build' in that directory.

NameTypeReqDescription
descriptionstringServer description
outputDirectorystringyesAbsolute path to directory where files will be created, e.g. 'C:/projects/my-server'
salesforceInstanceUrlstringSalesforce instance URL to pre-configure, e.g. 'https://myorg.salesforce.com'
serverNamestringyesName for the new MCP server, e.g. 'my-salesforce-server'

No output schema declared.

No examples provided.

sf_create_mcp_tool ~165

Adds a new tool definition to an existing MCP server project by reading the src/index.ts file and appending the tool registration. Provide the tool name, description, input schema as a JSON object (field names to {type, description}), and handler code. The tool code is inserted before the 'Start server' section. Run 'npm run build' after adding tools.

NameTypeReqDescription
handlerCodestringyesTypeScript handler function body code
inputSchemaobjectyesJSON Schema for the tool's input parameters
projectDirectorystringyesAbsolute path to the MCP server project directory
toolDescriptionstringyesDetailed description of what the tool does
toolNamestringyesTool API name, e.g. 'get_account_data'

No output schema declared.

No examples provided.

sf_create_messaging_channel ~272

Creates a Messaging Channel for Salesforce digital engagement (SMS, WhatsApp, Facebook Messenger, Apple Messages for Business, etc.). channelType options: SMS, WhatsApp, Facebook, AppleBusinessChat, Line, GoogleBusinessMessages, EinsteinBotChannel, WebChat phoneNumber: E.164 format phone number for SMS/WhatsApp channels (e.g. +15551234567) pageId: Facebook Page ID or equivalent external platform identifier routingType: Queue (route to a queue) or Bot (route to an Einstein Bot first) queueName: required when routingType=Queue botName: required when routingType=Bot (bot handles initial messages) After creating, configure the channel with sf_create_embedded_service to add it to a site.

NameTypeReqDescription
botNamestringBot API name for bot-first routing
channelNamestringyesAPI name / MasterLabel for the Messaging Channel
channelTypestringyes
descriptionstring
labelstringyes
pageIdstringFacebook Page ID for Facebook Messenger
phoneNumberstringPhone number for SMS/WhatsApp channels
queueNamestringQueue DeveloperName to route work items to
routingTypestring

No output schema declared.

No examples provided.

sf_create_milestone ~134

Creates a Milestone Type that can be referenced in Entitlement Processes to define SLA checkpoints. Milestones represent required steps (e.g., 'First Response', 'Resolution') with time-based targets. fullName: milestone type API name name: display name description: optional description recurrenceType: how the milestone repeats — recursIndependently, recursChained, or noRecurrence

NameTypeReqDescription
descriptionstringDescription
fullNamestringyesMilestone type API name
namestringyesDisplay name
recurrenceTypestringRecurrence behaviour

No output schema declared.

No examples provided.

sf_create_muting_permission_set ~113

Creates a Muting Permission Set that removes specific permissions from users in a Permission Set Group. Use to create exceptions — e.g., a Permission Set Group grants broad access, and a Muting Permission Set removes a subset of that access for specific users. fullName: muting permission set API name label: display label description: optional description

NameTypeReqDescription
descriptionstringDescription
fullNamestringyesMuting permission set API name
labelstringyesDisplay label

No output schema declared.

No examples provided.

sf_create_named_credential ~217

Creates a Named Credential for making authenticated callouts to external systems from Apex or Flows. Named Credentials store the endpoint URL and authentication details securely, so developers don't hardcode credentials. Supports NoAuthentication, Basic (username/password), OAuth, and more. Use with sf_create_remote_site_setting to also allow the URL.

NameTypeReqDescription
allowCalloutbooleanAllow callouts using this credential
allowFormulabooleanAllow formulas in HTTP body (enables merge fields)
endpointstringyesEndpoint URL, e.g. 'https://api.example.com'
fullNamestringyesNamed credential API name, e.g. 'My_External_API'
labelstringyesDisplay label
passwordstringPassword for Password protocol (encrypted at rest)
principalTypestringNamedUser: shared credentials. PerUserPrincipal: per-user OAuth. Anonymous: no auth.
protocolstringAuthentication protocol
usernamestringUsername for Password protocol

No output schema declared.

No examples provided.

sf_create_next_best_action ~221

Creates a Next Best Action (NBA) recommendation strategy (RecommendationStrategy metadata type). NBA strategies surface contextual recommendations to agents and customers on record pages, communities, and chatbots. A strategy defines: - contextObjectApiName: the record type that provides context (e.g. 'Account', 'Case', 'Opportunity') - recommendations: a list of actions the agent can offer, each with Accept/Decline buttons and an optional Flow to execute on acceptance NBA strategies can be displayed via: - Einstein Next Best Action component on a Lightning Record Page - OmniScripts and FlexCards - Service Console After creating, add the "Einstein Next Best Action" Lightning component to a record page and configure it to use this strategy.

NameTypeReqDescription
contextObjectApiNamestringObject that provides context, e.g. 'Account', 'Case'
descriptionstringStrategy description
labelstringyesStrategy display label
recommendationsarrayRecommendation definitions
strategyNamestringyesStrategy API name

No output schema declared.

No examples provided.

sf_create_notification_type ~136

Creates a Custom Notification Type for sending in-app and mobile push notifications. Custom notification types can be triggered from Flows, Apex, or Process Builder. Users receive notifications in the Salesforce Bell icon (desktop) and on the Salesforce mobile app. fullName: notification type API name masterLabel: display label customNotifTypeName: developer name for the notification type description: optional description

NameTypeReqDescription
customNotifTypeNamestringyesDeveloper name for the notification type
descriptionstringDescription
fullNamestringyesCustom notification type API name
masterLabelstringyesMaster label

No output schema declared.

No examples provided.

sf_create_omniscript ~293

Creates an OmniStudio OmniScript — a guided interaction flow for collecting data or performing processes. OmniScripts are identified by Type + SubType + Language (e.g. AccountOpening / Personal / English). The fullName becomes Type_SubType_Language. The script is created inactive with the specified elements. Complex element configuration (branching logic, custom LWC overrides, remote actions) should be finalized in the OmniScript Designer after creation. isLwcEnabled: true deploys the script as a Lightning Web Component (recommended for performance). isOmniScriptEmbeddable: true allows embedding this script inside other OmniScripts. Use sf_activate_omniscript to activate after creation.

NameTypeReqDescription
descriptionstring
elementsarrayScript elements; complex structures are set via the OmniScript designer
isLwcEnabledbooleanUse LWC runtime (recommended for new scripts)
isOmniScriptEmbeddablebooleanAllow embedding in OmniStudio cards
labelstringyes
languagestringLanguage label, default English
scriptNamestringIgnored — fullName is derived from type_subType_language
subTypestringyesOmniScript sub-type, e.g. 'Create', 'Edit'
typestringyesOmniScript type, e.g. 'Account', 'Claims'

No output schema declared.

No examples provided.

sf_create_outbound_change_set ~119

Creates an Outbound Change Set in the org — a container for metadata components that can be deployed to connected orgs (sandbox → production). Optionally adds specified components immediately. Returns the change set ID and a link to view it in Setup. Use this before deploying to production when using the change set deployment model.

NameTypeReqDescription
changeSetNamestringyesName for the outbound change set
componentsarrayMetadata components to add to the change set
descriptionstringDescription of what this change set contains

No output schema declared.

No examples provided.

sf_create_outbound_message ~196

Creates a Workflow Outbound Message that sends a SOAP XML payload to an external endpoint when triggered by a Workflow Rule or Approval Process. Use for real-time integration with external systems that need to be notified of record changes. objectName: object the message is for fullName: developer name for the outbound message name: display name endpointUrl: external SOAP endpoint URL fields: field API names to include in the message integrationUser: optional username to authenticate the callout

NameTypeReqDescription
descriptionstringDescription
endpointUrlstringyesSOAP endpoint URL
fieldsarrayyesField API names to include in the message
fullNamestringyesOutbound message developer name
integrationUserstringUsername of the integration user (optional)
namestringyesDisplay name
objectNamestringyesObject API name, e.g. 'Opportunity'

No output schema declared.

No examples provided.

sf_create_package ~161

Creates a second-generation managed or unlocked package using the SF CLI. Packages bundle metadata for distribution. Managed packages support namespacing and AppExchange listing; unlocked packages support source-tracking without namespacing. name: package name packageType: Managed or Unlocked path: source path for the package, e.g. 'force-app' description: optional description noNamespace: create without a namespace (Unlocked packages only)

NameTypeReqDescription
descriptionstringPackage description
namestringyesPackage name
noNamespacebooleanCreate without a namespace (Unlocked only)
packageTypestringyesPackage type: Managed or Unlocked
pathstringyesPath to package source, e.g. 'force-app'

No output schema declared.

No examples provided.

sf_create_package_version ~162

Creates a new version of an existing second-generation package. Each version captures the current state of the package source. Package versions can be promoted and installed in target orgs. packageId: Package ID (0Ho...) or package alias installationKey: optional key to protect the version codeVersion: version number, e.g. '1.0.0.NEXT' wait: minutes to wait for version creation to complete

NameTypeReqDescription
codeVersionstringVersion number, e.g. '1.0.0.NEXT'
installationKeystringInstallation key for the package version
packageIdstringyesPackage ID (0Ho...) or package alias
waitintegerMinutes to wait for version creation

No output schema declared.

No examples provided.

sf_create_page_layout ~138

Creates a Page Layout for a Salesforce object. Page Layouts control what fields, related lists, and buttons appear on record detail and edit pages. Layouts are assigned to user profiles and record types. Define sections with fields and the related lists to include.

NameTypeReqDescription
labelstringyesLayout display label
layoutNamestringyesLayout developer name, e.g. 'Account_Layout'
objectNamestringyesObject API name, e.g. 'Account' or 'Case__c'
relatedListsarrayRelated list API names to include
sectionsarrayLayout sections with fields

No output schema declared.

No examples provided.

sf_create_path_assistant ~156

Creates a Path Assistant (Sales Path or Kanban path) for a Salesforce object picklist field via the Metadata API. Define path items for each picklist value with optional guidance text, info titles, and key fields to highlight at each stage. Activate the path to make it visible to users.

NameTypeReqDescription
fieldNamestringyesPicklist field API name, e.g. 'StageName'
isActivebooleanWhether the path is active
labelstringyesDisplay label
objectNamestringyesObject API name, e.g. 'Opportunity'
pathItemsarrayyesPath items for each picklist value
pathNamestringyesPath assistant API name

No output schema declared.

No examples provided.

sf_create_permission_set ~173

Creates a Permission Set with object permissions, field permissions, Apex class access, and user permissions. Permission Sets extend a user's access without changing their profile. Use when you need to grant specific permissions to a subset of users (e.g., a 'Sales Manager' permission set that allows deleting opportunities).

NameTypeReqDescription
apexClassAccessesarrayApex class access permissions
descriptionstringDescription of this permission set
fieldPermissionsarrayField-level permissions to grant
fullNamestringyesPermission set API name, e.g. 'Sales_Manager_Perms'
labelstringyesDisplay label
objectPermissionsarrayObject-level permissions to grant
tabSettingsarrayTab visibility settings
userPermissionsarrayUser-level permissions

No output schema declared.

No examples provided.

sf_create_permission_set_group ~123

Creates a Permission Set Group that aggregates multiple Permission Sets into a single assignable unit. Users assigned the group receive all permissions from all included permission sets. Simplifies administration when users need a combination of permissions. fullName: Permission Set Group API name label: display label permissionSets: array of Permission Set API names to include

NameTypeReqDescription
descriptionstringDescription
fullNamestringyesPermission Set Group API name
labelstringyesDisplay label
permissionSetsarrayyesAPI names of permission sets to include

No output schema declared.

No examples provided.

sf_create_platform_cache_partition ~132

Creates a Platform Cache partition in the Salesforce org via the Metadata API. Platform Cache improves app performance by storing data server-side close to Apex code. Allocate capacity for session cache (per-user, per-session) and org cache (shared across all users). Optionally mark as the default partition.

NameTypeReqDescription
descriptionstringDescription
isDefaultPartitionbooleanWhether this is the default partition
orgCacheSizeintegerOrg cache size in MB
partitionNamestringyesCache partition API name
sessionCacheSizeintegerSession cache size in MB

No output schema declared.

No examples provided.

sf_create_platform_event ~164

Creates a Platform Event object (ending in __e) for event-driven architecture. Platform Events enable real-time publish/subscribe communication between systems. Publishers fire events and subscribers (Flows, Apex triggers, external systems) react to them. PublishAfterCommit waits for DML to commit; PublishImmediately fires right away.

NameTypeReqDescription
descriptionstringDescription of the event
fieldsarrayCustom fields on the platform event
fullNamestringyesPlatform event API name, e.g. 'Order_Created__e'
labelstringyesSingular label
pluralLabelstringyesPlural label
publishBehaviorstringPublishAfterCommit: published when DML transaction commits. PublishImmediately: published regardless of transaction.

No output schema declared.

No examples provided.

sf_create_platform_event_trigger ~168

Creates an Apex trigger that fires when a Platform Event message is received (after insert). Use to process incoming platform events with Apex logic — e.g., creating records, sending notifications, or calling external APIs when an event is published. triggerName: Apex trigger name eventApiName: Platform event API name, e.g. 'MyEvent__e' body: Apex code body for the trigger apiVersion: Salesforce API version

NameTypeReqDescription
apiVersionstringAPI version, e.g. '62.0'
bodystringyesApex trigger body code
eventApiNamestringyesPlatform event API name, e.g. 'MyEvent__e'
triggerNamestringyesApex trigger name, e.g. 'HandleMyEvent'

No output schema declared.

No examples provided.

sf_create_presence_configuration ~148

Creates a Presence Configuration (PresenceUserConfig) that controls which Service Channels agents can handle and their total work capacity. capacity: total capacity units available to agents with this configuration serviceChannels: list of Service Channel API names the agents can work on allowAgentsToChangeStatus: whether agents can manually change their presence status Assign this configuration to agents via their Profile or Permission Set.

NameTypeReqDescription
allowAgentsToChangeStatusboolean
capacityintegerMaximum concurrent work items per agent
configNamestringyesAPI name of the PresenceUserConfig
descriptionstring
labelstringyes
serviceChannelsarray

No output schema declared.

No examples provided.

sf_create_presence_status ~132

Creates a Presence Status that agents can set to indicate their availability. statusType: - Online: agent is available for all assigned channels - Busy: agent is limited to specific channels - Offline: agent receives no work items serviceChannels: for Busy status, list which channels remain active. After creating, assign the status to profiles/permission sets with sf_assign_presence_status.

NameTypeReqDescription
labelstringyes
serviceChannelsarrayServiceChannel API names to associate
statusNamestringyesAPI name / DeveloperName of the Presence Status
statusTypestring

No output schema declared.

No examples provided.

sf_create_price_book ~203

Creates a Pricebook2 record and optionally adds products with pricing via PricebookEntry records. Price books define the prices for your products. Each org has one standard price book; additional custom price books can be used for different customer segments or regions. name: price book name isActive: whether the price book is active isStandard: true only for the standard price book currencyIsoCode: ISO currency code (e.g. 'USD') products: optional array of {productId, unitPrice, useStandardPrice?} to add to the price book

NameTypeReqDescription
currencyIsoCodestringCurrency ISO code, e.g. 'USD'
descriptionstringDescription
isActivebooleanWhether the price book is active
isStandardbooleanWhether this is the standard price book
namestringyesPrice book name
productsarrayProducts to add to this price book

No output schema declared.

No examples provided.

sf_create_product ~185

Creates a Salesforce Product2 record. Products represent items or services that can be added to Opportunities and Quotes via Opportunity Line Items. Use with sf_create_price_book to set pricing. name: product name productCode: optional SKU or product code description: optional description isActive: whether the product is available for use (default: true) family: product family/category, e.g. 'Hardware' quantityUnitOfMeasure: unit of measure, e.g. 'Each', 'Hour'

NameTypeReqDescription
descriptionstringProduct description
familystringProduct family, e.g. 'Hardware'
isActivebooleanWhether the product is active
namestringyesProduct name
productCodestringProduct code / SKU
quantityUnitOfMeasurestringUnit of measure, e.g. 'Each'

No output schema declared.

No examples provided.

sf_create_public_group ~92

Creates a Public Group (Group SObject with Type=Regular) for sharing rules, email distribution, or queue membership. Public groups can include users, roles, and other groups. Use as a sharing target in sf_create_sharing_rule.

NameTypeReqDescription
groupNamestringyesGroup developer name (no spaces)
labelstringyesGroup display name
membersarrayInitial group members

No output schema declared.

No examples provided.

sf_create_push_topic ~193

Creates a Streaming API PushTopic for real-time record change notifications via the SObject API. Clients subscribe to /topic/TopicName using the CometD protocol. Specify the SOQL query that filters which records trigger events, and configure which operations (create, update, delete, undelete) and fields trigger notifications.

NameTypeReqDescription
apiVersionnumberAPI version number (e.g. 62)
notifyForFieldsstringWhich fields trigger notifications
notifyForOperationCreatebooleanNotify on record create
notifyForOperationDeletebooleanNotify on record delete
notifyForOperationUndeletebooleanNotify on record undelete
notifyForOperationUpdatebooleanNotify on record update
querystringyesSOQL query for the PushTopic
topicNamestringyesPushTopic name (max 25 chars)

No output schema declared.

No examples provided.

sf_create_queue ~168

Creates a Queue in Salesforce. Queues are groups of users that can be assigned records (Cases, Leads, etc.). When a record is assigned to a queue, any queue member can work on it. Use for support teams, sales teams, or any scenario where multiple people share a pool of records to process.

NameTypeReqDescription
doesSendEmailToMembersbooleanSend email to all queue members when record is added
emailstringQueue email address for notifications
fullNamestringyesQueue API name, e.g. 'Support_Level_1'
namestringyesQueue display name
queueMembersobjectQueue members
supportedObjectsarrayyesObject API names this queue supports, e.g. ['Case', 'Lead']

No output schema declared.

No examples provided.

sf_create_queue_routing_config ~137

Associates a Routing Configuration with an existing Queue, enabling OmniChannel routing for that queue. After creating a Routing Configuration (sf_create_routing_configuration), use this tool to link it to the Queue that holds the work items. Work items assigned to the queue will then be routed to agents using the specified routing model. queueDeveloperName: the API name of the Queue (DeveloperName, not label) routingConfigName: the API name of the Routing Configuration to link

NameTypeReqDescription
queueDeveloperNamestringyesDeveloperName of the existing queue
routingConfigNamestringyesAPI name of the RoutingConfiguration to link

No output schema declared.

No examples provided.

sf_create_quick_action ~160

Creates an object-specific quick action on a Salesforce object via the Metadata API. Supports Create, Update, LogACall, and SendEmail action types. Optionally specify a target object (for Create type) and the fields to include in the action layout.

NameTypeReqDescription
actionNamestringyesQuick action API name
actionTypestringyesType of quick action
descriptionstringDescription of the quick action
fieldsarrayFields to include in the quick action layout
labelstringyesDisplay label for the quick action
objectNamestringyesObject API name, e.g. 'Account'
targetObjectstringTarget object API name (required for Create type)

No output schema declared.

No examples provided.

sf_create_record ~111

Creates a single SObject record via the Salesforce REST API. Provide the object API name and a fields object with field API names and values. For bulk creation (100+ records), use sf_bulk_import_records instead.

NameTypeReqDescription
fieldsobjectyesKey-value pairs of field API names to values, e.g. {Name: 'Acme', Industry: 'Technology'}
objectApiNamestringyesSObject API name, e.g. 'Account', 'Contact', 'My_Object__c'

No output schema declared.

No examples provided.

sf_create_record_type ~179

Creates a Record Type on a Salesforce object. Record Types allow different page layouts, picklist values, and business processes for different types of records on the same object. For example, create 'Enterprise' and 'SMB' record types on Opportunity with different Stage values.

NameTypeReqDescription
businessProcessstringBusiness process API name to associate (for Opportunity/Lead/Case/Solution)
descriptionstringDescription
fullNamestringyesRecord type developer name, e.g. 'Enterprise_Deal'
isActivebooleanWhether this record type is active
labelstringyesRecord type label
objectNamestringyesObject API name, e.g. 'Opportunity' or 'Case__c'
picklistValuesarrayRestrict picklist values per record type

No output schema declared.

No examples provided.

sf_create_remote_site_setting ~161

Creates a Remote Site Setting to allow an external URL for Apex callouts. Salesforce blocks outbound HTTP calls by default — adding a Remote Site Setting allows Apex code to call that URL. Required for any external API callout from Apex or Flows. Use with sf_create_named_credential for authenticated callouts.

NameTypeReqDescription
descriptionstringDescription of why this site is trusted
disableProtocolSecuritybooleanDisable protocol security (not recommended)
fullNamestringyesRemote site setting API name
isActivebooleanWhether this remote site setting is active
namestringyesDisplay name
urlstringyesURL to allow for callouts, e.g. 'https://api.example.com'

No output schema declared.

No examples provided.

sf_create_report ~199

Creates a Salesforce Report using the Report metadata type. Supports Tabular, Summary, Matrix, and Joined formats. Specify the report type (e.g., Accounts, Opportunities), columns to display, and optional filters. Reports are created in the specified folder or your personal folder by default.

NameTypeReqDescription
columnsarrayyesField API names to include as columns, e.g. ['ACCOUNT_NAME', 'ANNUAL_REVENUE']
descriptionstringReport description
filtersarrayReport filters
folderNamestringFolder API name for the report
formatstringReport format
groupByFieldstringField to group by (Summary/Matrix formats)
labelstringyesReport display name
reportNamestringyesReport API name
reportTypestringyesReport type API name, e.g. 'Account', 'Opportunity', 'AccountList'

No output schema declared.

No examples provided.

sf_create_report_folder ~107

Creates a folder for organizing Reports or Dashboards. Folder access types: Hidden (only owner), Shared (explicit sharing), Public (all users). After creating, use sf_share_report_folder to grant access to specific users, roles, or groups.

NameTypeReqDescription
accessTypestringFolder access type
folderNamestringyesFolder API name
folderTypestringWhether this is a report or dashboard folder
labelstringyesFolder display name

No output schema declared.

No examples provided.

sf_create_report_type ~150

Creates a Custom Report Type that defines what objects and fields are available when building reports. A report type specifies a primary object and optionally related objects (joined via relationships). Use when the standard report types don't include the data you need, or when you want to create a specialized reporting structure.

NameTypeReqDescription
baseObjectstringyesPrimary object API name, e.g. 'Account', 'Opportunity'
categorystringReport category for organization
deployedbooleanDeploy this report type immediately
descriptionstringDescription
fullNamestringyesReport type developer name
labelstringyesDisplay label
relationshipsarrayRelated object joins

No output schema declared.

No examples provided.

sf_create_role ~204

Creates a Role in the Salesforce role hierarchy. Roles control record visibility through role-based sharing. Users in higher roles can see records owned by users in subordinate roles. Specify a parentRole to place this role in the hierarchy, or omit it for a top-level role.

NameTypeReqDescription
accountAccessLevelstringAccount and contact access level for subordinates
caseAccessLevelstringCase access level for subordinates
contactAccessLevelstringContact access level for subordinates
descriptionstringDescription of this role
fullNamestringyesRole API name, e.g. 'VP_Sales'
mayForecastManagerSharebooleanGrant manager forecast sharing
namestringyesRole display name, e.g. 'VP of Sales'
opportunityAccessLevelstringOpportunity access level for subordinates
parentRolestringParent role API name (omit for top-level role)

No output schema declared.

No examples provided.

sf_create_role_hierarchy ~126

Creates multiple Salesforce roles in the role hierarchy in a single call. Roles control record visibility — users in higher roles see records owned by subordinate-role users (depending on OWD settings). Use to set up an entire hierarchy at once. roles: array of {fullName, name, parentRole?, description?} - fullName: role API name (e.g. 'VP_Sales') - name: display label - parentRole: API name of parent role (omit for top-level)

NameTypeReqDescription
rolesarrayyesRoles to create in the hierarchy

No output schema declared.

No examples provided.

sf_create_routing_configuration ~261

Creates a Routing Configuration that defines how work items are assigned to agents. routingModel options: - LeastActive: routes to the agent with the fewest active work items - MostAvailable: routes to the agent with the most available capacity - ExternalRouting: custom routing via Apex or external system capacity: agent capacity consumed per work item (1–100) priority: routing priority (lower number = higher priority, range 1–10) unitType: Percentage or Throughput (how capacity is measured) pushTimeout: seconds before a declined/unanswered item is re-queued (optional) After creating, link it to a queue with sf_create_queue_routing_config.

NameTypeReqDescription
capacitynumberCapacity percentage or item count
configNamestringAPI name of the RoutingConfiguration
descriptionstring
labelstringyes
priorityintegerRouting priority (lower number = higher priority)
pushTimeoutintegerSeconds before push routing times out (0 = no timeout)
routingConfigNamestringAlias for configName
routingModelstring
routingPriorityintegerAlias for priority
unitTypestring

No output schema declared.

No examples provided.

sf_create_saml_sso_config ~210

Creates a SAML Single Sign-On (SSO) configuration in Salesforce via the Metadata API. Provide the identity provider issuer URL, base64-encoded IdP certificate, login URL, and user identity mapping settings. Supports username, federation ID, and user ID identity types. Used to enable SAML 2.0 federation with external identity providers.

NameTypeReqDescription
attributeNamestringSAML attribute name (for Attribute identity location)
identityLocationstringWhere user identity is stored
identityProviderCertificatestringyesBase64-encoded IdP certificate
identityTypestringUser identity type
issuerstringyesIdentity provider issuer URL
loginUrlstringyesIdentity provider login URL
logoutUrlstringIdentity provider logout URL
namestringyesSSO configuration API name
requestSignatureMethodstringSignature method
samlVersionstringSAML version

No output schema declared.

No examples provided.

sf_create_sandbox ~138

Creates a new sandbox org via the Tooling API (SandboxInfo object). Supports Developer, Developer Pro, Partial Copy, and Full sandbox types. Optionally specify an Apex class to run after the sandbox copy completes. The sandbox creation is asynchronous — use sf_list_sandboxes to monitor the status.

NameTypeReqDescription
apexClassIdstringApex class ID to run after sandbox copy
autoActivatebooleanAutomatically activate the sandbox after creation
descriptionstringDescription
licenseTypestringyesSandbox license type
sandboxNamestringyesSandbox name (max 10 chars, alphanumeric)

No output schema declared.

No examples provided.

sf_create_scheduled_flow ~173

Creates a Schedule-Triggered Flow that runs automatically on a recurring schedule (e.g., daily, weekly) against a batch of matching records. Use for nightly batch processing, periodic data updates, or scheduled notifications. fullName: Flow API name label: Flow display label objectApiName: object whose records to process scheduledPaths: array defining when the flow runs (offsetNumber, offsetUnit, timeSource) description: optional description

NameTypeReqDescription
descriptionstringFlow description
fullNamestringyesFlow API name, e.g. 'Nightly_Account_Update'
labelstringyesFlow display label
objectApiNamestringyesObject API name to process records from, e.g. 'Account'
scheduledPathsarrayyesScheduled path definitions

No output schema declared.

No examples provided.

sf_create_scheduled_job ~138

Schedules an Apex class that implements the Schedulable interface to run on a cron schedule. Use for batch processing, nightly data cleanup, report generation, or any periodic automation. The Apex class must already exist in the org. Example cron: '0 0 2 * * ?' = daily at 2 AM.

NameTypeReqDescription
classNamestringyesApex class that implements Schedulable interface
cronExpressionstringyesCron expression, e.g. '0 0 2 * * ?' for daily at 2 AM
jobNamestringyesName for the scheduled job

No output schema declared.

No examples provided.

sf_create_scratch_org ~148

Creates a Salesforce scratch org using the SF CLI. Scratch orgs are temporary, configurable environments for development and testing. Requires a Dev Hub org to be authorized. definitionFile: path to project-scratch-def.json (optional, defaults to CLI default) alias: alias for the scratch org duration: number of days before expiry (1–30) devHubAlias: Dev Hub org alias

NameTypeReqDescription
aliasstringAlias for the scratch org
definitionFilestringPath to project-scratch-def.json (optional)
devHubAliasstringDev Hub org alias
durationintegerScratch org duration in days (1-30)

No output schema declared.

No examples provided.

sf_create_search_layout ~202

Creates or updates a SearchLayout for a Salesforce object, defining which fields appear in search results, lookup dialogs, and lookup filter fields. Use to customize what columns users see when they search for records or open a lookup dialog. objectName: the API name of the object, e.g. 'Account' or 'Invoice__c' searchResultsAdditionalFields: field API names to show as columns in global search results lookupDialogsAdditionalFields: field API names to show in lookup dialog results lookupFilterFields: field API names used as filterable columns in lookups

NameTypeReqDescription
lookupDialogsAdditionalFieldsarrayField API names to show in lookup dialogs
lookupFilterFieldsarrayField API names used as filter fields in lookup
objectNamestringyesObject API name, e.g. 'Account' or 'Invoice__c'
searchResultsAdditionalFieldsarrayField API names to show in search results

No output schema declared.

No examples provided.

sf_create_service_channel ~193

Creates an OmniChannel Service Channel that connects work items from a Salesforce object to the OmniChannel routing engine. channelType options: Case, Chat, Messaging, Voice, Email, SocialPost, Custom relatedObjectApiName: the Salesforce object this channel routes (e.g. "Case", "LiveChatTranscript", "MessagingSession"). Required for Custom type. capacity: maximum number of simultaneous work items an agent can handle on this channel (default 1). Service Channels are referenced by Routing Configurations and Presence Configurations.

NameTypeReqDescription
capacityintegerCapacity weight for this channel
channelNamestringyesAPI name / DeveloperName of the Service Channel
channelTypestring
labelstringyes
relatedObjectstringAlias for relatedObjectApiName
relatedObjectApiNamestringSObject routed via this channel, default 'Case'

No output schema declared.

No examples provided.

sf_create_service_territory ~169

Creates a Service Territory for Field Service Lightning. Territories define the geographic areas or organizational divisions where field service resources operate. isActive: set true to make the territory immediately available for scheduling operatingHoursName: API name of an existing OperatingHours record to set business hours Address fields (street, city, state, country, postalCode): optional location for the territory center

NameTypeReqDescription
citystring
countrystring
isActiveboolean
labelstringyes
operatingHoursNamestringName of the OperatingHours record to link
postalCodestring
statestring
streetstring
territoryNamestringyesName of the Service Territory

No output schema declared.

No examples provided.

sf_create_sharing_rule ~186

Creates a Sharing Rule for a Salesforce object. Sharing Rules extend the OWD by automatically sharing records with users who meet criteria (criteria-based) or who own records (ownership-based). Use to give specific roles/groups access to records they wouldn't normally see based on OWD.

NameTypeReqDescription
accessLevelstringAccess level granted
criteriaItemsarrayFor criteria-based rules: conditions that trigger sharing
labelstringyesDisplay label
objectNamestringyesObject API name, e.g. 'Account', 'Opportunity'
ruleNamestringyesSharing rule developer name
ruleTypestringcriteria: share based on field values. ownership: share based on record owner.
sharedFromobjectFor ownership-based rules: whose records are shared
sharedToobjectyesWho receives the sharing

No output schema declared.

No examples provided.

sf_create_skill ~101

Creates a Skill that can be assigned to service agents. Skills are used for: - OmniChannel skill-based routing (route work to agents with required skills) - Field Service Lightning (assign skills to resources, skills to work types) After creating a skill, assign it to agents with sf_assign_skill_to_agent.

NameTypeReqDescription
descriptionstring
labelstringyes
skillNamestringyesDeveloperName / API name of the skill

No output schema declared.

No examples provided.

sf_create_static_resource ~165

Creates a Static Resource from text/JSON/JS/CSS content. Static Resources are files stored in Salesforce and served via a CDN URL — ideal for JavaScript libraries, CSS stylesheets, JSON configuration, or any other file that needs to be served from Salesforce. Content is provided as a string and deployed via the Metadata API.

NameTypeReqDescription
cacheControlstringCache control setting
contentstringyesThe file content as a string (text, JSON, JS, CSS, etc.)
contentTypestringMIME type, e.g. 'application/json', 'text/css', 'application/javascript'
descriptionstringDescription of this resource
fullNamestringyesStatic resource API name, e.g. 'MyLibrary'

No output schema declared.

No examples provided.