---
title: Model Context Protocol (MCP)
description: MCP is an open standard for connecting AI models to external tools and data through a uniform server interface — the transport layer beneath most production agent tool use.
url: https://www.factualminds.com/glossary/model-context-protocol/
publishDate: 2026-08-30
updateDate: 2026-08-30
---

# Model Context Protocol (MCP)

> MCP is an open standard for connecting AI models to external tools and data through a uniform server interface — the transport layer beneath most production agent tool use.

## Definition

The **Model Context Protocol (MCP)** is an open standard for connecting AI models to external tools, data sources and services through a uniform interface. An **MCP server** exposes a set of capabilities — tools to call, resources to read, prompts to reuse — and any MCP-aware client can consume them without a bespoke integration.

The practical value is combinatorial. Without a shared protocol, connecting *N* assistants to *M* systems is *N × M* integrations. With MCP it is *N + M*.

## Where it fits in an agent stack

MCP is the **transport and interface layer** for tool use. It is not an agent framework, not a runtime, and not a model.

On AWS, [Amazon Bedrock AgentCore](/glossary/bedrock-agentcore/) Gateway is the governed entry point through which an agent reaches tools — including MCP servers — with authentication, customer-configurable rate limits, and Cedar-based fine-grained access control on writes. AWS also publishes its own MCP servers for interacting with AWS services.

## MCP in commerce

For merchants, an MCP server over the catalog is how an agent reaches product, inventory and order data without you shipping a separate integration for every assistant that appears.

One surface to maintain, one place to enforce authentication and rate limits, one audit log. That framing matters, because an MCP server exposing commercial data is a **public interface** — an infrastructure and security design problem before it is an AI one. Blast radius under a scrape, per-caller rate limiting, and what a compromised token can reach are the questions to settle first.

## When not to use it

- **A single, stable integration.** If exactly one assistant needs exactly one system, a direct API call is simpler and has fewer moving parts. MCP earns its keep at *N × M*, not at 1 × 1.
- **Write-heavy, high-risk actions without an authorization layer.** MCP describes what a tool does; it does not decide whether this caller may do it. Pair it with policy evaluation outside the model — Cedar via AgentCore Gateway, or your own authorization service.
- **As a substitute for a data contract.** Exposing four systems that disagree about what a product identifier is, through a clean protocol, produces confidently wrong answers with better formatting.

## Related terms

[AI agent](/glossary/ai-agent/) · [Tool catalog](/glossary/tool-catalog/) · [Amazon Bedrock AgentCore](/glossary/bedrock-agentcore/) · [Agentic commerce](/glossary/agentic-commerce/) · [Human in the loop](/glossary/human-in-the-loop/)

## Related AWS Services

- amazon-bedrock-agentcore
- agentic-commerce-readiness
- aws-bedrock

## Related Posts

- aws-mcp-server-ga-agent-toolkit-serverless-plugin
- aws-agent-toolkit-for-aws-skills-guide
- ai-agent-ecommerce-integration-2026
- aws-security-hub-mcp-app-preview-2026

---

*Source: https://www.factualminds.com/glossary/model-context-protocol/*