RS Glossary
Model Context Protocol (MCP)
Model Context Protocol (MCP) is an open protocol that standardizes how AI applications exchange context and capabilities with external services through a host-client-server architecture.
- Review state
- Reviewed in POC
- Freshness
- Current
- Version
- 1
- Model Context Protocol (MCP)
- Model Context Protocol
- MCP
Remember it this wayMCP is the language of the connection; a server is one participant.
In plain language
MCP gives compatible applications and services shared rules for discovering and using prompts, resources, and tools. The host application manages clients and user control; each client connects to a particular server. The protocol defines the exchange, while each implementation decides what capabilities to offer and authorize.
Why it matters
A shared protocol can reduce one-off integration work and make external capabilities more portable across AI applications. The same connection can expose data or actions, so clear permissions, isolation, and informed consent remain part of the architecture.
Example
A desktop AI application uses MCP clients to connect separately to a source-code server and a calendar server. Both integrations use the same protocol, but each server exposes different capabilities and keeps a separate connection boundary.
Common misconception
MCP is not a model, an MCP server, or blanket permission for an AI to use every connected system. It standardizes messages and capabilities. The host, client, server, and user still have distinct security and authorization responsibilities.
Related terms
Sources
- Model Context Protocol, “Architecture”specifies the host-client-server architecture, capability negotiation, and security boundaries.
- Model Context Protocol, “Server features overview”defines prompts, resources, and tools as server primitives with different control relationships.
Learn more
- Read [[mcp-server|MCP Server]] for the implementation role that exposes selected capabilities.
- Treat server output as an external trust boundary and evaluate risks such as [[prompt-injection|Prompt Injection]].
Public history
30 recorded events · 30 public summaries
A potential shared concept was discussed and selected for initial glossary drafting.
The captured candidate received a complete initial draft and entered section-level human review.
Radar reviewed the initial definition draft for human consideration.
Radar reviewed the initial plain-language-explanation draft for human consideration.
Radar reviewed the initial why-it-matters draft for human consideration.
Radar reviewed the initial example draft for human consideration.
Radar reviewed the initial common-misconception draft for human consideration.
Radar reviewed the initial remember-it-this-way draft for human consideration.
Radar reviewed the initial related-terms draft for human consideration.
Radar reviewed the initial sources draft for human consideration.
Radar reviewed the initial learn-more draft for human consideration.
Definition review recorded as approve.
Plain-Language Explanation review recorded as approve.
Why It Matters review recorded as approve.
Example review recorded as approve.
Common Misconception review recorded as approve.
Remember It This Way review recorded as approve.
Related Terms review recorded as approve.
Sources review recorded as approve.
Learn More review recorded as approve.
All wording and media review gates are approved; the term is now canonical.
Definition review recorded as approve.
Plain-Language Explanation review recorded as approve.
Why It Matters review recorded as approve.
Example review recorded as approve.
Common Misconception review recorded as approve.
Remember It This Way review recorded as approve.
Related Terms review recorded as approve.
Sources review recorded as approve.
Learn More review recorded as approve.
Source: vault/Glossary/terms/model-context-protocol/term.md · sha256:837d1af45f417dc83552f7f338f34f50ef07e4a6d5cbe88bf3216efaef29f590 · Release: rs-glossary-glossary-team-poc-0.5.5-2026-09-02