---
id: "entity-mcp-d51"
type: "entity"
entityType: "tool"
canonicalName: "Model Context Protocol"
aliases: ["MCP"]
source_timestamps: ["00:07:08", "00:07:30"]
tags: ["open-standards", "protocols"]
related: ["entity-anthropic", "concept-google-play-services-pattern", "concept-cnw-zip-extensions"]
url: "https://modelcontextprotocol.org/"
sources: ["s51-512k-leaked-code"]
sourceVaultSlug: "s51-512k-leaked-code"
originDay: 51
---
# Model Context Protocol (MCP)

## Profile

An open standard published by [[entity-anthropic-d51|Anthropic]] designed to be the **universal connector** between AI tools and data sources. Adopted by 50+ tools including Google Vertex; 200+ implementations on GitHub.

## The Strategic Read

The speaker [[entity-nate-b-jones|Nate B. Jones]] argues Anthropic is using MCP as the *open foundation* upon which they are building a proprietary, locked-in ecosystem (via [[concept-cnw-zip-extensions|.cnw.zip]] [[entity-conway-d51|Conway]] extensions) — a direct parallel to Android's relationship with Google Play Services. See [[concept-google-play-services-pattern]] and [[contrarian-open-standards-lock-in]].

## Counter-Perspective

MCP is genuinely widely adopted (200+ implementations); 80%+ of GitHub repos using it stick to MCP-only without `.cnw.zip`. So while the *strategy* may be capture, the *execution* is contestable.

## Prerequisite

Understanding MCP is required to grasp the broader argument — see [[prereq-mcp-knowledge]].

## Canonical Reference

https://modelcontextprotocol.org/