---
id: "entity-mcp-d18"
type: "entity"
entityType: "tool"
canonicalName: "Model Context Protocol"
aliases: ["MCP", "Model Context Protocol"]
source_timestamps: ["11:10:00", "22:30:00"]
tags: ["protocol", "standard"]
related: ["concept-mcp", "action-deploy-mcp-server"]
sources: ["s18-anthropic-openai-memory"]
sourceVaultSlug: "s18-anthropic-openai-memory"
originDay: 18
---
# Model Context Protocol (MCP) — Standard

## Profile

The Model Context Protocol (MCP) is the underlying technology that makes the speaker's proposed solution viable. It is described as a universal, **bidirectional** standard that allows AI platforms to read from and write to external, user-owned context databases.

## Role in the Source

MCP is the **load-bearing infrastructure** for the entire BYOC thesis. Without it, [[action-deploy-mcp-server]] reduces to building a static knowledge base that cannot evolve. With it, professionals can host their context once and plug it into any compliant AI platform (e.g., [[entity-claude-d18]] desktop).

For the conceptual treatment, see [[concept-mcp]]. For the prerequisite knowledge a practitioner needs, see [[prereq-mcp-understanding]].

## Caveat (from enrichment)

No canonical public reference matching the exact description in the video was identified during enrichment. Treat MCP here as either a nascent emerging standard or the speaker's own architectural proposal — the strategic implications hold in either case.