# Account Engagement MCP connector

The Account Engagement connector brings campaigns, custom fields, custom redirects and bulk actions into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, where each person works inside their own Account Engagement access and every call is logged.

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

## Facts

| | |
| --- | --- |
| Application | Account Engagement |
| Category | Marketing Automation |
| AI tools | 180 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| 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 Account Engagement is connected

- Which campaigns are tagged for the spring launch?
- Create a custom redirect for the partner webinar landing page.
- Show me the errors from last night's bulk action.

## Connect Account Engagement in Elaichi

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

1. Open Connections, choose Add connection, and pick Account Engagement.
2. Optionally set Share with, then press Connect.
3. Supply your own Account Engagement app, then approve. Account Engagement needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

## Account 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.

## Account 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`.

## Account 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.

## Account 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.

## Account 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 Account 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 Account 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 Account Engagement through Elaichi

### Find the right campaign before a launch

Marketing. Ask for every Account Engagement campaign tagged for the quarter, read the details of the one you need, and fix a wrong tag without opening the app.

### Add a custom field in one ask

Marketing operations. Describe the field the sales team keeps asking for and have it created in Account Engagement, then rename or retire old custom fields the same way.

### Set up tracked links for a campaign

Demand generation. Create the custom redirects for a new campaign, check which ones already exist, and tag them so reporting lands in the right place.

### Connect a campaign to Salesforce

Revenue operations. Tie an Account Engagement campaign to its Salesforce campaign so attribution lines up, and confirm which campaigns still have no connection.

### See why a bulk action failed

Marketing operations. Pull up last night's bulk action, read every error it produced, and start a corrected run from the same conversation.

### Check which campaigns are live before outreach

Sales. Ask what Account Engagement campaigns are running this month and which tags they carry, so a call references the right offer.

## Elaichi vs Zapier MCP vs Composio for Account Engagement

All three can connect Account 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 Account Engagement tools | Allow or restrict single Account 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 Account 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 Account Engagement to Claude?

Connect Account Engagement in Elaichi, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Account Engagement connects over OAuth and asks you to register an OAuth application inside Account Engagement yourself, so one person brings a client ID and secret once and enters them in Elaichi. After that, everyone on the team signs in to Account Engagement as themselves and nobody handles the client ID or secret again.

### Does Account Engagement work with ChatGPT and Cursor as well as Claude?

Yes. Once Account Engagement is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Account Engagement once and every client picks it up.

### What can an AI agent actually do with my Account Engagement data?

It can list and read Account Engagement campaigns, tag and untag them, and connect a campaign to its Salesforce counterpart. It can create, update and delete custom fields and custom redirects, start bulk actions and read the errors a bulk action produced. Short, concrete asks such as "tag the spring webinar campaign as Q2" work better than long paragraphs.

### Does connecting Account Engagement give the AI access to everything in my account?

No. Every call into Account Engagement runs as the person who signed in, so the agent sees only the campaigns, custom fields and redirects that person could already open. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Account Engagement itself allows.

### Can my team share one Account Engagement connection?

Yes. One person connects Account Engagement in Elaichi and shares it with a team, and nobody else ever sees the client ID or secret. Each teammate still signs in to Account Engagement as themselves, so the audit log names the actual person behind every campaign change or bulk action.

### Can I stop an agent from deleting or changing things in Account Engagement?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting custom fields or custom redirects in Account Engagement for a role or for one person while leaving reading and tagging open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Account Engagement connection when someone leaves?

Offboarding the person in Elaichi ends their access to Account Engagement through every client at once. A connection they shared keeps working for everyone else on the team. If you ever want Account Engagement gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. Account 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 Account Engagement?

Yes. Both let Claude, ChatGPT or Cursor use Account 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 Account Engagement call.

### How is Elaichi different from Composio for Account 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 Account 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 180 Account Engagement tools

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

- **List all Account Engagement account** (List). Use the account resource to learn about the current user's Account Engagement instance, such as the address, website URL, and account level. Needs the Admin &gt; Account &gt; Edit Settings ability.
- **List all Account Engagement bulk action errors** (List). Download the CSV error report of a finished bulk action. Required: bulk_action_id.
- **Create a Account Engagement bulk action** (Create). Start a bulk action (move prospects to the recycle bin, or permanently delete recycle-bin prospects) from a CSV of ids. Multipart: input = JSON {object: Prospect, bulkAction: delete|permanentdelete, status: Ready|Paused, sendSystemEmail}, file = CSV with header id.
- **Get single Account Engagement bulk action by ID** (Get). Read a bulk action and its progress.
- **List all Account Engagement bulk actions** (List). Query bulk actions; the connector follows nextPageToken.
- **Update a Account Engagement bulk action by ID** (Update). Pause (status Paused), resume (status Ready) or cancel (status Cancelled) a bulk action that has not reached a final status.
- **Create a Account Engagement campaign salesforce connection** (Create). Associates an Account Engagement campaign to a Salesforce campaign. The field salesforceCampaignId is required. Needs the Marketing &gt; Other &gt; Campaigns &gt; Create ability.
- **Get single Account Engagement campaign by ID** (Get). Read one campaign by id. Needs the Marketing &gt; Other &gt; Campaigns &gt; View ability.
- **List all Account Engagement campaigns** (List). An Account Engagement campaign tracks the first interaction that a person has with your online marketing materials. Query campaigns; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Marketing &gt; Other &gt; Campaigns &gt; View ability.
- **Account Engagement campaigns tag** (Action). Adds a Tag to the Campaign object, which creates a TaggedObject. Needs the Marketing &gt; Other &gt; Campaigns &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement campaigns untag** (Action). Remove a tag from a Campaign object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Marketing &gt; Other &gt; Campaigns &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Get single Account Engagement custom field by ID** (Get). Read one custom field by id. Needs the Prospect &gt; Prospects &gt; Configure Fields ability.
- **Create a Account Engagement custom field** (Create). Create a custom field. Required: name, fieldId, type. Needs the Prospect &gt; Prospects &gt; Configure Fields ability.
- **Update a Account Engagement custom field by ID** (Update). Update a custom field; omitted fields stay unchanged. Needs the Prospect &gt; Prospects &gt; Configure Fields ability.
- **Delete a Account Engagement custom field by ID** (Delete). Delete a custom field (some objects go to the recycle bin). Needs the Prospect &gt; Prospects &gt; Configure Fields ability.
- **List all Account Engagement custom fields** (List). Use custom fields to capture and track more data about your prospects. Query custom fields; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Prospect &gt; Prospects &gt; Configure Fields ability.
- **Account Engagement custom fields tag** (Action). Adds a Tag to the Custom Field object, which creates a TaggedObject. Needs the Prospect &gt; Prospects &gt; Configure Fields AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement custom fields untag** (Action). Remove a tag from a Custom Field object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Prospect &gt; Prospects &gt; Configure Fields AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Get single Account Engagement custom redirect by ID** (Get). Read one custom redirect by id. Needs the Marketing &gt; Content &gt; Custom Redirects &gt; View ability.
- **Create a Account Engagement custom redirect** (Create). Create a custom redirect. Required: name, campaignId, destinationUrl. Needs the Marketing &gt; Content &gt; Custom Redirects &gt; Create ability.
- **Update a Account Engagement custom redirect by ID** (Update). Update a custom redirect; omitted fields stay unchanged. Needs the Marketing &gt; Content &gt; Custom Redirects &gt; Create ability.
- **Delete a Account Engagement custom redirect by ID** (Delete). Delete a custom redirect (some objects go to the recycle bin). Needs the Marketing &gt; Content &gt; Custom Redirects &gt; Delete ability.
- **List all Account Engagement custom redirects** (List). Track links on your website or third-party site with Account Engagement’s custom redirects. Query custom redirects; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Marketing &gt; Content &gt; Custom Redirects &gt; View ability.
- **Account Engagement custom redirects tag** (Action). Adds a Tag to the Custom Redirect object, which creates a TaggedObject. Needs the Marketing &gt; Content &gt; Custom Redirects &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement custom redirects untag** (Action). Remove a tag from a Custom Redirect object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Marketing &gt; Content &gt; Custom Redirects &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Get single Account Engagement dynamic content variation by ID** (Get). Read one dynamic content variation by id. Needs the Content &gt; Dynamic Content &gt; View ability.
- **List all Account Engagement dynamic content variations** (List). Dynamic content personalizes parts of your website based on what you know about a viewer. Query dynamic content variations; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Content &gt; Dynamic Content &gt; View ability.
- **Create a Account Engagement dynamic content variation** (Create). Create a dynamic content variation. Required: dynamicContentId, operator, value1. Needs the Content &gt; Dynamic Content &gt; Create ability.
- **Get single Account Engagement dynamic content by ID** (Get). Read one dynamic content by id. Needs the Content &gt; Dynamic Content &gt; View ability.
- **List all Account Engagement dynamic contents** (List). Dynamic content personalizes parts of your website based on what you know about a viewer. Query dynamic contents; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Content &gt; Dynamic Content &gt; View ability.
- **Create a Account Engagement dynamic content** (Create). Create a dynamic content. Required: name, basedOnProspectApiFieldId. Needs the Content &gt; Dynamic Content &gt; Create ability.
- **Account Engagement dynamic contents tag** (Action). Adds a Tag to the Dynamic Content object, which creates a TaggedObject. Needs the Content &gt; Dynamic Content &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement dynamic contents untag** (Action). Remove a tag from a Dynamic Content object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Content &gt; Dynamic Content &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Create a Account Engagement email cms copy** (Create). Copy a sent email to your Salesforce CMS Marketing workspace. Needs the Marketing &gt; Emails &gt; Sent &gt; Copy to CMS ability.
- **Create a Account Engagement email template** (Create). Create a email template. Required: name, subject, isOneToOneEmail, isAutoResponderEmail, isDripEmail, isListEmail, textMessage, htmlMessage, senderOptions, trackerDomainId, folderId, type, campaignId. Needs the Marketing &gt; Emails &gt; Email Templates &gt; Create ability.
- **Get single Account Engagement email template by ID** (Get). Read one email template by id. Needs the Marketing &gt; Emails &gt; Email Templates &gt; View ability.
- **Update a Account Engagement email template by ID** (Update). Update a email template; omitted fields stay unchanged. Needs the Marketing &gt; Emails &gt; Email Templates &gt; Create ability.
- **Delete a Account Engagement email template by ID** (Delete). Delete a email template (some objects go to the recycle bin). Needs the Marketing &gt; Emails &gt; Email Templates &gt; Delete ability.
- **List all Account Engagement email templates** (List). Use an email template to design a reusable email layout for your engagement programs, autoresponders, one-to-one emails, and list emails. Query email templates; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Marketing &gt; Emails &gt; Email Templates &gt; View ability.
- **Account Engagement email templates tag** (Action). Adds a Tag to the Email Template object, which creates a TaggedObject. Needs the Marketing &gt; Emails &gt; Email Templates &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement email templates untag** (Action). Remove a tag from an Email Template object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Marketing &gt; Emails &gt; Email Templates &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Create a Account Engagement email** (Create). Create a email. Required: name, campaignId, prospectId. Needs the Marketing &gt; Emails &gt; Emails &gt; Send One-to-one ability.
- **Get single Account Engagement email by ID** (Get). Read one email by id. Needs the Marketing &gt; Emails &gt; Emails &gt; View ability.
- **List all Account Engagement emails** (List). Use email resources to send emails to prospects, and to learn how prospects responded to the emails. Query emails; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Marketing &gt; Emails &gt; Emails &gt; View ability.
- **Account Engagement emails tag** (Action). Adds a Tag to the Email object, which creates a TaggedObject. Needs the Marketing &gt; Emails &gt; Emails &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **Account Engagement emails untag** (Action). Remove a tag from an Email object. When you remove a tag, the associated TaggedObject record is deleted. Needs the Marketing &gt; Emails &gt; Emails &gt; Create AND Marketing &gt; Segmentation &gt; Tags &gt; Create ability.
- **List all Account Engagement engagement studio program structures** (List). An encrypted and base64 encoded Engagement Studio Program can be downloaded using the Download Program Structure endpoint. This file holds an Engagement Studio Program structure without specific information from the source (such as object IDs). A downloaded program structure file is required to... Needs the Marketing &gt; Engagement Studio...
- **Get single Account Engagement engagement studio program by ID** (Get). Read one engagement studio program by id. Needs the Marketing &gt; Engagement Studio &gt; Engagement Program &gt; View ability.
- **List all Account Engagement engagement studio programs** (List). The Engagement Studio Program API provides a programmatic way to copy Engagement Studio Programs across different Orgs and Business Units. Query engagement studio programs; the connector follows nextPageToken (up to 1,000 per page, 100,000 records in total). Needs the Marketing &gt; Engagement Studio &gt; Engagement Program &gt; View ability.
- **Create a Account Engagement engagement studio program** (Create). Create a engagement studio program. Required: name. Needs the Marketing &gt; Engagement Studio &gt; Engagement Program &gt; Create/Edit ability.
- ...and 130 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
