---
id: "concept-mcp"
type: "concept"
source_timestamps: ["11:10:00", "11:25:00", "22:30:00", "23:00:00"]
tags: ["protocols", "interoperability", "infrastructure"]
related: ["action-deploy-mcp-server", "concept-professional-capital", "entity-mcp"]
definition: "An open, bidirectional standard that allows AI models to read from and write to external, user-controlled data sources, acting as the 'HTTP for AI'."
sources: ["s18-anthropic-openai-memory"]
sourceVaultSlug: "s18-anthropic-openai-memory"
originDay: 18
---
# Model Context Protocol (MCP)

## Definition

An open, bidirectional standard that allows AI models to read from and write to external, user-controlled data sources, acting as the 'HTTP for AI'.

## Body

The Model Context Protocol (MCP) is presented as the **critical technological unlock** for the "Bring Your Own Context" (BYOC) paradigm. [[entity-nate-b-jones]] describes MCP using two analogies:

- **"USB-C connector for AI"** — a universal physical-style connector
- **"HTTP for AI"** — a universal communication protocol that decouples client from server

See also the entity stub at [[entity-mcp-d18]].

## Crucial Property: Bidirectional

MCP is **not just a read-only protocol**. It is a bidirectional read-write standard. This means an MCP-compliant AI agent can:
1. Dynamically **query** a user's personal context database to retrieve relevant domain knowledge or workflow preferences.
2. **Write back** to that database to update preferences based on new interactions.

This is why [[prereq-mcp-understanding]] insists practitioners must internalize the read-write nature — otherwise MCP looks like a static backup rather than living infrastructure.

## Why MCP Breaks Lock-In

By hosting their professional context on a personal MCP server (see [[action-deploy-mcp-server]]), a knowledge worker can plug their accumulated [[concept-professional-capital]] into any compliant AI platform — [[entity-claude-d18]], [[entity-chatgpt-d18]], Gemini, etc. This architecture **breaks platform lock-in**, shifting the center of gravity from the siloed AI vendor to the user's portable, self-owned context infrastructure.

## Enrichment Caveat

The enrichment overlay flagged that public references to a formally established "Model Context Protocol" matching this exact description were limited at the time of extraction. Adjacent interoperability efforts include OpenAI function calling, Anthropic tool use, and the emerging AI Exchange Protocol — but none provide the bidirectional user-owned context DB pattern that MCP describes here. Treat this as a forward-looking architecture pattern that the speaker is advocating for, even if standardization is nascent.


## Related across days
- [[concept-model-context-protocol]]
- [[concept-open-brain-d21]]
- [[concept-open-brain-d22]]
- [[concept-shared-surface]]
- [[concept-context-graph]]