---
title: "What is Model Context Protocol (MCP) in AI?"
description: "Model Context Protocol (MCP) is an open standard for connecting AI applications to tools and data. Learn how MCP works and how it compares to function calling."
type: "glossary-term"
canonical_url: "https://theaiengineering.com/glossary/model-context-protocol"
markdown_url: "https://theaiengineering.com/glossary/model-context-protocol.md"
topic: "Model Context Protocol"
author: "The AI Engineering Editors"
publisher: "The AI Engineering"
updated: "2026-11-06"
keywords: ["Model Context Protocol (MCP)","MCP","model context protocol"]
citation: "The AI Engineering Editors. \"What is Model Context Protocol (MCP) in AI?\" The AI Engineering, updated Nov 06, 2026. https://theaiengineering.com/glossary/model-context-protocol"
---

# What is Model Context Protocol (MCP) in AI?

Also called MCP, model context protocol.

> **Definition of Model Context Protocol (MCP):** Model Context Protocol (MCP) is an open protocol, introduced by Anthropic in November 2024, that standardizes how AI applications connect to external tools, data sources, and prompts through MCP servers.

Model Context Protocol (MCP) is an open standard that defines how AI applications connect to external tools and data. Anthropic [introduced MCP](https://www.anthropic.com/news/model-context-protocol) on November 25, 2024, to replace one-off integrations between each AI application and each data source with a single protocol. In December 2025, MCP became a founding project of the Linux Foundation's Agentic AI Foundation, which now hosts its development.

## How MCP works

MCP works through three roles defined in the [MCP specification](https://modelcontextprotocol.io/specification/latest): a host (the AI application, such as an IDE or a chat app), clients (connectors inside the host, one per server connection), and [MCP servers](https://theaiengineering.com/glossary/mcp-server) that expose capabilities. All messages use [JSON-RPC 2.0](https://theaiengineering.com/glossary/json-rpc).

**Figure 1: One MCP host with a dedicated client per server connection.**

An MCP host contains three clients, each connected to its own server: a local files server over stdio and remote tickets and database servers over Streamable HTTP.

Components:

- **Client 1**
- **Client 2**
- **Client 3**
- **Files server**: Local subprocess
- **Tickets server**: Remote
- **Database server**: Remote

Groups:

- Host (AI application): Client 1, Client 2, Client 3

Connections:

- Client 1 → Files server: stdio
- Client 2 → Tickets server: Streamable HTTP
- Client 3 → Database server: Streamable HTTP

Servers offer three primitives: tools (functions the model can call), resources (read-only data supplied as context), and prompts (reusable templates a user invokes). The standard transports are [stdio](https://theaiengineering.com/glossary/mcp-transport), for local servers launched as subprocesses, and Streamable HTTP, for remote servers, with an authorization framework for HTTP that recommends OAuth for obtaining tokens. The current revision, dated 2026-07-28, makes the protocol stateless: every request carries its protocol version and client capabilities, replacing the connection-level initialization handshake of earlier revisions.

## MCP vs function calling

MCP and function calling solve different layers of the same problem. [Function calling](https://theaiengineering.com/glossary/tool-calling) is a model capability: the model receives tool definitions in its request and returns a structured call. MCP is the integration layer: it standardizes how an application discovers tools (`tools/list`), executes them (`tools/call`), and connects to the systems behind them.

A host typically reads tool definitions from its MCP servers, passes them to the model as function definitions, and routes each resulting call back to the right server. The practical benefit is reuse: one MCP server for a database works with every MCP-compatible host, instead of each application writing its own integration.

[What is Model Context Protocol](https://theaiengineering.com/articles/what-is-model-context-protocol) covers architecture and security in depth, and [A2A vs MCP](https://theaiengineering.com/articles/a2a-vs-mcp) explains how MCP relates to agent-to-agent protocols. The [MCP topic hub](https://theaiengineering.com/topics/mcp) collects related guides.

## Related terms

- [MCP server](https://theaiengineering.com/glossary/mcp-server): An MCP server is a program that exposes tools, resources, and prompts to AI applications through the Model Context Protocol, running locally over stdio or remotely over Streamable HTTP.
- [Tool calling](https://theaiengineering.com/glossary/tool-calling): Tool calling is an LLM capability in which the model, given a list of tool definitions, outputs a structured request naming a tool and its arguments, which the application executes and returns.
- [A2A protocol](https://theaiengineering.com/glossary/a2a-protocol): The A2A (Agent2Agent) protocol is an open standard, introduced by Google in April 2025, that lets AI agents built on different frameworks discover each other, exchange messages, and delegate tasks.
- [AI agent](https://theaiengineering.com/glossary/ai-agent): An AI agent is a software system in which a large language model runs in a loop, calling tools, reading their results, and repeating until the task is complete or a stop condition is reached.
- [Context engineering](https://theaiengineering.com/glossary/context-engineering): Context engineering is the practice of selecting, structuring, and pruning all the information placed in an LLM's context window at each step, including instructions, retrieved data, tool results, and memory.
- [JSON-RPC](https://theaiengineering.com/glossary/json-rpc): JSON-RPC is a lightweight, transport-agnostic remote procedure call protocol that encodes method calls, results, and errors as JSON objects; version 2.0 is the message format of MCP and A2A.
- [MCP transport](https://theaiengineering.com/glossary/mcp-transport): An MCP transport is the binding that carries Model Context Protocol messages between a client and a server; the specification defines stdio for local subprocesses and Streamable HTTP for remote servers.
- [MCP gateway](https://theaiengineering.com/glossary/mcp-gateway): An MCP gateway is a proxy that sits between MCP hosts and many MCP servers, exposing them through one endpoint and centralizing authentication, tool access policy, and audit logging.

## Guides that cover model context protocol (mcp)

- [What is the Model Context Protocol (MCP)? How it works](https://theaiengineering.com/articles/what-is-model-context-protocol): The Model Context Protocol (MCP) is an open standard for connecting AI apps to tools and data. Learn its architecture, transports, tool calls, and security.
- [How to build an MCP server: a Python and TypeScript tutorial](https://theaiengineering.com/articles/how-to-build-an-mcp-server): Learn how to build an MCP server with the official Python and TypeScript SDKs: tools, resources, transports, testing, client config, and production security.
- [A2A protocol vs MCP: differences and when to use each](https://theaiengineering.com/articles/a2a-vs-mcp): A2A protocol vs MCP: A2A connects AI agents to other agents, and MCP connects an agent to tools and data. Compare agent cards, tasks, transports, and security.
- [What is tool calling? How LLM function calling works](https://theaiengineering.com/articles/tool-calling): Tool calling lets an LLM request actions from your code through structured calls. Learn the request loop, parallel calls, structured outputs, security, and MCP.
- [How to build an AI agent: a step-by-step guide in Python](https://theaiengineering.com/articles/how-to-build-an-ai-agent): Learn how to build an AI agent from scratch in Python: when you need one, tool schemas, the agent loop, stop conditions, guardrails, evals, and tracing.
- [AI coding agents: how they work and how the major tools compare](https://theaiengineering.com/articles/ai-coding-agents): AI coding agents compared: how they differ from autocomplete, the four main categories, a comparison table of major tools, and how to evaluate and secure them.
- [AI agent frameworks compared: LangGraph, CrewAI, ADK, and more](https://theaiengineering.com/articles/ai-agent-frameworks): An AI agent frameworks comparison of LangGraph, LangChain, CrewAI, the OpenAI, Claude, and Google SDKs, Pydantic AI, Mastra, and more, by language and license.
- [What is an AI gateway? How it works and when you need one](https://theaiengineering.com/articles/what-is-an-ai-gateway): An AI gateway is a proxy between your apps and model providers. Learn how it works, its core features, AI gateway vs API gateway, and open source options.
- [What are AI agents? How agents work and when to use one](https://theaiengineering.com/articles/what-are-ai-agents): AI agents are LLM systems that call tools in a loop until a task is done. Learn how the loop works, agents vs agentic AI, examples, failure modes, and limits.
- [What is AI engineering? The discipline, the stack, and the work](https://theaiengineering.com/articles/what-is-ai-engineering): What is AI engineering? A plain definition, how it differs from ML and software engineering, the layers of the stack, and what AI engineers do day to day.

Part of the [Model Context Protocol](https://theaiengineering.com/topics/mcp) topic hub.

## Cite this definition

The AI Engineering Editors. "What is Model Context Protocol (MCP) in AI?" The AI Engineering, updated Nov 06, 2026. https://theaiengineering.com/glossary/model-context-protocol

- Title: What is Model Context Protocol (MCP) in AI?
- Author: The AI Engineering Editors
- Publisher: The AI Engineering
- Updated: 2026-11-06
- URL: https://theaiengineering.com/glossary/model-context-protocol
- Markdown: https://theaiengineering.com/glossary/model-context-protocol.md
