쉐도잉 연습: Demystifying MCP | Architect Insights - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
Hi, I'm Scott Reila, Principal Architect Evangelist at Salesforce.
2
In this episode of Architect Insights, we're going to be exploring Model Context Protocol, or MCP.
3
Often called the USBC for AI, MCP is an open standard revolutionizing how AI agents dynamically connect to external tools and data.
4
Today, we will unpack how it works, examine the architectural trade-offs, and discuss why this new protocol complements your standard APIs.
5
Let's get started.
6
Before we dive in, please note that we may be discussing some forward-looking products and features today.
7
Please make all purchasing decisions based on what is currently available.
8
There are two types of MCP interactions at Salesforce.
9
On the left side, we have Agent Force acting as a client.
10
These are Agent Force agents
11
that need to connect to other external systems to get access to information like order status or inventory availability, or even to execute tasks based on the conversation.
12
On the right side, Salesforce acts as a server.
13
In this scenario, we have external or local agents that need to be able to use Salesforce data via Headless 360.
14
We'll be touching on both sides in our discussion today.
15
But before we go any further, we need to understand exactly what the model context protocol is.
16
MCP is the new open standard for connecting AI to outside tools and data.
17
It was introduced by Anthropic in November of 2024 to solve major integration bottlenecks.
18
Traditionally, if you wanted an agent to interact with a system, you would have to build custom skills or code API or SOC will calls for every single interaction.
19
MCP changes this by providing one unified connection standard, eliminating the need for those custom agent specific builds.
20
It allows AI models to consistently discover and use external features, and because it is open source, it works seamlessly across all AI providers.
21
MCP is often called the USBC for AI.
22
Just like you no longer want to carry around separate micro USB and Lightning cables,
23
MCP means we finally have a single unified configuration protocol for all of our AI agent integrations.
24
Now that we know the what, let's talk about how MCP actually works.
25
Let's start with the component view.
26
Looking at the left side of the screen, we have our hosts.
27
These could be chat interfaces like Claude or ChatGPT, code editors like VS Code or Claude Code or Cursor, or agents like AgentForce.
28
Each of these hosts has its own LLM connection and an embedded MCP client.
29
You can think of the host and the embedded client as sitting together as one unit for now.
30
In the middle, we have the MCP server.
31
The server handles the information discovery and setup, illustrating the different tools, resources, and prompts that are available to the host.
32
There are three types of interactions the MCP server provides.
33
First, we have tools, basically any callable code like APEX, API, whatever.
34
Tools are called dynamically by the agent.
35
For example, if I ask for an order status, the agent will gravitate towards an order status tool to make that call.
36
If there's no appropriate a tool, the LLM will tell me that it can't get the information, or worse, it may actually try to hallucinate the answer.
37
Guardrails are very important here.
38
Next are resources.
39
These represent data or files, and they are fundamentally different from tools because they are not directly callable by the agent.
40
To use the resource, the user must specifically mention it in their question, such as asking for a specific order using a manual pointer like at order 123.
41
Additionally, resources can handle notifications and follow-up information, which only trigger if the underlying system explicitly tells the MCP server that the resource was updated.
42
Lastly, we have prompts.
43
These are essentially just prompt templates.
44
It is critical to note that there is no LLM interaction on the MCP server side.
45
All LLM processing happens over on the host side.
46
Now that we know the components, let's discuss initialization.
47
Anytime you add a new mcp server
48
or start your agent an initialization step occurs exposing an mcp server without security is a bad idea even
49
if the data isn't highly sensitive like a weather app for
50
instance you absolutely must protect your server from denial of service attacks
51
if someone asks an open server for the weather in every
52
single us zip code it could easily crash your mcp server the admin or user
53
if local pre-configures the api key in the headers of the
54
host mcp json config file the host initiates the connection sending a request to the remote mcp server
55
while passing those authorization headers the server then validates the key
56
and if it is a valid api key the server successfully returns the tool list
57
and capabilities for the host to store we'll talk more about storage a little bit later
58
if the key is invalid
59
or missing the server immediately rejects the call with a 401 unauthorized
60
or a 403 forbidden error this step is essential
61
because it allows the mcp server to to identify exactly who is making the call, enabling the server to enforce strict rate limiting or resource throttling.
62
Now let's talk about user authentication, which is what Salesforce uses for Headless 360.
63
This one starts off the same way, where the user or admin configures their host.
64
Looking at step one, the initial connection attempt goes from the client host to the remote MCP server.
65
However, it returns a 401 unauthorized, which prompts the host to fire up a browser and go to the token URL.
66
This takes us to step two where the user logs in through a PKCE or Pixie challenge.
67
Once the user authenticates, Salesforce uses the external app to grant your scopes and determine which MCP servers your user can access.
68
Moving down to step three, the code is exchanged for a bearer and access token.
69
The host connects the user using that bearer token, And as long as the user has the right scopes,
70
the server returns the tool list and capabilities that the user is allowed to access.
71
As you can see, this is a little bit more involved.
72
But this is exactly where we start talking about why it is so important to know who the user is.
73
Every user in Salesforce has different permissions and capabilities.
74
And in this OAuth flow, it ensures that our agent
75
and our chat client can only execute what is specifically available to
76
that user and only access the MCP servers that are enabled.
77
Now that the MCP is initialized, let's talk about the actual tool invocation.
78
Let's say a user asks a question like, what's the humidity level in Chicago?
79
Starting on step one of the diagram, the host app sends the user's prompt alongside a list of available tools stored in the host to the LLM.
80
This is a critical detail depending on how many MCP servers you have connected.
81
The first call can consume a massive amount of your context window
82
because every single associated tool is sent to the LLM with the question in context.
83
The LLM then evaluates the tool descriptions to decide which one to call.
84
Once the tool is selected, like get current weather, we move to step two.
85
The host sends the tool call request, including inferred arguments like the Chicago zip code, to the MCP server.
86
The server executes the action with the external system and then returns the raw data back to the host.
87
Finally, in step three, the host passes the original question alongside that raw tool result back to the LLM.
88
The LLM extracts the specific data, like finding the 76% humidity from a large block of data, and generates the final natural language response for the user.
89
Notice the token burn happening here.
90
We are making multiple LLM calls per interaction, consuming tokens during both the tool selection phase and the final answer generation phase,
91
which is why managing your context window is very important.
92
Now that we have an idea of what MCP call looks like, let's check out a quick demo.
93
I have an MCP server for weather connected right here.
94
When I initialize my connection, look at the list of tools that populate.
95
We have get current weather, get weather conditions, get current air quality, and so on.
96
Notice that there isn't a tool in this list that explicitly mentions humidity levels.
97
This means the LLM actually has to go through each of the tool descriptions to understand
98
which one is the best fit for our question.
99
In this case, it decides get current weather is the best call.
100
Now let's look at the contract happening under the covers.
101
You can see the tool is looking for a location parameter, like Chicago.
102
When we run this, it goes out to the external system and returns an answer, but it doesn't just return a clean 53%.
103
Look at this large blob of data right here.
104
This is the entire result set that gets passed back to the LLM.
105
If I scan through it, I can see the humidity level is 53%, buried right here.
106
In order for the LLM to give that simple answer, the LLM has to process this entire raw result set alongside the user's original question and context.
107
This is where more token burn happens.
108
You are consuming a large amount of tokens based on the
109
sizable tool result just to extract one specific data point and generate a final natural language answer.
110
For an agent interaction, this is necessary to give the exact answer.
111
Is the same level of processing and token burn needed for a system-to-system integration?
112
Based on this analysis, we need to understand each use case and determine if MCP or API should be used.
113
Let's take a look at a side-by-side comparison of why both exist.
114
Looking at the left side, APIs are built for integration.
115
They rely on programmatic code and deterministic contracts.
116
Because there is no LLM interpreting the request or response, there is zero token cost and the data structure is strict and static.
117
Now looking at the right side, MCP is built for interaction.
118
It relies on the probabilistic reasoning of an LLM, which as we saw in the demo, consumes tokens to select a tool and generate the final answer.
119
However, MCP has dynamic discovery.
120
If you add a new tool to your server, the agent knows it exists after the next initialization
121
and how to use it without you having to build out custom agent-specific integrations.
122
For AgentForce, this is slightly different because the admin has to enable each of the tools for security reasons.
123
For system-to-system integrations, APIs remain as the go-to standard due to their deterministic nature and strict processing on the client side.
124
However, if natural language processing or additional reasoning is needed, like in an agentic interaction, then MCP would be desirable.
125
Ultimately, MCP is a powerful standard that complements your APIs.
126
It does not replace them.
127
By understanding the strengths and limitations of both, you can build smarter agentic interactions while maintaining the reliability of your system to system integrations.
128
Thanks for watching and see you next time.
✨ 추천 영상
C11
143 문장
MCP vs API: The protocol every developer needs to know
University StudentsBusiness English+1
C14
78 문장
Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded
University StudentsBusiness English+1
C11
346 문장
Trust the Process: How to Design Teams That Actually Work
University StudentsBusiness English+1
C1101 문장
BGP Overview
University StudentsBusiness English+1
C11
60 문장
Course Preview | SC-100 | Microsoft Cybersecurity Architect
University StudentsBusiness English+2
C11
197 문장
Unreal Engine 5.8 - Experimental MCP Server Support Walkthrough | State of Unreal 2026
University StudentsBusiness English+1
C15
34 문장
Marketing Research Essentials Intro, Models & Intelligence
University StudentsBusiness English+1
C11
497 문장
Technical deep dive on Managed Instance for App Service | BRK102
University StudentsBusiness English+1
C13
13 문장
Robots with connected brains
University StudentsBusiness English+1
C14
321 문장
8 Tech Choices to Lock In Before Agentmaxxing
University StudentsBusiness English+1
C11
364 문장
Running AI Agents in Secure Sandboxes with E2B & Docker MCP | Docker’s AI Guide to the Galaxy
University StudentsBusiness English+1
C11
49 문장
Why Do You Need BOTH a MAC and IP Address?
University StudentsBusiness English+1
이 비디오로 영어 회화 연습을 하는 이유
비즈니스 및 기술 분야의 전문적인 컨텍스트에서 영어를 사용하는 것은 IELTS 스피킹이나 실무 회화에서 중요한 역량입니다. 이 비디오는 "Model Context Protocol(MCP)"이라는 전문 용어를 다루면서도 자연스러운 발화 패턴을 보여주기 때문에, 전문 용어와 일상적인 설명을 결합한 표현을 연습할 수 있습니다. 특히 shadow speech 기법을 사용해 발화 속도, 강세, 억양을 따라하기 좋은 내용입니다. 복잡한 개념을 간단히 설명하는 방식은 영어로 아이디어를 전달하는 능력을 키우는 데 도움이 됩니다.
문맥 속 문법과 표현
- "Often called the USBC for AI, MCP is an open standard...": "Called ~"로 시작하는 분사구문은 명사를 설명하는 데 자주 사용됩니다. 이 구조를 사용하면 긴 문장을 간결하게 만들 수 있으며, IELTS 스피킹에서 객관적인 설명을 할 때 유용합니다.
- "We'll be touching on both sides in our discussion today.": "Touch on ~"은 "간략히 다루다"는 뜻으로, 회화에서 너무 깊게 들어가지 않고 주제를 언급할 때 자연스럽게 사용됩니다. 실무 회화에서 주제의 범위를 설명할 때 유용한 표현입니다.
- "If there's no appropriate tool, the LLM will tell me that it can't get the information...": 조건문 "If ~, ~ will ~"은 가정적인 상황을 설명할 때 필수적인 구조입니다. 이 비디오에서는 기술적인 시나리오를 설명하는 데 사용되었으며, 영어 회화 연습에서 다양한 상황을 표현할 때 활용할 수 있습니다.
발음의 함정
이 비디오에는 발음이 어려운 단어와 구문이 몇 가지 있습니다. "protocol"은 [ˈproʊtəkɔːl]로 발음하지만, 흔히 [prəˈtoʊkɔːl]로 잘못 발음하는 경우가 있습니다. "bottlenecks"의 [ˈbɑːtlnek]는 "병목 현상"을 뜻하며, 't'가 약하게 발음되어 [ˈbɑːlnek]로 들릴 수 있으니 주의해야 합니다. 또한 "hallucinate"의 [həˈluːsɪneɪt]는 "환각을 보다"라는 뜻으로, 중간의 'u'가 길게 발음됩니다. shadowing site에서 이 단어들을 반복 연습하면 발음 교정에 도움이 됩니다. 특히 "MCP"와 같은 약어는 [em si pi]로 명확하게 발음해야 하며, 빠르게 말할 때 약어의 발음이 모호해지지 않도록 주의해야 합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.