# Salesforce Marketing Cloud Engagement MCP connector

Connect Salesforce Marketing Cloud Engagement to Elaichi and your team can search, draft, update and approve email assets from Claude, ChatGPT, Cursor or Microsoft Copilot, each person inside their own access, every action logged.

Source: https://elaichi.ai/connectors/salesforcemarketingcloudengagement/

## Facts

| | |
| --- | --- |
| Application | Salesforce Marketing Cloud Engagement |
| Category | Marketing Automation |
| AI tools | 324 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Salesforce Marketing Cloud Engagement is connected

- Find the latest version of the spring sale email template.
- Which approvals are still waiting on the brand team?
- List every asset in the Q3 newsletters folder.

## Connect Salesforce Marketing Cloud Engagement in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Salesforce Marketing Cloud Engagement.
2. Optionally set Share with, then press Connect.
3. Paste your Salesforce Marketing Cloud Engagement app credentials. Salesforce Marketing Cloud Engagement authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Salesforce Marketing Cloud Engagement tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Salesforce Marketing Cloud Engagement MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Salesforce Marketing Cloud Engagement MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Salesforce Marketing Cloud Engagement MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Salesforce Marketing Cloud Engagement MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Salesforce Marketing Cloud Engagement MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Salesforce Marketing Cloud Engagement to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Salesforce Marketing Cloud Engagement tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Salesforce Marketing Cloud Engagement through Elaichi

### Find the right version of an email

Email marketing. Ask for the latest spring sale template or last month's newsletter and get the asset back from Salesforce Marketing Cloud Engagement, with its folder and status, without clicking through Content Builder.

### Draft a content block from a brief

Content. Paste a brief and have a new content block or email created in Salesforce Marketing Cloud Engagement, then tweak the copy in an existing asset when the product name changes.

### Check shared headers, footers and salutations

Brand. Pull up every header, footer and salutation your emails share and spot the one still carrying last year's logo or legal line.

### Tidy folders before the next quarter

Marketing operations. List the asset categories, create the folders for the coming campaigns, and archive the batch of assets nobody has touched since the last launch.

### See what is waiting for sign-off

Compliance. Ask which approvals are still open in Salesforce Marketing Cloud Engagement, who holds each approval role, and update an approval once the review is done.

### Bring back an archived asset

Marketing. When someone asks for the email that ran two summers ago, restore it from the archive and read it back in the same conversation.

## Elaichi vs Zapier MCP vs Composio for Salesforce Marketing Cloud Engagement

All three can connect Salesforce Marketing Cloud Engagement to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Salesforce Marketing Cloud Engagement tools | Allow or restrict single Salesforce Marketing Cloud Engagement tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Salesforce Marketing Cloud Engagement call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Salesforce Marketing Cloud Engagement to Claude?

Connect Salesforce Marketing Cloud Engagement in Elaichi first, where you enter the app credentials from your Marketing Cloud account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Salesforce Marketing Cloud Engagement is ready to use in Claude.

### Does Salesforce Marketing Cloud Engagement work with ChatGPT and Cursor as well as Claude?

Yes. One Salesforce Marketing Cloud Engagement connection in Elaichi works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Every client points at the same endpoint, https://api.elaichi.ai/mcp, so you connect Salesforce Marketing Cloud Engagement once and use it everywhere.

### What can an AI agent actually do with my Salesforce Marketing Cloud Engagement content?

An agent can look through your Salesforce Marketing Cloud Engagement assets, find the email, template or content block you mean, read it, draft a new one, or update the copy in an existing one. It can list the folders your content lives in, show the headers, footers and salutations your emails share, archive or restore assets, and tell you which approvals are still waiting and who needs to sign off. Short, specific asks work best, such as the name of a campaign or a folder rather than a long description.

### Does connecting Salesforce Marketing Cloud Engagement give the AI my whole account?

No. Everything an agent does in Salesforce Marketing Cloud Engagement runs inside the access of the person who signed in, so it sees the folders, assets and approvals that person can already open and nothing more. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

### Can my team share one Salesforce Marketing Cloud Engagement connection?

Yes. One person connects Salesforce Marketing Cloud Engagement in Elaichi and shares it with the marketing team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created or changed an asset, not the account that holds the connection.

### Can I stop an agent from deleting or changing things in Salesforce Marketing Cloud Engagement?

Yes. In Elaichi you can restrict any single action for Salesforce Marketing Cloud Engagement, such as deleting a folder or updating an approval, on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Salesforce Marketing Cloud Engagement connection when someone leaves?

When you offboard someone in Elaichi their access to Salesforce Marketing Cloud Engagement ends at once, in every client they used. A connection shared with the team keeps working for everyone else. If you want to remove Salesforce Marketing Cloud Engagement entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Salesforce Marketing Cloud Engagement MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Salesforce Marketing Cloud Engagement is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Salesforce Marketing Cloud Engagement?

Yes. Both let Claude, ChatGPT or Cursor use Salesforce Marketing Cloud Engagement. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Salesforce Marketing Cloud Engagement call.

### How is Elaichi different from Composio for Salesforce Marketing Cloud Engagement?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Salesforce Marketing Cloud Engagement: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 324 Salesforce Marketing Cloud Engagement tools

Every tool below is callable through https://api.elaichi.ai/mcp once Salesforce Marketing Cloud Engagement is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Salesforce Marketing Cloud Engagement account settings** (List). Retrieve information about settings that apply to your account. Retrieves the status of the Einstein Data Pooling. To retrieve the status of this business rule for all business units in an enterprise, include the entire_enterprise=true query parameter (GET /platform/v1/settings).
- **List all Salesforce Marketing Cloud Engagement approval roles** (List). Retrieves a list of roles for a given approval item as well as the users assigned to those roles (GET /hub/v1/approvals-v2/{id}/roles). Required: approval_id.
- **List all Salesforce Marketing Cloud Engagement approval settings** (List). Retrieves the approvals settings based on the current user context (GET /hub/v1/approvals-v2/settings).
- **Salesforce Marketing Cloud Engagement approval settings bulk update** (Update). Updates the approvals settings with the values provided in the request body. Currently only the EnableEmailApprovals setting can be updated using the API (PATCH /hub/v1/approvals-v2/settings).
- **Create a Salesforce Marketing Cloud Engagement approval** (Create). Create Approval and an associated workflow item (POST /hub/v1/approvals-v2).
- **Get single Salesforce Marketing Cloud Engagement approval by ID** (Get). Get Approval item for current user (GET /hub/v1/approvals-v2/{id}). Required: id.
- **List all Salesforce Marketing Cloud Engagement approvals** (List). Get all Approval items (GET /hub/v1/approvals-v2). The connector pages through all results with $page and $pageSize.
- **Update a Salesforce Marketing Cloud Engagement approval by ID** (Update). Update Approval item (PATCH /hub/v1/approvals-v2/{id}). Required: id.
- **Salesforce Marketing Cloud Engagement asset archives bulk update** (Update). Archive an asset. When you archive an asset, Marketing Cloud Engagement removes it from availability for queries, triggered sends, and journeys, as if the asset were deleted (PATCH /asset/v1/content/assets/{id}/archive). Required: asset_id.
- **List all Salesforce Marketing Cloud Engagement asset categories** (List). Get categories. Returns one or more Content Builder categories that are owned by or reside in your MID. To request categories that have been shared with your MID, add a scope parameter to the call (GET /asset/v1/content/categories). The connector pages through all results with $page and $pagesize.
- **Create a Salesforce Marketing Cloud Engagement asset category** (Create). Create category. Creates a category in Content Builder. A category is a folder that contains assets (POST /asset/v1/content/categories).
- **Get asset category by ID** (Get). Get category by ID. Returns one Content Builder category by ID (GET /asset/v1/content/categories/{categoryId}). Required: id.
- **Update a Salesforce Marketing Cloud Engagement asset category by ID** (Update). Update category. Updates a Content Builder category (PUT /asset/v1/content/categories/{categoryId}). Required: id.
- **Delete a Salesforce Marketing Cloud Engagement asset category by ID** (Delete). Delete category. Deletes a Content Builder category (DELETE /asset/v1/content/categories/{categoryId}). Required: id.
- **Get asset channel view by ID** (Get). Get channel view. Returns the compiled HTML for a requested channel view of an asset (GET /asset/v1/content/assets/{id}/channelviews/{viewName}). Required: asset_id, id.
- **List all Salesforce Marketing Cloud Engagement asset files** (List). Get asset file. Gets the binary file for an asset (GET /asset/v1/content/assets/{id}/file). Required: asset_id.
- **List all asset headers footers** (List). Get email salutations. Retrieves the header and footer of an email asset by specifying the asset ID (GET /asset/v1/content/assets/{id}/salutations). Required: asset_id.
- **Create a Salesforce Marketing Cloud Engagement asset query** (Create). Get assets by advanced query. Use an advanced query to retrieve a collection of assets (POST /asset/v1/content/assets/query).
- **Salesforce Marketing Cloud Engagement asset restores bulk update** (Update). Restore asset. Restore an asset hidden by a prior archive operation, and make it available again for queries, triggered sends, journeys, and other operations (PATCH /asset/v1/content/assets/{id}/restore). Required: asset_id.
- **List all Salesforce Marketing Cloud Engagement asset salutations** (List). Get default salutations. Retrieves the default header and footer for an account (GET /asset/v1/content/assets/salutations).
- **List all Salesforce Marketing Cloud Engagement assets** (List). Get assets by simple filter. Retrieve a collection of assets by applying basic filters and sorting rules (GET /asset/v1/content/assets). The connector pages through all results with $page and $pagesize.
- **Create a Salesforce Marketing Cloud Engagement asset** (Create). Create asset. Creates a new asset (POST /asset/v1/content/assets).
- **Get single Salesforce Marketing Cloud Engagement asset by ID** (Get). Get asset by ID. Retrieves an asset by its ID (GET /asset/v1/content/assets/{id}). Required: id.
- **Update a Salesforce Marketing Cloud Engagement asset by ID** (Update). Update an asset. Modify the properties of an existing asset (PUT /asset/v1/content/assets/{id}). Required: id.
- **Salesforce Marketing Cloud Engagement assets partial update** (Update). Patch an asset. Modify the properties of an asset deleted in the last 30 days (PATCH /asset/v1/content/assets/{id}). Required: asset_id.
- **Delete a Salesforce Marketing Cloud Engagement asset by ID** (Delete). Delete an asset. Deletes an asset (DELETE /asset/v1/content/assets/{id}). Required: id.
- **List all async request results** (List). Retrieve the results of a request to asynchronously insert rows into a data extension. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (GET /data/v1/async/{requestId}/results). Required: request_id.
- **List all async request statuses** (List). Retrieve the status of a request to asynchronously insert rows into a data extension. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (GET /data/v1/async/{requestId}/status). Required: request_id.
- **List all Salesforce Marketing Cloud Engagement audit events** (List). GET /data/v1/audit/auditEvents. Retrieve logged Audit Trail audit events for the current account and its child accounts. Logins are audited at the enterprise level. Timestamps for Audit Trail data use the US Central Standard Time (GMT-6, CST) timezone (GET /data/v1/audit/auditEvents). The connector pages through all results with $page and $pagesize.
- **List all Salesforce Marketing Cloud Engagement auth discovery** (List). Get base URLs. Obtain the base URLs for the Marketing Cloud Auth and REST APIs. These application-specific URLs are unique to your Marketing Cloud account and installed package (GET /v2/discovery). Required: clientId, resource.
- **Get automation definition by ID** (Get). Retrieve an automation definition, including its steps and activities, by providing its ID. Each activity in the steps array includes an objectTypeId that identifies the type of activity. For the list of activity types, see Automation Activity Types (GET /automation/v1/automations/automation/definition/{id}). Required: id.
- **Update automation definition by ID** (Update). Update the name, description, or key of an automation definition by providing its ID. Include only the properties that you want to change. If another automation in your business unit already uses the name or key, the API returns a 409 response. This operation changes only the name, description, and key (PATCH /automation/v1/automations/automation/definition/{id}). Required: id.
- **Delete automation definition by ID** (Delete). Delete an automation definition by providing its ID. You can’t delete an automation while it’s running. In that case, the API returns a 409 response (DELETE /automation/v1/automations/automation/definition/{id}). Required: id.
- **List all automation definitions by key** (List). Retrieve an automation definition, including its steps and activities, by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Get an automation definition (GET /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
- **Automation definitions by key bulk update** (Update). Update the name, description, or key of an automation definition by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Update an automation definition (PATCH /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
- **Automation definitions by key bulk delete** (Delete). Delete an automation definition by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Delete an automation definition (DELETE /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
- **Update automation file trigger by ID** (Update). Activate or deactivate an automation file trigger by providing its ID. ## Required Scopes To update the status of a trigger request, your API user must have this permission: - Automation Write (automations_write) (PATCH /automation/v1/automations/filetrigger/{id}). Required: id.
- **Automation file triggers by key bulk update** (Update). Activate or deactivate an automation file trigger by providing its key. ## Required Scopes To update the status of a trigger request, your API user must have this permission: - Automation Write (automations_write) (PATCH /automation/v1/automations/filetrigger/key:{key}). Required: filetrigger_key.
- **List all Salesforce Marketing Cloud Engagement automation folders** (List). Retrieve a list of all folders in the account. ## Required Scopes To retrieve automation folders, your API user must have this permission: - Automation Read (automations_read) (GET /automation/v1/folders). Required: filter.
- **Create a Salesforce Marketing Cloud Engagement automation run once** (Create). Run all activities in an automation one time by specifying its ID. ## Required Scopes To run the activities in an automation, your API user must have these permissions: - Automation Execute (automations_execute) (POST /automation/v1/automations/{id}/actions/runallonce). Required: automation_id.
- **Create automation run once by key** (Create). Run all activities in an automation one time by specifying its external key. ## Required Scopes To run the activities in an automation, your API user must have these permissions: - Automation Execute (automations_execute) (POST /automation/v1/automations/key:{key}/actions/runallonce). Required: automation_key.
- **Create a Salesforce Marketing Cloud Engagement automation start** (Create). Start an automation by providing its ID. Start a one-time run of an automation. In the request body, list the activities to include in the run by their IDs. To get the activity IDs, retrieve the automation (POST /automation/v1/automations/{id}/actions/start). Required: automation_id.
- **Create automation starts by key** (Create). Start an automation by providing its external key. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Start an automation (POST /automation/v1/automations/key:{key}/actions/start). Required: automation_key.
- **Get automation trigger status by ID** (Get). Check the status for a specified Trigger API requestID. &gt; Note &gt; &gt; To see the automation details, make sure that the request’s file details meet the criteria for exactly one automation trigger configuration. See _Salesforce Help_: Configure a Trigger Automation (GET /automation/v1/automations/trigger/status/{requestId}). Required: id.
- **Create automation trigger validation** (Create). Validate the settings for a new automation trigger. Check the settings for an automation trigger start source before you create the automation (POST /automation/v1/automations/trigger/validate).
- **Create automation trigger validations by ID** (Create). Validate the trigger settings for an existing automation by providing its ID. Check updated settings for the trigger start source of an existing automation (POST /automation/v1/automations/trigger/validate/{id}). Required: validate_id.
- **Create automation trigger validations by key** (Create). Validate the trigger settings for an existing automation by providing its external key. Check updated settings for the trigger start source of an existing automation, identified by its external key. This operation performs the same checks as Validate an automation trigger by ID (POST /automation/v1/automations/trigger/validate/key:{key}). Required: validate_key.
- **Create a Salesforce Marketing Cloud Engagement automation trigger** (Create). Start an automation that uses a trigger start source. When you upload a file, the Trigger API request passes the file details for Automation Studio to evaluate. You can queue a maximum of 200 Trigger requests at a time in each member ID (MID) (POST /automation/v1/automations/trigger).
- **Update automation trigger by ID** (Update). Activate or Deactivate an Automation Trigger. If no automation has the specified ID, or if the automation doesn’t use a trigger start source, the API returns a 404 response (PATCH /automation/v1/automations/trigger/{id}). Required: id.
- **Automation triggers by key bulk update** (Update). Activate or deactivate an automation trigger by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Update automation trigger (PATCH /automation/v1/automations/trigger/key:{key}). Required: trigger_key.
- ...and 274 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
