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

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

## Facts

| | |
| --- | --- |
| Application | Sendoso |
| Category | Marketing Automation |
| AI tools | 12 |
| Authentication | Connects over OAuth |
| Needs your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Sendoso is connected

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

## Connect Sendoso in Elaichi

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

1. Open Connections, choose Add connection, and pick Sendoso.
2. Optionally set Share with, 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.

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

## Connect Sendoso to 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.

## Connect Sendoso to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Sendoso to 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.

## Connect Sendoso 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

Only Read is granted by default, which is not enough to call a Sendoso tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Sendoso through Elaichi

### Send a gift right after the call

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

### Turn a cold reply into a gift link

Sales Development. 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.

### Check how a campaign is being used

Marketing. Pull the list of sends for a Sendoso campaign, see who has sent what, and summarize which teams are actually using the budget.

### Collect an address before shipping

Customer Success. Start an address collection for a customer whose shipping details you do not have, so the physical gift goes to the right place.

### Find out who is in which group

Revenue Operations. List Sendoso users and team groups, spot who is missing from a group, and add a new user when someone joins the sales floor.

### Send a welcome gift to a new hire

People. Ship a physical gift or eGift to a new employee from the onboarding campaign, and confirm afterwards that the send went out.

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

## All 12 Sendoso tools

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

- **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.
- **List all Sendoso campaigns** (List). Get all active campaigns in Sendoso. Returns id, name, start_date, end_date, description, created_at, user_id, gift_id, status, delivery_type, currency, and ship_to_countries fields in the response.
- **Get single Sendoso campaign by ID** (Get). Get details about a specific campaign in Sendoso using id. Returns fields including id, name, start_date, description, status, delivery_type, and currency, which provide key information about the campaign configuration and activity.
- **List all Sendoso sends** (List). List all sends in Sendoso. Returns id, send_gid, type, subtype, currency, current_total_cost, status, created_at, touch, recipient, sender, sent_via, and status_updates for each send.
- **Create a Sendoso physical gift** (Create). Send a physical gift in Sendoso using recipient information such as name, email, and address. Returns success, message, and tracking_code in the response.
- **Create a Sendoso physical gift address collection** (Create). Create a new physical gift send request with address collection in Sendoso. Requires touch_id, name, email, no_address, confirm_address, address_confirmation_via, resume_with_unconfirmed_address, expire_after_days, hide_product_info, via, and via_from. Returns success status, message, and tracking_code in the response.
- **Create a Sendoso egift** (Create). Send an eGift via Sendoso Email. Requires touch_id, email, via, and via_from. Returns success status, message, tracking_code, and tracking_url to confirm and track the eGift delivery.
- **Create a Sendoso egift link** (Create). Generate one or more eGift links in Sendoso for recipients using touch_id, via, via_from, and recipient_users. Returns egift_link and recipient_email_or_phone_number for each recipient.