MCP Servers

模型上下文协议服务器、框架、SDK 和模板的综合目录。

Marketing Orchestration MCP — campaigns, audiences, content, ads, attribution, budget governance for AI agents

创建于 5/25/2026
更新于 about 3 hours ago
Repository documentation and setup instructions

Marketing Orchestration MCP Server

Crates.io License ADK-Rust Enterprise Registry Ready

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.

Architecture

MCP Marketing Architecture

Why This Exists

The marketing MCP landscape is fragmented — single-platform tools (Google Ads MCP, MailerLite MCP) or read-only analytics. Nobody offers unified campaign orchestration across channels with budget governance.

| Capability | Competitors | mcp-marketing | |-----------|:-----------:|:-------------:| | Multi-channel orchestration | ❌ | ✅ | | Campaign lifecycle (draft→launch→pause) | ❌ | ✅ | | Budget governance (approval gates) | ❌ | ✅ | | Cross-channel attribution | ⚠️ read-only | ✅ | | Multi-backend (HubSpot, Mailchimp, Ads) | ❌ | ✅ |

Tools (22)

Campaigns (5)

| Tool | Purpose | Risk | |------|---------|------| | list_campaigns | List by status/channel | read_only | | get_campaign | Details + performance summary | read_only | | create_campaign | Create multi-channel campaign (draft) | internal_write | | launch_campaign | Activate across channels | gated (budget) | | pause_campaign | Pause a running campaign | internal_write |

Audiences (4)

| Tool | Purpose | Risk | |------|---------|------| | list_audiences | List segments with sizes | read_only | | get_audience | Segment definition + criteria | read_only | | create_audience | Build segment from criteria | internal_write | | estimate_reach | Estimate before committing | read_only |

Content (4)

| Tool | Purpose | Risk | |------|---------|------| | list_content | List assets | read_only | | create_content | Generate copy (email, ad, social) | internal_write | | get_ab_variants | A/B test variants + performance | read_only | | get_content_calendar | Scheduled content view | read_only |

Channels (4)

| Tool | Purpose | Risk | |------|---------|------| | list_channels | Configured channels + status | read_only | | schedule_post | Schedule social media post | external_write | | create_ad | Create ad (Google/Meta/LinkedIn) | financial_action | | send_campaign_email | Send email to audience | external_write |

Performance (3)

| Tool | Purpose | Risk | |------|---------|------| | get_campaign_metrics | Impressions, clicks, conversions, ROAS | read_only | | get_attribution | Multi-touch attribution | read_only | | get_channel_comparison | Cross-channel performance | read_only |

Budget (2)

| Tool | Purpose | Risk | |------|---------|------| | get_budget_status | Spend vs budget, burn rate | read_only | | allocate_budget | Shift budget between channels | financial_action |

Installation

cargo install mcp-marketing

Configuration

| Backend | Env Vars | What it provides | |---------|----------|-----------------| | HubSpot | HUBSPOT_ACCESS_TOKEN | Campaigns, contacts, email, workflows | | Mailchimp | MAILCHIMP_API_KEY | Campaigns, audiences, automations | | Custom API | MARKETING_API_URL | Your own backend (full spec) |

Auto-detected from env vars. No data stored in the MCP server.

Client Configuration

{
  "mcpServers": {
    "marketing": {
      "command": "mcp-marketing",
      "args": [],
      "env": {
        "HUBSPOT_ACCESS_TOKEN": "your-token"
      }
    }
  }
}

End-to-End Example: Product Launch Campaign

Agent: "Launch a product campaign for our new feature targeting enterprise users"

1. create_audience(name="Enterprise Users", criteria={"plan":"enterprise","active":true})
2. estimate_reach(criteria={"plan":"enterprise"}) → 2,400 users
3. create_campaign(name="Feature Launch", channels=["email","linkedin","google"], audience_id="aud-1", budget_cents=500000)
4. create_content(content_type="email_subject", brief="New feature announcement for enterprise")
5. create_content(content_type="ad_copy", brief="Enterprise feature - LinkedIn ad")
6. create_ad(platform="linkedin", campaign_id="camp-1", headline="...", body="...")
7. send_campaign_email(campaign_id="camp-1", audience_id="aud-1", subject="...", body="...")
8. launch_campaign(id="camp-1")
9. get_campaign_metrics(id="camp-1") → track performance
10. get_channel_comparison() → email vs linkedin vs google
11. allocate_budget(campaign_id="camp-1", allocations={"linkedin":300000,"google":200000})

Governance

  • 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

License

Apache-2.0


Part of the ADK-Rust Enterprise MCP server ecosystem.

Built with ❤️ by Zavora AI

快速设置
此服务器的安装指南

安装命令 (包未发布)

git clone https://github.com/zavora-ai/mcp-marketing
手动安装: 请查看 README 获取详细的设置说明和所需的其他依赖项。

Cursor 配置 (mcp.json)

{ "mcpServers": { "zavora-ai-mcp-marketing": { "command": "git", "args": [ "clone", "https://github.com/zavora-ai/mcp-marketing" ] } } }