Business operationsPublic source

Marketing Orchestration MCP Server

Multi-channel marketing orchestration for AI agents — campaigns, audiences, content generation, ads, social, email, performance analytics, attribution, and budget governance. 22 tools across the full campaign lifecycle.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides marketing capabilities through a typed MCP contract.

Architecture

How Marketing Orchestration MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Marketing Orchestration MCP Server

Validates the request and owns 22 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Marketing Orchestration MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Marketing Orchestration MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

22 named tools

list_campaigns

List by status/channel

see documentation

get_campaign

Details + performance summary

see documentation

create_campaign

Create multi-channel campaign (draft)

see documentation

launch_campaign

Activate across channels

see documentation

pause_campaign

Pause a running campaign

see documentation

list_audiences

List segments with sizes

see documentation

get_audience

Segment definition + criteria

see documentation

create_audience

Build segment from criteria

see documentation

estimate_reach

Estimate before committing

see documentation

list_content

List assets

see documentation

create_content

Generate copy (email, ad, social)

see documentation

get_ab_variants

A/B test variants + performance

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

22 see documentation

launch_campaign — gated if budget exceeds threshold
create_ad — commits ad spend (financial action)
send_campaign_email — external write (customer-facing)
allocate_budget — financial action, shifts real money

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-marketing

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-marketing",
    ["mcp-marketing"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring