Model Context Protocol
Open protocol for connecting AI applications to tools, data sources, prompts, and reusable context through defined server interfaces.
- Published
- Updated
- Evidence checked
- Sources
- 2
At a glance
MCP can expose marketing systems to agents, but permissions, approval, and evidence remain application responsibilities.
- Record type
- Standard
- Primary scope
- MCP · agents · tool access
- Evidence state
- Official specification
- Record owner
- Marketing Wiki Editors
Model Context Protocol defines how AI applications connect to external capabilities. Server can expose tools for model-called actions, resources for application-selected context, and prompts for reusable interaction patterns.
Marketing use#
MCP can connect agent to:
- Content repository
- Analytics warehouse
- Campaign platform
- Asset library
- Customer research
- Approval system
Safety boundary#
Protocol does not make action safe. Server and client still need authentication, authorization, input validation, audit records, and human approval for consequential mutations.
Read-only discovery tools should remain separate from sending, publishing, deleting, billing, or audience mutation.
Good index interface#
Marketing catalog MCP server could expose bounded read tools:
search_resources
get_resource
list_categories
get_changes_since
Every result should retain evidence URL, verification date, and dataset version.
Evidence state#
This entry summarizes official MCP documentation. Marketing Wiki has not yet published MCP server or interoperability benchmark.
For a client-specific acceptance method, see Grok Bot for Email Marketing: MCP Permissions, Approval, and a Migma Case Study.