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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which campaigns are tagged for the spring launch?
Working in Account Engagement with Elaichi
-
List all Account Engagement account
-
List all Account Engagement bulk action errors
-
Get single Account Engagement bulk action by ID
How to connect Account Engagement to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Account Engagement MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Account Engagement MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Account Engagement through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Account Engagement is logged.
-
Marketing
Find the right campaign before a launch
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.
-
Marketing operations
Add a custom field in one ask
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.
-
Demand generation
Set up tracked links for a campaign
Create the custom redirects for a new campaign, check which ones already exist, and tag them so reporting lands in the right place.
-
Revenue operations
Connect a campaign to Salesforce
Tie an Account Engagement campaign to its Salesforce campaign so attribution lines up, and confirm which campaigns still have no connection.
-
Marketing operations
See why a bulk action failed
Pull up last night's bulk action, read every error it produced, and start a corrected run from the same conversation.
-
Sales
Check which campaigns are live before outreach
Ask what Account Engagement campaigns are running this month and which tags they carry, so a call references the right offer.
Try asking
- “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.”
What connecting Account Engagement gets you
6 screens from Elaichi, each doing one job for your Account Engagement account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about campaigns in plain language.
Get answers from live Account Engagement campaigns, custom fields and redirects, not stale exports.
Copy the endpoint
AI apps
One endpoint, every client, no shared key.
Claude, ChatGPT and Cursor reach Account Engagement through one governed endpoint, each person signed in.
Tool catalog
180 Account Engagement tools, no code to write.
Campaigns, custom fields, custom redirects and bulk actions, every method ready the moment you connect.
Toolboxes
Every team gets its own toolbox.
Marketing manages campaigns, ops handles custom fields, sales reads only what it needs.
Shared connections
Teammates work through one connection, credentials unseen.
One person connects Account Engagement once and shares it, nobody else touches the client secret.
Audit log
Every change in Account Engagement is named.
See who tagged a campaign, edited a custom field or ran a bulk action, and when.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Account Engagement digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
Account Engagement
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Account Engagement
Queued
Workflows
A schedule starts the work, you approve it.
New Account Engagement campaigns are fetched, grouped and drafted into a digest before anyone signs off.
Account Engagement health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Custom fields
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Marketing 34%
Demand gen 27%
Marketing ops 21%
Revenue ops 18%
Collections and dashboards
Numbers computed from campaigns, no model involved.
Four metrics, a 14 day chart of campaigns created and a team breakdown, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Account Engagement tools for your AI agents
180 tools are ready to call through Elaichi's MCP endpoint the moment you connect Account Engagement, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Account Engagement in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot