AWS Glossary
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.
AI & assistant-friendly summary
This section provides structured content for AI assistants and search engines. You can cite or summarize it when referencing this page.
Summary
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.
Key Facts
- •AWS also publishes its own MCP servers for interacting with AWS services
- •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
- •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
Entity Definitions
- Amazon Bedrock
- Amazon Bedrock is an AWS service relevant to model context protocol (mcp).
- Bedrock
- Bedrock is an AWS service relevant to model context protocol (mcp).
Related Content
- AMAZON BEDROCK AGENTCORE— Related service
- AGENTIC COMMERCE READINESS— Related service
- AWS BEDROCK— Related service
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 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 · Tool catalog · Amazon Bedrock AgentCore · Agentic commerce · Human in the loop
Related Services
Amazon Bedrock AgentCore Consulting
Production agent infrastructure on Amazon Bedrock AgentCore — Runtime, Gateway, Memory, Identity, Observability and Evaluations. Bring your own framework; we operate the substrate.
Agentic Commerce Readiness
Make your store sellable to AI shopping agents. ACP and UCP protocol surfaces, an MCP server over your catalog, and product data that survives an agent comparison — built on AWS.
Amazon Bedrock Consulting for Production LLM Applications
Amazon Bedrock implementation consulting — Knowledge Bases, Agents, Guardrails, model routing, and production RAG. Hands-on Bedrock engineering, not GenAI strategy.
Related Articles
AWS MCP Server Hits GA: What It Changes for Agentic Development (Plus the Serverless Agent Plugin)
On May 6, 2026, AWS made its managed MCP server generally available in 2 regions—with IAM guardrails, CloudWatch metrics, and CloudTrail logging—while the March 25, 2026 Agent Plugin for AWS Serverless brought packaged SAM/CDK skills into Cursor and Claude Code.
AWS Agent Toolkit for AWS: Plugins, Rules, and Every Skill Explained
The official aws/agent-toolkit-for-aws repo ships 43 atomic Agent Skills across 13 category folders—plus aws-core, aws-agents, and aws-data-analytics plugins. Here is why that bundle matters for IAM and audit posture, how the tree fits together, and how to pair it with the May 6, 2026 GA AWS MCP Server.
How AI Agents Should Communicate With Shopify, ERP, CRM and Warehouse Systems (2026)
Tool-based integration beats Admin API keys in the prompt. No native Shopify connector. Reuse Gateway ~180 to 95 ms and ~$791/mo at 50K sessions — not an integration SLA.
AWS Security Hub MCP App (Preview): Investigate Exposure Findings Inside Claude Desktop
On Jul 27, 2026, AWS launched the Security Hub MCP App preview—8 read-only tools that bring exposure findings, attack paths, and remediation guidance into Claude Desktop at no additional cost for Security Hub customers.
Need help with this topic?
Our AWS-certified team implements, audits, and optimizes these services in production — from Bedrock RAG pipelines to multi-account landing zones.