MCP is like a USB-C port for your AI applications.
Just as USB-C offers a standardized way to connect devices to various accessories, MCP standardizes how your AI apps connect to different data sources and tools.
Let's dive in! 🚀
At its core, MCP follows a client-server architecture where a host application can connect to multiple servers.
Key components include:
- Host
- Client
- Server
Here's an overview before we dig deep 👇
The Host and Client:
Host: An AI app (Claude desktop, Cursor) that provides an environment for AI interactions, accesses tools and data, and runs the MCP Client.
MCP Client: Operates within the host to enable communication with MCP servers.
Next up, MCP server...👇
The Server
A server exposes specific capabilities and provides access to data.
3 key capabilities:
- Tools: Enable LLMs to perform actions through your server
- Resources: Expose data and content from your servers to LLMs
- Prompts: Create reusable prompt templates and workflows
The Client-Server Communication
Understanding client-server communication is essential for building your own MCP client-server.
Let's begin with this illustration and then break it down step by step... 👇
1️⃣ & 2️⃣: capability exchange
client sends an initialize request to learn server capabilities.
server responds with its capability details.
e.g., a Weather API server provides available `tools` to call API endpoints, `prompts`, and API documentation as `resource`.
3️⃣ Notification
Client then acknowledgment the successful connection and further message exchange continues.
Before we wrap, one more key detail...👇
Unlike traditional APIs, the MCP client-server communication is two-way.
Sampling, if needed, allows servers to leverage clients' AI capabilities (LLM completions or generations) without requiring API keys.
While clients to maintain control over model access and permissions
I hope this clarifies what MCP does.
In the future, I'll explore creating custom MCP servers and building hands-on demos around them.
Over to you! What is your take on MCP and its future?
That's a wrap!
If you enjoyed this breakdown:
Follow me → @akshay_pachaar ✔️
Every day, I share insights and tutorials on LLMs, AI Agents, RAGs, and Machine Learning!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
There's one rule you can not miss if you want to do the same!
Here's the full breakdown (with code):
There are primarily 2 factors that determine how well an MCP app works:
- If the model is selecting the right tool?
- And if it's correctly preparing the tool call?
Today, let's learn how to evaluate any MCP workflow using @deepeval's MCP evaluations (open-source).
Let's go!
Here's the workflow:
- Integrate the MCP server with the LLM app.
- Send queries and log tool calls, tool outputs in DeepEval.
- Once done, run the eval to get insights on the MCP interactions.
Let's build a reasoning LLM, from scratch (100% local):
Today, we're going to learn how to turn any model into a reasoning powerhouse.
We'll do so without any labeled data or human intervention, using Reinforcement Finetuning (GRPO)!
Tech stack:
- @UnslothAI for efficient fine-tuning
- @HuggingFace TRL to apply GRPO
Let's go! 🚀
What is GRPO?
Group Relative Policy Optimization is a reinforcement learning method that fine-tunes LLMs for math and reasoning tasks using deterministic reward functions, eliminating the need for labeled data.
Here's a brief overview of GRPO before we jump into code: