# Reachdesk MCP connector

The Reachdesk connector lets Claude, ChatGPT, Cursor, Microsoft Copilot or Elaichi's own agent look up contacts, send gifts and direct mail, and review sends and transactions in Reachdesk, with every action logged under the person who asked.

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

## Facts

| | |
| --- | --- |
| Application | Reachdesk |
| Category | Sales Enablement |
| AI tools | 9 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| 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 Reachdesk is connected

- Send the Q3 welcome campaign to Dana Ortiz at Northwind
- List every Reachdesk send from this week and its status
- Show last month's transactions grouped by campaign

## Connect Reachdesk in Elaichi

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

1. Open Connections, choose Add connection, and pick Reachdesk.
2. Optionally set Share with, then press Connect.
3. Paste a Reachdesk API key. One person generates a token in Reachdesk and pastes it once. Everyone else works through Share with, and never sees it.

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

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

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

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

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

## Reachdesk 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 Reachdesk 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 Reachdesk 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 Reachdesk through Elaichi

### Send a gift right after the call

Sales. Ask for a Reachdesk campaign send to the prospect you just spoke with, so the gift lands while the conversation is still fresh. The agent finds the contact and creates the send for you.

### Launch a bulk send to an event list

Marketing. Hand over the attendee list and have a bulk send created in Reachdesk in one ask, instead of uploading rows by hand before the event.

### Check whether the renewal gift arrived

Customer Success. Ask for a specific Reachdesk send by its ID and get its status back without opening the app, then follow up with the customer at the right moment.

### See every send from the last quarter

Sales Operations. List all Reachdesk sends and see which reps are using their gifting budget and which organizations have been touched, ready to paste into the pipeline review.

### Reconcile gifting spend against transactions

Finance. Pull the list of Reachdesk transactions for the month and match it to the gifting budget before close, with no export and no spreadsheet cleanup.

### Raise a GDPR request for a contact

Legal. Create a GDPR request in Reachdesk when a contact asks for their data to be removed, and check on its progress later by its ID.

## Elaichi vs Zapier MCP vs Composio for Reachdesk

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

Connect Reachdesk in Elaichi first, which only asks you to paste a Reachdesk API key, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi as yourself and Reachdesk is ready to use in about twenty minutes end to end.

### Does Reachdesk work with ChatGPT and Cursor as well as Claude?

Yes. Reachdesk is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing to set up again per client.

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

It can look up Reachdesk contacts and organizations, create a campaign send to one person or a bulk send to a whole list, check on a single send, list every send and every transaction, and raise or check a GDPR request. Rather than seeing a list of Reachdesk tools, Claude searches for the right one each time, so short concrete asks like "send the welcome campaign to Dana Ortiz" work better than long paragraphs.

### Does connecting Reachdesk give the AI access to my whole account?

No. Every call to Reachdesk runs inside the access of the person who signed in, so the agent sees the contacts, sends and transactions that person can already see and nothing more. Elaichi can narrow that access with restrictions, and it can never widen it beyond what Reachdesk itself allows that person.

### Can my team share one Reachdesk connection?

Yes. One person connects Reachdesk in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every Reachdesk send and lookup in the audit log is tied to the person who asked for it.

### Can I stop an agent from creating sends or spending in Reachdesk?

Yes. Restrictions in Elaichi work per action, so you can allow looking up Reachdesk contacts and sends while restricting the creation of campaign sends or bulk sends, and you can set that on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Reachdesk connection when someone leaves?

Offboarding that person in Elaichi ends their access to Reachdesk through every client at once. If they had shared a Reachdesk connection with a team, it keeps working for everyone else. If you ever want it gone entirely, disconnecting Reachdesk once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

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

Yes. Reachdesk 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 Reachdesk?

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

### How is Elaichi different from Composio for Reachdesk?

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

## All 9 Reachdesk tools

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

- **Create a Reachdesk bulk send** (Create). Bulk Send. Trigger a gift send from a campaign to many recipients in a single request. This is the bulk counterpart to Trigger Campaign. Instead of one recipient per call, you send a list of recipients and the request is processed asynchronously: the endpoint responds immediately with a bulk send `id`, and the individual gifts are created in the background. As with the single trigger, each gift is built from the campaign's own configuration — you don't send the gift-card amount, bundle items, note template, or marketplace product. You only provide the recipients and the sender; everything else comes from the campaign. It works for every campaign type (gift card, note, bundle, marketplace).
- **Create a Reachdesk campaign send** (Create). Trigger Campaign. Trigger a gift send from a campaign. Only manual campaigns can be triggered. request_id makes the call idempotent; sender is the email of a Reachdesk user with access to the campaign; recipient can reference a CRM contact (provider + provider_contact_id) or give name/email/address directly.
- **List all Reachdesk contacts** (List). List Contacts. Get a list of contacts within your organization. Paged automatically (page-based).
- **Create a Reachdesk gdpr request** (Create). Create GDPR Request. Create a GDPR Request for erasing or exporting subject data.
- **Get single Reachdesk gdpr request by ID** (Get). Get GDPR Request. Get the information and status about an existing GDPR Request (Coming Soon) The id is the GDPR request id. Marked "Coming Soon" in the Reachdesk reference.
- **List all Reachdesk organization** (List). Get Organization. Retrieve the basic information about the Organization associated to the given API Token.
- **Get single Reachdesk send by ID** (Get). Get Send. Retrieves a single send The id is the send id.
- **List all Reachdesk sends** (List). List Sends. Get a list of Sends within your Organization Paged automatically (page-based).
- **List all Reachdesk transactions** (List). List Transactions. Get a list of transactions within your organization. Paged automatically (page-based).
