Registers and configures MCP servers as Salesforce Agentforce action types, including auth, rate limits, tool discovery, prebuilt servers (DX, Heroku, MuleSoft), and Apex integration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/salesforce-claude-code:sf-agentforce-mcp-actionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
How to use Model Context Protocol (MCP) servers as Agentforce action types. For building MCP servers, see `mcp-server-patterns`.
How to use Model Context Protocol (MCP) servers as Agentforce action types. For building MCP servers, see mcp-server-patterns.
MCP exposes external tools to Agentforce via JSON-RPC 2.0 over HTTP/SSE. An MCP server declares tools (with names, descriptions, parameters, return types), and Agentforce discovers them at connection time. Each tool becomes an available agent action.
Setup > MCP Servers > New MCP Server
| Field | Value |
|---|---|
| Name | Descriptive name (e.g., "Weather API") |
| Endpoint URL | Server URL (HTTPS required for production) |
| Auth | OAuth 2.0 with Integration User |
| Transport | HTTP/SSE (standard) |
After registration, tools appear in Agentforce Asset Library and can be added to topics.
In Agent Script, MCP tools are referenced like any other action. The target: field is not needed — MCP tools are auto-discovered from the server's tool manifest.
topic weather:
actions:
get_weather:
description: "Get current weather for a city"
inputs:
city: string
description: "City name"
is_required: True
outputs:
temperature: number
description: "Temperature in Fahrenheit"
is_displayable: True
reasoning:
actions:
weather: @actions.get_weather
with city = ...
Setup > Agentforce > Agent Assets > Add Action > select MCP tool from Asset Library.
| Limit | Value |
|---|---|
| Requests per minute per server | ~50 |
| Timeout per tool call | 120 seconds (matches agent timeout) |
| Max payload size | Platform-dependent |
On connection, the MCP server returns its tool manifest:
{
"tools": [
{
"name": "get_weather",
"description": "Get current weather conditions",
"inputSchema": {
"type": "object",
"properties": {
"city": { "type": "string", "description": "City name" }
},
"required": ["city"]
}
}
]
}
Agentforce uses tool names and descriptions for LLM routing — keep them clear and specific.
| Server | Purpose | Setup |
|---|---|---|
| Salesforce DX MCP Server | Deploy, test, manage scratch orgs from AI assistants | @salesforce/mcp npm package |
| Heroku Platform | Manage Heroku apps, dynos, add-ons | Built-in connector |
| MuleSoft | API orchestration, integration flows | MuleSoft Anypoint connector |
Fully managed cloud endpoints — zero infrastructure. Pre-built for core CRM and B2C Commerce APIs.
If an MCP action fails in Agent Script:
sf mcp test or direct HTTP to verify the server respondsmcp-server-patterns — building MCP servers (Node SDK)sf-agentforce-development — Agent Script patternsnpx claudepluginhub jiten-singh-shahi/salesforce-claude-code --plugin salesforce-claude-codeDiscovers zero-setup hosted MCP servers (Supabase, Vercel, Sentry, Stripe, Linear, Slack, Greptile) and provides connection URLs for immediate use in any MCP client.
Guides building MCP servers to integrate external APIs/services using Python FastMCP or Node/TypeScript MCP SDK. Covers Microsoft ecosystem, server types, and custom development workflow.
Searches, installs, configures, updates, and removes MCP servers across many coding agents (Claude Code, VS Code, Cursor, etc.). Supports npx add-mcp, the official registry, and direct config editing.