Marketing Automation
Sendoso MCP connector
The Sendoso connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent look up Sendoso campaigns, sends, users, and groups, and send physical gifts, eGifts, and eGift links inside the access of whoever signed in.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Sendoso to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Sendoso once
-
Open Connections, choose Add connection, and pick Sendoso.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Sendoso app, then approve. Sendoso needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Sendoso to 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.
Connect Sendoso to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Sendoso to 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.
Connect Sendoso 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.
Use cases
What teams do with Sendoso through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Send a gift right after the call
Ask for a thank-you eGift or a physical gift to the prospect you just spoke with, picked from the campaign your team already runs, without opening Sendoso.
-
Sales Development
Turn a cold reply into a gift link
Generate an eGift link from a Sendoso campaign and drop it into the follow-up email, so the recipient claims it on their own terms.
-
Marketing
Check how a campaign is being used
Pull the list of sends for a Sendoso campaign, see who has sent what, and summarize which teams are actually using the budget.
-
Customer Success
Collect an address before shipping
Start an address collection for a customer whose shipping details you do not have, so the physical gift goes to the right place.
-
Revenue Operations
Find out who is in which group
List Sendoso users and team groups, spot who is missing from a group, and add a new user when someone joins the sales floor.
-
People
Send a welcome gift to a new hire
Ship a physical gift or eGift to a new employee from the onboarding campaign, and confirm afterwards that the send went out.
Try asking
- “Which Sendoso campaigns had the most sends last month?”
- “Send an egift link to the three contacts I closed.”
- “List Sendoso sends from my team still awaiting address collection.”
AI tools
Sendoso tools for your AI agents
12 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sendoso, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Sendoso gets you
6 screens from the product, each doing one job for your Sendoso account.
The agent
Ask about Sendoso sends in plain language.
Questions about campaigns, sends and gifts answered from live Sendoso records.
- campaigns
- sends
- egift links
- users
Ask Elaichi to work across your apps.
Which Sendoso campaigns had the most sends last month?
Send an egift link to the three contacts I closed.
List Sendoso sends from my team still awaiting address collection.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Sendoso here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
12 Sendoso tools ready without custom code.
Campaigns, sends, egift links, users and groups, every method already mapped.
- List all Sendoso users
- Create a Sendoso user
- List all Sendoso me
- List all Sendoso groups
Toolboxes
Every team gets its own Sendoso toolbox.
Scope campaign tools to marketing and gift sends to sales, separately.
- Sales
- Marketing
- Customer success
- Field events
Shared connections
Teammates send gifts without seeing a credential.
See who connected each Sendoso account and which teams and members use it.
- Sales EMEA
- Sales AMER
- Marketing
- Customer success
Audit log
Every Sendoso send has a name on it.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Sendoso sends into an approved digest.
Fetch sends, group them, draft a digest, a person approves, post back.
Sendoso digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch campaigns
Sendoso
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 Michael Brennan
Approve Deny -
Post the digest
Sendoso
Queued
Collections and dashboards
Sendoso gift numbers arrive before anyone asks.
Four metrics, 14 days of sends created and a team breakdown, refreshed hourly.
Sendoso health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Sends
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Marketing 21%
Customer success 18%
FAQ
Frequently asked questions
How do I connect Sendoso to Claude?
Connecting Sendoso to Claude takes two steps: connect Sendoso in Elaichi, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Sendoso connects over OAuth, but it needs an OAuth application registered inside your own Sendoso account, so somebody on your side brings a client ID and secret once when setting up the connector. After that, each person simply signs in to Sendoso with their own login when Claude asks, and nobody else handles those details again.
Does Sendoso work with ChatGPT and Cursor as well as Claude?
Yes. Once Sendoso is connected in Elaichi, the same endpoint https://api.elaichi.ai/mcp works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Sendoso once and every client picks it up.
What can an AI agent actually do with my Sendoso data?
Through the Sendoso connector an agent can list your campaigns and open a single campaign, see the sends that have gone out, and look up users, groups, and who belongs to each team group. It can also do the work of sending: create a physical gift, start an address collection for a recipient, send an eGift, or generate an eGift link, and create a new Sendoso user. It cannot delete campaigns, sends, or users through this connector.
Does connecting Sendoso give the AI access to every campaign and send in our account?
No. Every call to Sendoso runs as the person who signed in, so an agent only sees the campaigns, sends, and groups that person can already see in Sendoso, and only sends gifts from budgets that person can use. Elaichi can narrow that access further, for example to read-only, but it can never widen it beyond what Sendoso itself allows that person.
Can I stop an agent from sending gifts or changing things in Sendoso?
Yes. Restrictions in Elaichi work per action, so you can allow an agent to read Sendoso campaigns and sends while blocking it from creating physical gifts, eGifts, eGift links, or new users. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a Sendoso connection when someone leaves?
When you offboard a person in Elaichi, their access to Sendoso through every client ends at once. A shared Sendoso connection keeps working for everyone else on the team, so nobody loses the ability to send gifts. If you want to remove Sendoso entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Sendoso in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.