StandardOfficial specification

Model Context Protocol

MCP can expose marketing systems to agents, but permissions, approval, and evidence remain application responsibilities.

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.

Sources

Evidence used on this page

  1. MCP server concepts
  2. Model Context Protocol specification