Skip to content

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.

1

In Elaichi

Connect Sendoso once

  1. Open Connections, choose Add connection, and pick Sendoso.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

sendoso
Sendoso
Attentive
Beamer
beehiiv
Bird
Buffer
2

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.

Sendoso MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

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

    Sign in and approve.

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

Sendoso MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

Sendoso MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 12 Sendoso tools below

Compare

Elaichi vs Zapier MCP vs Composio for Sendoso

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

Elaichi compared with Zapier MCP and Composio for Sendoso, by what to check
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 Sendoso tools Allow or restrict single Sendoso 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 Sendoso 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 $15 per user per month. 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.

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Sendoso users List List all active users in Sendoso organization. Returns current_page, per_page, total_users, and users array with id, first_name, last_name, email, and team_group_id.
Create a Sendoso user Create Create a new user invitation in Sendoso for a specific team group using team_group_id. Returns success status, message, receiver_email, team_group_id, user_role, invitation_status, and expires_at.
List all Sendoso me List Get current user details in Sendoso. Returns id, first_name, last_name, email, role, balance, and team_balance in the response.
List all Sendoso groups List List all active team groups in Sendoso. Returns group details including id, name, budget, team_id, and timestamps. Supports pagination through page and per_page query parameters.
List all Sendoso team group users List Get all users for a specific team group in Sendoso. Requires team_group_id. Returns id, first_name, last_name, email, balance, sandbox, team_group_id, team_id, and key for each user.

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
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Sendoso · gift sends to prospects

Sendoso starter 18 Mar 4, 2026

Marketing toolbox

Sendoso · campaigns and egift links

— 9 Mar 2, 2026

Customer success toolbox

Sendoso · renewal and thank you gifts

— 24 Feb 27, 2026

Field events toolbox

Sendoso · physical gifts and address collection

Sendoso starter 6 Feb 19, 2026

Partnerships toolbox

Sendoso · partner egifts and campaigns

— 31 Jan 30, 2026

Operations toolbox

Sendoso · users, groups and send reporting

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
SE

Sendoso (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SE

Sendoso (Sales AMER)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SE

Sendoso (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SE

Sendoso (Customer success)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
SE

Sendoso (Field events)

Connected by Ryan Hayes

Personal • Active Not shared
SE

Sendoso (Partnerships)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Sendoso Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Sendoso Campaigns Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Sendoso Campaigns List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch campaigns

    Sendoso

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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 my team share one Sendoso connection?

Yes. One person connects Sendoso in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret, or any credential. Each teammate still signs in to Sendoso as themselves, so every gift sent and every campaign viewed is logged under that person's name.

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.

Does the Sendoso MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Sendoso 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, 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 Sendoso?

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

How is Elaichi different from Composio for Sendoso?

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 Sendoso: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Sendoso in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.