MCP Servers

Model Context Protocol (MCP) is the foundational technology that enables Agentforce Vibes’ agentic capabilities. MCP provides a standardized interface for tool discovery, execution, and results integration between AI models and development tools.

MCP serves as a universal connector between the agent and your tools. Just as USB provides a standard way to connect devices to your computer, MCP provides a standard way for AI agents to connect with development tools and services.

When you interact with Agentforce Vibes, MCP handles the connection between your request and the tools that fulfill it:

  1. Tool Discovery—the agent discovers available tools in your environment.
  2. Intelligent Selection—when you make a request, the agent determines which tools it needs.
  3. Execution—the agent runs the appropriate tools in the right sequence.
  4. Results Integration—tool results combine into a coherent response.

The Toolkit tab in the Agentforce Vibes panel displays all configured MCP servers, grouped by type. Each server shows its connection status and the number of available tools.

To access the MCP Servers panel:

  1. Open the Agentforce Vibes panel.
  2. Click the Toolkit tab.
  3. Click MCP Servers.

The panel groups servers by type:

  • Salesforce Platform—servers that connect to your Salesforce orgs (Salesforce DX, Salesforce API Context).
  • Local Process—servers that run locally on your machine (GitHub, custom servers).

Each server displays its current state:

  • Connected (green)—server is functioning and shows the number of available tools.
  • Error (red)—connection failed. The panel displays the error message (for example, “Authentication failed (HTTP 401). Try reconnecting your org.”).

To add a new MCP server:

  1. Click + Add Server in the MCP Servers panel.
  2. Select a Server Type from the dropdown (for example, “Salesforce Platform”).
  3. Enter a Name for the server (for example, “Prod Org MCP”).
  4. Enter the URL for the server (for example, https://your-instance.salesforce.com).
  5. Click Add Server.

To configure the server using JSON directly, click Switch to JSON in the top-right corner of the Add MCP Server form.

Click a server to open its detail view. Use the toggle in the top-right corner to enable or disable the server without removing its configuration.

Salesforce Platform servers appear under the “Salesforce Platform” group in the MCP Servers panel. These servers connect to your Salesforce orgs and provide tools for development, metadata operations, and org management.

The Salesforce DX MCP Server ships with Agentforce Vibes and provides CLI tools for Salesforce development, testing, and deployment.

  • Accurate Context—tools understand Salesforce metadata, org structure, and development patterns.
  • Secure Integration—all tools operate within Salesforce’s trusted security boundary.
  • Optimized Workflows—tools handle common Salesforce development tasks.
  • Consistent Experience—all tools follow Salesforce conventions.

The Salesforce DX server is installed and enabled by default in Code Builder. For local VS Code users, enable it through the Toolkit tab.

Verify that the Salesforce DX server is working by trying these prompts:

  • “Show me my authorized orgs”—confirms org connection.
  • “Run a simple Apex test”—confirms tool execution.
  • “What Lightning Web Components are in my project?”—confirms project context.

Salesforce hosted MCP servers connect the agent to remote Salesforce capabilities without relying on local MCP services. They appear in the “Salesforce Platform” group alongside Salesforce DX.

Prerequisites: Your admin must enable hosted MCP servers in your org before they appear available. See Create an External Client App for admin setup instructions.

Available hosted servers include:

  • Salesforce API Context—provides the agent with access to your org’s metadata schema, object definitions, and API descriptions. Helps the agent generate more accurate code by understanding your org’s specific configuration.
  • Metadata Experts - provides the execute_metadata_action tool, which handles core business logic for registered metadata types.

You can add MCP servers beyond the Salesforce-provided ones. Use the + Add Server button for servers that support the standard MCP protocol, or add configuration directly to mcp.json for more control.

Adding configuration directly to the JSON file is recommended over marketplace installation. Marketplace installs depend on the LLM interpreting the server’s GitHub README, which is nondeterministic and token-heavy.

  • Tool limit—approximately 20 tools can run simultaneously. Select the tools that match your workflow and turn off servers you aren’t using to reduce the tool burden.
  • Server dependencies—MCP functionality depends on properly configured servers. Check connection status in the Toolkit panel if tools aren’t responding.
  • Authentication errors—if a server shows an authentication error (HTTP 401), try reconnecting your org through the Salesforce CLI or refreshing your credentials.
  • Admin enablement required—Salesforce hosted MCP servers require your admin to enable them in the org before you can connect.