tmlc.
in
MCP Simplified
The USB-C for AI Integrations
Plug & Play for Language Models
[Link]
[Link]
Model Context Protocol
Model Context Protocol is a standardized protocol to connect LLMs to
external tools, data, and actions.
The Model Context Protocol (MCP) is a new open standard that bridges AI systems
with the external world — files, APIs, tools, databases, and services.
Think of it like a USB-C port for AI — one unified connector to plug into anything
your model needs, dynamically and securely.
No more brittle, custom code or one-off APIs. With MCP, AI becomes truly context-
aware.
[Link]
Manual code for every tool (Google Drive, SQL,
Custom API
etc.). Each had its own auth, format, and
Integrations
quirks.
How AI Language Model Standardized, but platform-locked and one-
accessed Plugins (e.g., OpenAI) way (model → API).
Tools Agent Frameworks
(e.g., LangChain
LLMs used custom-wired tools. Devs had to set
up everything.
before
Tools)
MCP RAG & Vector DBs
Gave static text as context — no actions or
real-time queries.
[Link] The growing need for agent
orchestration
The explosion of context-hungry
The Rise of
LLM applications
Over 1,000+ community-built
MCP servers in just a few months
Although announced by Anthropic
Backing from industry players like
in Nov 2024, MCP began gaining Zed, Replit, Sourcegraph
traction only in early 2025 due to
MCP is now poised to standardize how
AI systems plug into the real world.
[Link]
Why MCP Matters ?
Connecting AI to real-world data meant
building manual, one-off API
integrations — often fragile, complex,
and limited to pulling static data.
This approach made AI agents hard to
scale and tightly tied to specific
environments.
MCP simplifies this with a dynamic,
standardized, and two-way protocol,
letting AI access tools and data in real
time — more flexibly and scalably.
Source: [Link]
[Link]
The Core MCP Architecture
Local/Remote
MCP Host MCP Client MCP Server
Sources
AI Interface Smart Connector Context Provider Data Source
Acts as the AI interface Protocol clients that Provides access to These are the actual data
that initiates context maintain 1:1 connections external tools or data, like locations — on your
requests (e.g., Claude with servers APIs, files, or services. computer or hosted online.
Desktop, AI IDEs).
It routes messages Think of it as a modular The MCP Server retrieves
It’s the brain that drives between the host and the plugin the AI can interact data from here and serves
interactions with tools available context with directly. it to the client.
through the MCP providers.
ecosystem.
[Link]
The Core MCP Architecture
[Link]
How MCP Actually Works
1. MCP Host as Central Hub: The MCP Host (typically on your computer) acts as the
central point for communication.
2. Communication via MCP Protocol: The MCP Host communicates with multiple
MCP Servers using the MCP Protocol.
3. MCP Servers as Data Source Intermediaries: Each MCP Server then interacts with
a specific data source, such as a local database or a web API connected to a
remote database.
4. Data Retrieval: The MCP Servers facilitate the retrieval and potentially the
manipulation of data from those data sources.
[Link]
How Messages Travel in MCP
MCP uses JSON-RPC 2.0 as its wire format.
This means every request and response between clients and servers is
structured in a standardized JSON format.
The transport layer (like HTTP, WebSocket, etc.) handles converting MCP
protocol messages into JSON-RPC format for transmission.
On receiving a message, the transport converts it back to MCP for the AI
agent to understand and respond.
[Link]
MCP enables live, bidirectional
communication between AI agents and
tools.
Instead of one-off API calls, agents can:
a. Send requests
Two-Way
b. Receive structured replies
c. Follow up dynamically — just like a
conversation
Communication It supports ongoing sessions, not just static
retrievals.
in MCP
[Link]
Feature APIs MCP
Integration Manual Dynamic
Communication One-way Two-way
MCP vs Tool Discovery Static Real-time
Traditional Auth Varies per API Unified
APIs Maintenance Complex Simplified
[Link]
MCP in Agentic Workflows
Agentic AI isn’t just about smarter models — it’s about smarter workflows.
MCP enables models to:
Understand their environment
Perform multi-step tasks using real-time context
Collaborate with tools dynamically (even update your docs or codebase!)
It’s the missing context bridge between LLMs and the real world.
Ideal:
[Link]
When building context-rich AI agents
If your model needs access to files, APIs, or
tools dynamically
For creating reusable, scalable integrations
across apps
When Avoid:
If you only need tight, deterministic, low-
Should You latency control
For applications requiring locked-down
environments
Use MCP?
[Link]
More pre-built connectors
(MCP servers)
Frameworks for
orchestration adoption
What Comes
(like CrewAI, LangGraph)
Next? Better UI tools for developers
and users
(Visual, friendly interfaces)
[Link]
FOLLOW & CONNECT
TMLC Academy
[Link]
Let’s build the The Machine Learning Company
future of AI
[Link]
together ! LinkedIn
The Machine Learning Company