Module 5: Model Context Protocol (MCP)

Lesson 1: What is MCP and Why It Matters?

Before the Model Context Protocol (MCP), connecting an LLM to a data source (like GitHub, a Database, or Google Drive) was a fragmented nightmare. Every developer had to write custom "Glue Code" to bridge the gap between the model's chat interface and the data source's API.

In this lesson, we define the MCP standard and understand why it is the "USB-C of AI Architecture."

---

1. The Fragmentation Problem

Imagine you want Claude to read your Gmail and update a Jira ticket.

• For Gmail: You write OAuth logic, parse MIME types, and summarize.
• For Jira: You write a completely different set of logic for their specific API.

If you change models (e.g., from Claude to a custom local model), you have to rewrite all that glue code. The system is Brittle and Non-Scalable.

---

2. The MCP Solution: A Unified Contract

MCP introduces a standard protocol that sits between the Client (the app Claude lives in) and the Server (the data source).

Instead of "Custom Glue," you use a Standardized Interface. Any MCP-compliant client can talk to any MCP-compliant server.

The Three Entities:

1. The Client: The host application (e.g., Claude Desktop, a custom FastAPI app).
2. The Server: The bridge to the data (e.g., a "GitHub MCP Server").
3. The Model: The intelligence that uses the protocol.

---

3. Why it matters for the CCA-F Architect

The MCP is Domain 2 of the exam. You are expected to understand it not as a "Feature," but as a System-level Architecture.

• Interoperability: Build a tool once, use it across any Claude-powered app.
• Security: Standardize how credentials and data are handled.
• Context injection: Dynamically provide data to the model only when needed.

---

4. Visualizing the Protocol

graph LR
    A[Claude Model] <-->|Instruction| B[MCP Client]
    B <-->|Standard Protocol| C[MCP Server: GitHub]
    B <-->|Standard Protocol| D[MCP Server: Database]
    B <-->|Standard Protocol| E[MCP Server: Search]
    C <--> F(GitHub API)
    D <--> G(Postgres)
    E <--> H(Google Search)

In the diagram above, the MCP Client is the orchestrator. It doesn't need to know "How" to talk to Postgres; it only needs to know "How" to talk to the MCP Protocol.

---

5. Summary

MCP is an open standard that decouples models from data sources. It provides a reliable, predictable, and scalable way to give Claude "Hands" and "Eyes."

In the next lesson, we will look at how the protocol actually works: Standardizing Tool Communication.

---

Interactive Quiz

1. What was the "Fragmentation Problem" before MCP?
2. Define the three entities in an MCP architecture.
3. Why is MCP called the "USB-C of AI"?
4. Scenario: You have built a custom tool to read your company's proprietary legal docs. Why is it better to build this as an MCP server rather than a custom tool in a single script?

---

Reference Video: