--- schema_version: "1" id: 22f1634a2c6496b9a3ad89e10a3161651bf0d01f4d67bcde2bee7b6962c20382 title: Agentforce Vibes MCP Tools collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/einsteinfordevs/guides/files/devagent-mcp.md canonical_url: https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/devagent-mcp.html source_site: developer.salesforce.com content_type: documentation content_hash: 016885fa191ea8831746340ab9fbd4937af8fd47be575179391710a65c3dbf32 products: - Agentforce Vibes Developer Guide (Deprecated) - salesforcedx --- # Agentforce Vibes MCP Tools Model Context Protocol (MCP) is the foundational technology that enables Agentforce's agentic capabilities. MCP transforms how AI agents interact with development tools by providing a standardized interface for tool discovery, execution, and results integration. Understanding MCP helps you leverage Agentforce's full potential and troubleshoot issues when they arise. MCP serves as a universal translator between AI models and development tools. Just as USB provides a standard way to connect different devices to your computer, MCP provides a standard way for AI agents to connect with various development tools and services. Here's how MCP works in Agentforce: 1. **Tool Discovery**: Agentforce discovers the tools that are available in your environment. 2. **Intelligent Selection**: When you make a request, Agentforce determines which tools are needed. 3. **Execution**: Agentforce executes the appropriate tools in the right sequence. 4. **Results Integration**: Tool results are integrated into a coherent response. ## Benefits of using MCP The integration of MCP brings several key benefits. It provides a standardized interface for accessing all development tools and services, while also enabling dynamic discovery of the tools available in your environment. MCP is also context-aware, integrating deeply with your project structure and org metadata to deliver more relevant results. ## Salesforce-Specific Tooling The out-of-the-box [Salesforce DX MCP Server](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm#a4d-includes-dxserver) included with Agentforce Vibes is designed specifically for Salesforce development workflows. It provides several key benefits: - **Accurate Context**: Tools understand Salesforce metadata, org structure, and development patterns. - **Secure Integration**: All tools operate within Salesforce's trusted security boundary. Developers can work confidently without compromising safety. - **Optimized Workflows**: Tools ‌are designed for common Salesforce development tasks. - **Consistent Experience**: All tools follow Salesforce conventions and best practices. ### Enable Salesforce DX MCP Server To enable the Salesforce DX MCP Server: 1. **Click Vibes Icon**: Look for the Agentforce Vibes icon ([![agentforce](https://developer.salesforce.com/media/einsteinfordevs/vibecodey_icon.png)]) in the Activity Bar. 2. **Switch to Act Mode** - In the chat interface, locate the mode selector. - Switch from standard chat, and toggle from **Plan** to **Act mode**. See [Agentforce Plan and Act Modes](https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/devagent-planact.md). 3. **Enable MCP Servers** Click **"Enable MCP Servers"** to install and enable the **Salesforce DX** server. Toggle **Salesforce DX** MCP server on. The **Salesforce DX** MCP server is installed and enabled by default in Code Builder. ### Verify MCP Server Status Check that your MCP server is connected: - 🟢 **Green indicator**: Server connected and functioning. - 🟡 **Yellow indicator**: Connection in progress. - 🔴 **Red indicator**: Connection failed (requires troubleshooting). If you're working with more than one MCP server, control which servers are active by clicking the server icon, opening Manage MCP Servers, and then toggling servers off and on. **note:** For local VS Code users, MCP servers are disabled by default. To use them you must explicitly enable them. ### Test Basic Functionality Try these prompts to verify your setup: 1. **Test Org Connection** ``` User: "Show me my authorized orgs". Expected: List of your connected Salesforce orgs. ``` 2. **Test Tool Execution** ``` User: "Run a simple Apex test". Expected: Agentforce proposes and executes test command on an Apex file. ``` 3. **Test Project Context** ``` User: "What Lightning Web Components are in my project?". Expected: List of your project's LWC components. ``` ### Tool Activation in the Salesforce DX MCP Server 1. To open the `a4d_mcp_settings.json` file, click settings in the MCP tools panel and then click **Configure MCP Servers**. 2. To configure the Salesforce DX MCP server with a customized set of tools, add or remove tools using the `--toolsets` or `--tools` flags. 3. Save the file. The default `a4d_mcp_settings.json` for Agentforce Vibes is - ```json { "mcpServers": { "https://github.com/salesforcecli/mcp": { "disabled": false, "timeout": 600, "type": "stdio", "command": "node", "args": [ "/Users/user/Library/Application Support/Code/User/globalStorage/salesforce.salesforcedx-einstein-gpt/MCP/a4d-mcp-wrapper.js", "@salesforce/mcp@latest", "--orgs", "ALLOW_ALL_ORGS", "--toolsets", "metadata", "--tools", "get_username,run_apex_test,run_soql_query,guide_lwc_development,orchestrate_lwc_component_creation,guide_lwc_accessibility,create_lwc_component_from_prd,assign_permission_set,list_all_orgs,list_devops_center_projects,list_devops_center_work_items,create_devops_center_pull_request,promote_devops_center_work_item,commit_devops_center_work_item,check_devops_center_commit_status,checkout_devops_center_work_item,run_code_analyzer,describe_code_analyzer_rule,detect_devops_center_merge_conflict,resolve_devops_center_merge_conflict" ] } } } ``` ## Limitations Be aware of these current MCP limitations. - **Server Dependencies**: MCP functionality depends on properly-configured servers. - **Server Installs**: Installing MCP servers from the third-party Marketplace (not supported by Salesforce) depends on the LLM interpreting the server’s GitHub README, which is non-deterministic and token-heavy. We recommend adding the configuration directly to the `a4d_mcp_settings.json` file instead. - There's roughly a 20 tool limit on the number of tools you can run at the same time. Edit the json file to select the right tools for your workflow. For the [Salesforce DX MCP Server](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm#a4d-includes-dxserver), you can select tools you want to run. Other MCP servers can be turned off to reduce the tool burden. ## See Also [Salesforce DX MCP Server and Tools (Beta)](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm) [Agentforce Vibes Troubleshooting](https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/einstein-troubleshoot.html)