AI Engineering Academy · Lesson

What Is MCP and Why It Matters

Understand what the Model Context Protocol standardizes, how it differs from ad-hoc function calling integrations, and why it is becoming the lingua franca for AI tool connectivity.

What Is MCP and Why It Matters is a free AI Engineering Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the AI Engineering Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

The Tool Integration Problem

Every AI assistant today solves the same problem differently: how do you connect an LLM to your databases, APIs, files, and services? Without a standard, every integration is a custom one-off — OpenAI function calling works differently from Anthropic's tool use, which works differently from Gemini's. Developers rebuild the same adapters over and over.

What Is the Model Context Protocol?

Model Context Protocol (MCP) is an open standard created by Anthropic that defines a common interface for connecting LLMs to external data sources and tools. Think of it like USB for AI integrations — once a tool or data source implements the MCP server spec, any MCP-compatible AI client can use it without custom code. Announced in November 2024, it has rapidly gained adoption across the industry.

The Client-Server Architecture

MCP uses a client-server model: an AI application (the client) connects to one or more MCP servers. Each server exposes capabilities — tools the model can call, resources it can read, and prompt templates it can use. The client (such as Claude Desktop or a custom app) manages the connections and routes tool calls to the correct server.

Client: Claude Desktop, VS Code extension, or your app
Server: A process exposing tools via MCP — a database adapter, a file system, a web search service

MCP's Three Primitives

MCP servers expose three types of capabilities:

Tools: Functions the model can call to take actions, similar to function calling. Example: execute_query(sql).
Resources: Static or dynamic data the model can read — like files, database rows, or API responses. Example: file:///config/settings.json.
Prompts: Reusable prompt templates the user can invoke with parameters. Example: a code review prompt that accepts a diff.

MCP vs. Direct Function Calling

With direct function calling, you define tools in your application code — tightly coupled to your LLM provider's API. With MCP, tools are defined in a separate server process that any client can connect to. Key differences:

Portability: One MCP server works with Claude, custom apps, and future clients
Reusability: Share MCP servers across teams and projects
Separation of concerns: Tool servers can be maintained independently from the AI application

MCP Transport: stdio and HTTP/SSE

MCP servers communicate with clients over two transport mechanisms. stdio is used for local tools — the client spawns the server as a child process and communicates over stdin/stdout. This is simple and secure for developer tools. HTTP + Server-Sent Events (SSE) is used for remote servers accessible over a network, suitable for shared team tools or production deployments.

# Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json)
# Connecting to a local MCP server via stdio:

# {
#   "mcpServers": {
#     "my-database": {
#       "command": "python",
#       "args": ["/path/to/my_mcp_server.py"],
#       "env": {
#         "DATABASE_URL": "postgresql://localhost/mydb"
#       }
#     }
#   }
# }

The MCP Ecosystem

Since MCP's release, a growing ecosystem of pre-built servers has emerged. Anthropic maintains official servers for common integrations, and community servers cover hundreds of services. Rather than building custom tool integrations from scratch, you can drop in an existing MCP server.

Official: GitHub, Google Drive, Slack, PostgreSQL, filesystem, web search
Community: Jira, Notion, Stripe, Snowflake, MongoDB, and many more
Custom: Build your own for proprietary internal tools

MCP in AI Development Workflows

MCP transforms AI coding assistants. With an MCP server connected to your codebase, Claude Desktop can read files, run tests, check git history, query databases, and browse documentation — all from a single chat window. This enables true agentic development where the AI understands and acts on your full development environment.

MCP SDK Overview

Anthropic provides SDKs for building MCP servers in Python and TypeScript. The Python SDK is mcp (install with pip install mcp). You define tools using decorators, resources using URI patterns, and the SDK handles the protocol negotiation, message serialization, and transport details for you.

# Install
# pip install mcp

# Minimal MCP server skeleton
from mcp.server import Server
from mcp.server.stdio import stdio_server
from mcp import types

app = Server('my-first-mcp-server')

@app.list_tools()
async def list_tools():
    return [
        types.Tool(
            name='hello',
            description='Returns a greeting message.',
            inputSchema={
                'type': 'object',
                'properties': {
                    'name': {'type': 'string', 'description': 'Name to greet'}
                },
                'required': ['name']
            }
        )
    ]

@app.call_tool()
async def call_tool(name: str, arguments: dict):
    if name == 'hello':
        return [types.TextContent(type='text', text=f'Hello, {arguments["name"]}!')]

import asyncio
asyncio.run(stdio_server(app))

Why MCP Matters for the Industry

MCP represents a shift toward standardization in AI tooling. Just as REST standardized web APIs and LSP standardized IDE language features, MCP is standardizing how AI models connect to tools. This benefits developers (build once, use everywhere), enterprises (audit and control one integration layer), and the ecosystem (shared, reusable tool libraries).

MCP Adoption and Future Direction

MCP adoption has grown rapidly since its launch. Major coding assistants (Cursor, Windsurf, VS Code Copilot), enterprise AI platforms, and cloud providers have announced MCP support. The protocol continues to evolve with proposals for authentication, sampling, and streaming improvements. Understanding MCP positions you to build interoperable AI integrations that work across the growing ecosystem.

Quick Check

Test your understanding of what MCP is and why it matters.

Lesson Recap

In this lesson you learned: MCP is an open standard that defines a universal interface for connecting LLMs to external tools and data sources, MCP servers expose three primitives: tools, resources, and prompts, and the MCP ecosystem provides pre-built servers for common services so you don't start from scratch. Next up we build our first MCP server in Python and connect it to Claude Desktop.

Frequently asked questions

Is the “What Is MCP and Why It Matters” lesson free?

Yes — the full text of “What Is MCP and Why It Matters” is free to read here on the web, and the AI Engineering Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the AI Engineering Academy course, upgrade to CoddyKit PRO.

What will I learn in “What Is MCP and Why It Matters”?

Understand what the Model Context Protocol standardizes, how it differs from ad-hoc function calling integrations, and why it is becoming the lingua franca for AI tool connectivity. You practise AI Engineering Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start AI Engineering Academy?

No prior experience is required. AI Engineering Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “What Is MCP and Why It Matters” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this AI Engineering Academy lesson?

Yes. Every AI Engineering Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to AI Engineering Academy