---
id: "entity-model-context-protocol"
type: "entity"
entityType: "other"
canonicalName: "Model Context Protocol"
aliases: ["MCP"]
source_timestamps: ["00:07:30", "00:12:47"]
tags: ["protocol", "standards", "integrations"]
related: ["concept-layer-2-identity", "concept-layer-4-tools", "entity-composio"]
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Model Context Protocol (MCP)

## Profile
Model Context Protocol (MCP) is an emerging open standard, mentioned as a potential future solution for both:
- **agent service discovery** in [[concept-layer-2-identity]]
- **tool integration** in [[concept-layer-4-tools]]

Not a company. No single canonical site (the specification is maturing in public).

## Strategic implication
If MCP achieves universal adoption (analogous to how TCP/IP, HTTP, or OAuth standardized prior layers), the value of proprietary middleware like [[entity-composio]] could diminish — agents would discover and use tools through a common standard rather than through a managed hub.

## Why it probably doesn't kill middleware soon
Large enterprises adopt new standards slowly and unevenly. Even if MCP wins technically, fragmentation in adoption keeps managed integration middleware durable for years.

In the M2M-auth literature, MCP is often referenced alongside OAuth Client Credentials and mTLS as part of the toolkit for agent-to-agent flows.