Shadowing Practice: MCP vs API: The protocol every developer needs to know - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
143 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
If you've ever built an app that talks to an AI model, MCP changes everything.
2
Because the way AI connects to your tools, data, and systems is being completely rewritten.
3
For years, APIs used to be the glue that held everything together.
4
But now there's a new standard rising fast and that something is called the Model Context Protocol or MCP.
5
And it might just be the biggest shift since APIs themselves.
6
So what exactly is MCP and why are people saying it could replace the way we integrate AI with everything around it?
7
Let's break it down clearly so that by the end of this video, you'll understand how MCP actually works and how it's different from APIs
8
and why it's reshaping how we build agents and applications that use large language models.
9
For decades, API were the universal handshake between systems.
10
You define an endpoint, you sent a request, and you got a response back.
11
It's clean and predictable.
12
And for traditional software, that is perfect.
13
But when large language models enter the picture, everything changed.
14
Models don't just call one endpoint.
15
They might talk to 10 endpoints, they want to chain them together, or even interpret unstructured data.
16
and also ask follow -up questions.
17
And that means they don't just need access to a tool, they also need context.
18
But here's the problem.
19
APIs are built for programs talking to programs.
20
They are not built for models reasoning over messy, real -world data.
21
An API is like a locked cabinet.
22
You need to know exactly what drawer to open
23
and what shape the key is but a model is trying to understand what's inside the cabinet without clear labels.
24
So it doesn't know which function to call or which parameters to pass until you tell it.
25
And you have to hard code it sometimes and oftentimes you have to keep explaining over and over again.
26
That's where MCP comes in.
27
It was designed to make models autonomously discover
28
and use tools without the constant hand -holding that we've been doing in prompt engineering.
29
So before we dive deeper, let's define both sides clearly.
30
APIs are the traditional way software communicates.
31
They expose specific endpoints, they accept requests in structured formats like JSON, and they return predictable outputs.
32
Developers document them, secure them, and version them.
33
But they assume one thing that both sides knows exactly what to expect.
34
MCP flips that assumption.
35
Instead of the model needing to be manually thought about each endpoint,
36
MCP gives the model a standardized way to discover what a tool can do, what kind of inputs it expects,
37
and what kind of outputs it returns.
38
all through context.
39
Think of it like giving a model a live machine -readable map of your API instead of a static instruction manual.
40
Now that sounds abstract, so let's make it real.
41
Imagine you're building an AI agent that manages support tickets.
42
You give it access to Gmail, Notion, and Jira.
43
With APIs, you'd write custom code for each integration, handle issues like pagination, auth tokens,
44
error cases, rate limits, and also teach the model through long prompts, like, when you want to create a Gira ticket,
45
call this endpoint with these fields.
46
When you want to reply to an email, call Gmail with this payload.
47
But with MCP, you don't need to do any of that.
48
Each service like Gmail, Notion, Jira, exposes an MCP compatible interface.
49
The model discovers these tools automatically and understands their functions as part of its environment.
50
You don't tell it how to do it, you give it the context and it figures it out dynamically.
51
That's the core difference between APIs, which are code level contracts between two applications,
52
and MCP, which is a semantic protocol between a model and its environment.
53
So you're no longer teaching the model which endpoint to hit,
54
but you're giving it a structured description of what's available and letting it reason about which tool to use and when.
55
It's like giving the model a toolbox instead of forcing it to memorize how each tool works.
56
This shift might sound small, but it's actually massive for developers building agentic systems.
57
With APIs, the logic of what to call and when to call it lived in your app code.
58
With MCP, that logic can actually move into the model's reasoning layer itself.
59
You can now build a general purpose agent that can plug into any tool that supports the protocol.
60
without having to rewrite code for each integration.
61
That's the magic here and its standardization, the same way HTTP made websites interoperable.
62
Allowing them to share and use data with each other
63
and other systems and letting them work together to perform tasks with minimal human intervention.
64
MCP is trying to make AI environments interoperable.
65
But let's talk about what's actually happening under the hood.
66
An MCP server is a lightweight process that sits next to your service or data source.
67
It describes what it can do and what functions it exposes all using JSON schemas.
68
The model connects to this server through a standardized interface like WebSocket,
69
or HTTP and receives metadata about the available resources.
70
Once connected, the model can call these functions directly, not by guessing, but by using the metadata.
71
It knows what inputs are required and what each field means and what type of output to expect.
72
The beauty is that everything is self -describing.
73
You don't have to prompt engineer the schema or reformat responses.
74
It's all standardized.
75
Compare that to an API where every single integration is bespoke.
76
You need a developer to read the docs, map the payloads, and manually wrap the endpoints.
77
So MCP abstracts that away.
78
This means instead of building 100 custom integrations, you build one MCP interface and every compatible model can use it instantly.
79
That's why people are calling MCP the plug and play layer for AI systems.
80
Now, this doesn't mean APIs are going away.
81
APIs are still the foundation.
82
They're how your systems actually function.
83
But MCP changes how models access those APIs.
84
Think of it like this.
85
MCP doesn't replace your backend.
86
It replaces the middleware between the model and the API.
87
The MCP server acts like a translator, converting your existing APIs into a format that models can understand automatically.
88
So instead of saying MCP versus API, it's more like MCP on top of APIs.
89
This distinction is key.
90
MCP doesn't compete with APIs.
91
It actually leverages them.
92
But it changes who the client is.
93
With API, the client is another program or user.
94
With MCP, the client is the model itself.
95
And that subtle difference changes everything about how we design integrations.
96
Let's zoom out for a bit.
97
The rise of MCP is part of a bigger movement towards model -native software architecture.
98
For decades, we've built systems for humans and for code.
99
Now we're building systems for models.
100
And models don't consume REST endpoints the way code does.
101
They consume context, which includes structure descriptions, schemas, and examples.
102
They do this so that they can reason, plan and act.
103
So MCP gives them that in a standardized way.
104
That's why developers building agent frameworks are moving in this direction.
105
They're realizing that connecting a model to a world of tools isn't about a bigger context window, it's about cleaner protocols.
106
And let's be honest, it's not all magic.
107
MCP is still pretty new.
108
The biggest challenge right now is adoption.
109
For MCP to truly work, the ecosystem needs servers, clients, and tools to agree on the same standard.
110
Another huge challenge is security and control.
111
When models can directly call tools through a protocol, you need clear permission layers.
112
You don't want a model accidentally sending an email, deleting a file, or making a huge database change that it wasn't supposed to.
113
APIs handle that through authentication, keys, and rate limits.
114
MCP needs to bring those guardrails into its protocol layer, which is already happening.
115
The spec defines capabilities, scopes, and authentication methods that keep things safe but it's still early days.
116
And the final challenge is the developer mindset.
117
Most of us grew up in an API world.
118
We think in terms of endpoints and routes.
119
MCP asks us to think in terms of capabilities and context, to design systems that describe what they can do, not just how to do it.
120
That's a huge paradigm shift, but it's worth learning early.
121
Here's where it all comes together.
122
Think about the moment when HTTP unified the internet.
123
Before that, every service had its own protocol, from FTP, Gopher, Telnet, which are all different internet protocols.
124
Once the web standardized on HTTP, suddenly everything became interoperable.
125
MCP is doing the same thing for AI agents.
126
Instead of each company inventing its own plugin format or integration layer,
127
MCP provides a single open protocol that any model can understand.
128
You build your ConnectShare once and any compliant model can use it.
129
That means the future of AI tools will look less like custom integrations and more like a shared ecosystem.
130
You will have an MCP server for your product, and any AI like Gemini, Claude, GPT can use it instantly.
131
That's the world we're heading towards.
132
One where models, not just humans, become first -class users of software.
133
So to sum it all up, APIs are not dead.
134
They are just evolving.
135
APIs were made for deterministic systems one program asking another for data.
136
And MCP is made for probabilistic systems, a model reasoning about what it can do.
137
So the next time someone says MCP versus API, Just remember, it's not a direct comparison.
138
It's a foundation being rebuilt.
139
MCP sits one layer above APIs and turning them from static routes into living interfaces that models can actually reason about.
140
And as more frameworks adopt it, you'll start seeing a new pattern emerge.
141
Instead of hard -coded integrations, we'll build model -aware systems where context tools and reasoning can all live in harmony.
142
I hope this video was helpful in explaining the differences between MCPs and APIs.
143
To learn more about the model context protocol at a deeper level, check out this next video.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
FOR YOU
המלץ על סרטון
C12
61 משפטים
MCP Just Got a Whole Lot Better
Business EnglishUniversity StudentsWorking Adults
C12
241 משפטים
AI Concepts Every Product Manager Should Know in 25 Minutes | Crash Course
Business EnglishUniversity StudentsWorking Adults
C112
25 משפטים
Introducing the Agents API
Business EnglishUniversity StudentsWorking Adults
C12
51 משפטים
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C11
180 משפטים
Your API Can’t Handle Real-World Integrations
Business EnglishUniversity StudentsWorking Adults
C13
108 משפטים
Jensen Huang & Satya Nadella on unmetered intelligence | Microsoft Build 2026
Business EnglishUniversity StudentsWorking Adults
C13
57 משפטים
Meta's new model wants "deep access" to your personal life...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C16
49 משפטים
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C1117 משפטים
I've Changed My Opinion On DEVELOPERS Vibe Coding
Business EnglishUniversity StudentsWorking Adults
C14
78 משפטים
Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded
Business EnglishUniversity StudentsWorking Adults
C12
144 משפטים
WWDC26: Run local agentic AI on the Mac using MLX | Apple
Business EnglishUniversity StudentsWorking Adults
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “MCP vs API: The protocol every developer needs to know”. המילים שחוזרות הכי הרבה: Mcp, model, Api, tool, systems. בסרטון הזה יש 143 משפטים ו-1697 מילים לתרגול Shadowing. הדיבור נמשך 12:19. הדובר שומר על קצב יציב של כ-138 מילים בדקה, קצב נוח לתרגול Shadowing. רק 78% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר.
אוצר מילים מרכזי בסרטון הזה
15 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| consume פועל | /kənˈsum/ | צרך |
| compatible שם תואר | /kəmˈpæt.ə.bəl/ | תואם, מתאים |
| handshake שם עצם | /ˈhæn(d)ˌʃeɪk/ | לְחִיצַת יָד |
| memorize פועל | /ˈmɛm.əˌɹaɪ̯z/ | שִׁנֵּן |
| paradigm שם עצם | /ˈpæɹ.ə.daɪm/ | פָּרָדִיגְמָה |
| translator שם עצם | /ˈtɹænzleɪtɚ/ | מְתַרְגֵּם, מְתַרְגֶּמֶת |
| authorization שם עצם | /ˌɔːθəɹaɪˈzeɪʃən/ | הַסְמָכָה |
| drawer שם עצם | /dɹɔɹ/ | מגירה, מְגֵרָה |
| glue שם עצם | /ɡlu/ | דֶבֶק |
| interpret פועל | /ɪnˈtɜː.pɹɪt/ | דּוֹבֵב |
| token שם עצם | /ˈtoʊkən/ | אֲסִימוֹן, זִ׳יטוֹן |
| messy שם תואר | /ˈmɛsi/ | חסר סדר, מבולגן |
| leverage שם עצם | /ˈlɛv.(ə.)ɹɪd͡ʒ/ | הנפה |
| emerge פועל | /ɪˈmɝd͡ʒ/ | צץ, התגלה |
| assumption שם עצם | /əˈsʌm(p).ʃ(ə)n/ | השערה hash'ará, הנחה hanakhá |
Phrasal verbs שתשמעו
| מילה | משמעות |
|---|---|
| check out פועל | בדק |
משפטים שכדאי לחזור עליהם
משפטים קצרים ושלמים מהסרטון שאפשר להשתמש בהם בשיחה יומיומית:
- They're how your systems actually function.
- MCP doesn't replace your backend.
- Let's zoom out for a bit.
- That's the world we're heading towards.
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | being completely rewritten · is called · are built |
| משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר | APIs, which are · MCP, which is · layer, which is |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | you've ever built · we've built |
הגייה ששווה לשים לב אליה
הדובר משתמש ב-27 קיצורים וצורות מקוצרות, כמו don't, doesn't, you're. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.
- הצלילים של “th”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- הצלילים של “sh” ו-“zh”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, handshake /ˈhæn(d)ˌʃeɪk/, pagination /ˌpæd͡ʒəˈneɪʃən/, reshape /ɹiːˈʃeɪ̯p/, standardization /ˌstæn.də.daɪˈzeɪ.ʃən/
- מילים ארוכות — שימו לב להטעמה: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, metadata /ˈmɛt.əˌdeɪ.tə/, manually /ˈmænj(u)əliː/, predictable /pɹəˈdɪktəbləl/, ecosystem /ˈikoʊˌsɪstəm/
צלילים שדוברי עברית מתקשים בהם:
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: manually /ˈmænj(u)əliː/, compatible /kəmˈpæt.ə.bəl/, static /ˈstæt.ɪk/, handshake /ˈhæn(d)ˌʃeɪk/, pagination /ˌpæd͡ʒəˈneɪʃən/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: prompt /pɹɑmpt/, rewrite /ɹiˈɹaɪt/, predictable /pɹəˈdɪktəbləl/, guardrail /ˈɡɑɹdˌɹeɪl/, memorize /ˈmɛm.əˌɹaɪ̯z/
- עיצור קולי בסוף מילה — /b/, /d/, /g/, /z/, /v/ בלי להפוך אותם לאטומים: expose /ɪkˈspoʊz/, payload /ˈpeɪloʊd/, memorize /ˈmɛm.əˌɹaɪ̯z/, oftentimes /ˈɔf.ənˌtaɪmz/, evolve /ɪˈvɑlv/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- תרגלו Shadowing משפט אחר משפט במהירות רגילה, וחזרו על כל משפט עד שהקצב שלכם תואם את הדובר.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו consume, compatible, handshake.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.