Lesson 40 of 41 · All lessons
Salesforce Agentforce Specialist
0 of 41 complete
1Exam Overview
  1. 1.1Agentforce Specialist Complete Exam Overview
2Prompt Engineering20%
  1. 2.1When to Use Prompt Builder
  2. 2.2Prompt Template Access Controls
  3. 2.3Field Generation and Flex Prompt Template Types
  4. 2.4Grounding Techniques for Prompt Templates
  5. 2.5Creating, Activating, and Executing Prompt Templates
  6. 2.6Best Practices for Writing Effective Prompts
  7. 2.7Trust Layer Security and Privacy Features
  8. 2.8Managing and Preventing Specific Models from Being Accessed
3Data 360 Fundamentals20%
  1. 3.1Agentforce Data Library
  2. 3.2Data 360 Concepts for Agentforce
  3. 3.3Chunking
  4. 3.4Indexing
  5. 3.5Retrievers
  6. 3.6Choosing a Grounding Approach for a Scenario
4AI Agents35%
  1. 4.1How an Agentforce Agent Works
  2. 4.2Agent Building Blocks and Agent Script
  3. 4.3Hybrid Reasoning and Deterministic Behavior
  4. 4.4Agentforce Builder: Canvas and Script Views
  5. 4.5Filters, Variables, and Template Expressions
  6. 4.6Standard and Custom Topics
  7. 4.7Standard and Custom Agent Actions
  8. 4.8Configure Topics, Instructions, and Actions for a Use Case
  9. 4.9Connecting Agents to Digital Experience, Email, Voice, and Slack
  10. 4.10Agent Security Context and Action Execution
  11. 4.11Choosing Between Employee and Service Agents
  12. 4.12When to Use Agent API
5Testing, Deployment, and Maintenance10%
  1. 5.1Testing Agents with Testing Center
  2. 5.2Understanding Testing Center Evaluations
  3. 5.3Deploying Agents from Sandbox to Production
  4. 5.4Deploying Prompt Templates Between Environments
  5. 5.5Reviewing Agent Behavior After Changes
6Governance and Observability10%
  1. 6.1Managing and Monitoring Agents
  2. 6.2Agent Analytics and Performance Signals
  3. 6.3Identifying Opportunities to Optimize Agent Behavior
  4. 6.4Using Observations to Guide Improvements
7Multi-Agent Orchestration5%
  1. 7.1Choosing a Multi-Agent Architecture
  2. 7.2Orchestrators and Connected Subagents
  3. 7.3Handoff and Supervisor Modes
  4. 7.4Model Context Protocol (MCP)
  5. 7.5Agent-to-Agent (A2A) Communication

Section 7 · Multi-Agent Orchestration · 5% of exam

7.4 Model Context Protocol (MCP)

3 min read Updated Nov 16, 2026

Exam objective

Explain how MCP standardizes an agent’s access to tools and data in external systems and how it differs from agent orchestration.

MCP connects agents with external capabilities

Model Context Protocol is an open standard for connecting AI applications with external systems and their capabilities. In a typical MCP arrangement, a server makes capabilities available, a client connects to the server, and a host coordinates the client experience. MCP servers can define tools, prompts, and resources at the protocol level. In Salesforce’s current Agentforce MCP integration, agents use MCP tools: executable functions exposed by a server and added to an agent as actions. These actions let an agent access an external capability through a standardized connection rather than requiring a separate custom integration for every tool.

Map the pattern to a business request

Suppose an agent needs a risk score from an external service. The service exposes an MCP tool, Agentforce connects to the MCP server, and the agent can invoke the tool when the request and instructions call for it. The tool performs the defined operation and returns structured data for the agent to use. Salesforce’s setup flow depends on the server source: third-party servers use the Agentforce Registry, while Salesforce-hosted and MuleSoft servers use API Catalog workflows. Administrators allowlist the individual tools that agents may use, then add the desired tool actions to the agent.

Distinguish MCP from multi-agent design

MCP is primarily a standardized way for an agent to use tools or data provided by a server. It does not, by itself, decide which specialist agent should own a conversation or how an orchestrator should combine delegated results. That is an architecture and routing decision. An agent can use MCP tools while remaining a single agent; a multi-agent design can delegate among specialists without MCP. Some solutions may use both: the coordinator chooses a specialist, and that specialist calls an external tool through MCP. On an exam, identify whether the requirement is tool interoperability or agent-to-agent collaboration.

Include governance and deployment checks

A protocol does not remove the need for security review. Confirm the server identity, authentication, tool allowlist, data returned, and action permissions. Test the tool in Agentforce Builder and Testing Center, and inspect traces when an action is missing or out of sync. Salesforce notes that MCP server registration metadata is not packaged with deployed agents, so target environments need their server registrations and allowlisted tools configured before the agent can use them. Validate the connection and tool behavior in each environment, and review changes to server definitions before activation.

If the requirement is “call an external tool or service,” think MCP; if it is “delegate work to another agent,” think A2A or an orchestration pattern.

MCP can standardize tool access, but the connected server, authentication, available tools, and data access still require governance.

Extra concept: MCP tools can be used as agent actions. Their presence does not turn the agent architecture into a multi-agent system.

Official references:

  • MCP for Agentforce https://help.salesforce.com/s/articleView?id=ai.agent_mcp.htm&language=en_US&type=5
  • Connect Agentforce Solutions to MCP Servers https://help.salesforce.com/s/articleView?id=ai.agent_mcp_connect.htm&language=en_US&type=5
  • Considerations for MCP for Agentforce https://help.salesforce.com/s/articleView?id=ai.agent_mcp_considerations.htm&language=en_US&type=5

Key takeaways

  • MCP is an open protocol for connecting agents to server-provided capabilities; Agentforce uses MCP tools as actions.
  • Allowlist only the required tools and verify server access, authentication, data, and action behavior.
  • MCP tool interoperability and multi-agent orchestration solve different design problems.

Check your knowledge

Answer exam-style Multi-Agent Orchestration questions with answers and explanations.

Practice Multi-Agent Orchestration
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Agentforce Specialist simulator: same number of questions, same time limit.

Get Complete Access