What Is MCP? A Simple Guide To Model Context Protocol for Salesforce Admins

What Is MCP? A Simple Guide to Model Context Protocol for Salesforce Admins

By

One of the challenges of the AI revolution is simply keeping up. Technology evolves quickly: Interfaces get updated, models change in terms of performance, precision, and sometimes even tone and personality. Completely new functionality is being added to agents at a breakneck speed. For Salesforce Admins, keeping up with new concepts and terminology can definitely be a challenge, especially when new ideas are defined with acronyms or by unfamiliar technological terms.

A great example is Model Context Protocol, or MCP, a new standard designed to let agents connect with tools, services, and external applications to access data, actions and prompts. Let’s break down what that term means, how the technology works, and what it will mean for admins and their Agentforce implementations.

MCP: A new solution to an old problem

MCP is a protocol drafted by Anthropic and has emerged as the de facto standard for describing how an agent should access tools, data sources and systems. For Salesforce, this will allow Agentforce to easily access services like databases and enterprise tools. Currently this requires custom application development, but in the future it should surface in custom and standard Salesforce functionality.

Ever since computing adopted the client-server model with two very different things trying to talk to each other securely and consistently, the problem of how to make that connection work has existed. How do clients authenticate themselves? How do servers deliver information to the right location? How does the client know what kind of data to expect and respond to it correctly? Now take those questions and realize if someone creates a different kind of server or client, you have to ask them all over again and design an integration that handles different answers.

The Internet Age is full of novel ideas and protocols that solve these kinds of problems. Many application programming interfaces (APIs) include some kind of means of asking for answers to these questions directly, and even import them into client applications.

MCP provides a singular, agreed-upon way for an agent to ask a server about its functionality. With MCP, Agentforce has a universal connector to external data sources and tools.

Context is king

Sound familiar? It should if you’ve been working with any kind of AI. Artificial intelligence will always, always, always be bad at its job if it lacks context. My classic example is the phrase “I need a ticket.” On its own, it lacks the detail needed to complete a task or generate a meaningful response, especially compared to something like “I need a plane ticket from Chicago to San Francisco for Dreamforce 2025.” 

For an agent to work with an external tool, it needs to understand the context of the functionality in a way that fits into its system of topics, prompts and instructions. MCP provides a universal standard for a client to engage with an external server to receive the context needed to deliver accurate, effective results.

The working parts of MCP include:

  • Host: The agentic platform (e.g., Agentforce)
  • Client: Acts within the host to communicate with MCP servers
  • Server: Exposes data, prompts, and actions
  • Actions: Enable the agent to take actions via your server
  • Resources: Provide structured data and content access
  • Prompts: Define reusable workflows and prompt templates

What do I need to know to make it work?

This is the cool part. Honestly? About as much as you need to turn on your TV. MCP might be a technically fancy name, and has some pretty fancy technical moving parts, but for Agentforce all of that gets handled behind the scenes for you. However, once partners start listing their MCP servers on AgentExchange, you’ll be able to:

  • Discover new functionality for your agents from our partners on AgentExchange
  • Register the functionality within your organization
  • Connect agents to the functionality with Agent Builder
  • Test that everything works in Testing Center
  • Optimize the experience using upcoming tools like Command Center

Stay tuned here for updates on how the Model Context Protocol (MCP) will integrate with your agentic solutions as agent-building tools advance. 

For a more visual overview, check out this video:

Learn more from these resources

Metadata Is Your Admin Blueprint for Building Better Agents

Metadata Is Your Admin Blueprint for Building Better Agents

If the idea of Salesforce Multitenancy is important to understanding Salesforce as a platform, then the logical next step is to consider its use of metadata.  Metadata is fairly ubiquitous in the internet age. We all know it’s important to tag data and content with information and descriptions so that browsers, search engines, and, these […]

READ MORE