Skip to main content
Glama
vinkius-labs

Salesforce Marketing Cloud MCP

by vinkius-labs
README.md
# šŸŽÆ Salesforce Marketing Cloud MCP Integration

[![Host on Vinkius Edge](https://img.shields.io/badge/Deploy%20on-Vinkius%20Edge-blue?style=for-the-badge)](https://vinkius.com/mcp/salesforce-marketing-cloud)
[![Docker Pulls](https://img.shields.io/docker/pulls/vinkius/salesforce-marketing-mcp?style=for-the-badge&logo=docker&color=2496ed)](https://hub.docker.com/r/vinkius/salesforce-marketing-mcp)

A cutting-edge Model Context Protocol server that translates LLM intent into Salesforce Marketing Cloud (SFMC) orchestration. Let your autonomous agents segment audiences, manage subscribers, and trigger Journey Builder workflows entirely through natural language.

## Revolutionizing Campaign Orchestration

Interacting with the SFMC SOAP and REST APIs is notoriously difficult due to complex XML envelopes, strict rate limits, and asynchronous data extension handling. This MCP server acts as an intelligent proxy. It provides LLMs with deterministic, safe tools to interact with your marketing stack.

### Why Vinkius is the Optimal Deployment Strategy

To ensure your marketing automation remains uninterrupted, this MCP is built to run on the **Vinkius Edge Platform**.
- **Zero-Maintenance Infrastructure**: The Vinkius platform handles horizontal scaling automatically. Whether your agent is pulling 10 or 10,000 subscriber records, Vinkius scales the MCP instance instantly.
- **Enterprise-Grade Compliance**: Securely bind your Marketing Cloud client IDs and secrets to the Vinkius vault. The LLM never touches your keys.
- **Vinkius Ecosystem**: Tap into the broader Vinkius marketplace to combine this SFMC server with other data enrichment MCPs seamlessly.

## Agent Capabilities

This server equips your AI with powerful marketing primitives:
- **`query_data_extension`**: A safe query interface for Data Extensions. Perfect for agents that need to analyze audience segments or retrieve personalized customer attributes before drafting an email.
- **`trigger_journey`**: Push users directly into active Salesforce Journeys. Enables the AI to respond to an event and immediately enroll a user in a nurture campaign.
- **`manage_subscriber`**: View, update, or unsubscribe contacts with built-in safeguards to respect communication preferences.

## 🌐 Deploy to Vinkius Edge

Get your Marketing Cloud MCP running globally in under a minute. We utilize Vinkius Edge for its unparalleled edge performance and security.

Execute the following command in your terminal:
```bash
npx mcpfusion deploy
```

You are ready to connect your LLM to the endpoint provided by Vinkius.

šŸ”— **[Get Started with the Salesforce Marketing Cloud MCP on Vinkius](https://vinkius.com/mcp/salesforce-marketing-cloud)**

## Local Contributions
Built on top of the `@mcpfusion/core` framework.
```bash
npm install
npm run dev
```

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: campaign creation, member addition, member retrieval, performance aggregation, status-based filtering, and name search. No two tools have overlapping purposes.

Naming Consistency3/5

Tool names follow a mixed convention: some start with a verb (sf_add_campaign_member, sf_create_campaign, sf_search_campaigns) while others start with a noun (sf_campaign_members, sf_campaign_performance, sf_campaigns_by_status). The prefix 'sf_' is consistent, but the lack of a uniform pattern reduces clarity.

Tool Count5/5

Six tools cover the core operations for a marketing campaign server (create, add members, query members, query campaigns by status, search by name, and aggregate performance). This is a well-scoped set without excess or deficiency.

Completeness3/5

The tool surface covers campaign creation and member addition, but lacks update and delete operations for both campaigns and campaign members. While common queries are supported, missing lifecycle actions force agents to rely on external mechanisms, creating minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues