---
id: "concept-mcp-d48"
type: "concept"
source_timestamps: ["00:02:29", "00:02:41", "00:12:00"]
tags: ["protocols", "ai-infrastructure", "interoperability"]
related: ["action-mcp-growth-hack", "quote-mcp-usb", "concept-command-line-design", "concept-workflow-blocks"]
definition: "A universal standard protocol that connects AI models to external tools, acting as a universal connector or 'USB plug' for AI agents."
sources: ["s48-markdown-design-meeting"]
sourceVaultSlug: "s48-markdown-design-meeting"
originDay: 48
---
# Model Context Protocol (MCP)

## Definition

A universal standard protocol that connects AI models to external tools and data sources. Acts as a 'USB plug for AI' — any tool that speaks MCP becomes natively callable by any agent that speaks MCP.

## The Analogy

[[entity-nate-b-jones|Nate B. Jones]] frames it explicitly: "MCP is becoming the USB plug for AI" ([[quote-mcp-usb]]). Just as USB collapsed dozens of incompatible peripheral connectors into one standard, MCP collapses bespoke API integrations into a uniform server-client protocol that agents can discover and execute against.

## How It Works (Conceptually)

- Any tool (a design generator, a video renderer, a 3D modeler, a database) is wrapped as an **MCP server** that advertises capabilities.
- An agent (e.g. [[entity-claude-d48|Claude]]) acts as the **MCP client**, reading available capabilities and calling them with structured arguments.
- All of this happens at the command line — no GUI plugin marketplace, no per-tool SDK.

## Why It Underpins the Whole Video

Every downstream paradigm shift in this vault depends on MCP being real and universal:

- [[concept-command-line-design]] — agents need to call design tools.
- [[entity-remotion|Remotion]] — Claude needs to invoke the renderer ([[claim-remotion-top-skill]]).
- [[entity-blender-mcp|Blender MCP]] — exposes Blender's Python API to LLMs.
- [[concept-design-markdown|design.md]] — read by agents over MCP.
- [[concept-workflow-blocks]] — primitives chain via MCP.
- [[action-mcp-growth-hack]] — Jones's prescription: make your product an MCP server.

## Caveat (from enrichment)

MCP's status as the *universal* standard is contested. Competing/analogous protocols include Anthropic Tool Use, OpenAI Functions, and emerging Agent2Agent (A2A). Treat MCP as a leading candidate rather than a settled winner.

## Related
[[quote-mcp-usb]] · [[claim-mcp-usb-for-ai]] · [[action-mcp-growth-hack]] · [[prereq-mcp-understanding-d48]] · [[concept-workflow-blocks]]


## Related across days
- [[concept-mcp-d18]]
- [[prereq-mcp-understanding-d48]]