Skip to content

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Send the Q3 welcome campaign to Dana Ortiz at Northwind

Working in Reachdesk with Elaichi

  • List all Reachdesk contacts
  • Get single Reachdesk gdpr request by ID
  • List all Reachdesk organization
Ask anything…
Governance / Audit log Last 24 hours
Reachdesk List all Reachdesk organization Emily Carter · ChatGPT · 9:41 AM Done
Reachdesk Get single Reachdesk gdpr request by ID Emily Carter · ChatGPT · 9:41 AM Done
Reachdesk List all Reachdesk contacts Emily Carter · ChatGPT · 9:41 AM Done
Reachdesk Create a Reachdesk bulk send Megan Brooks · Claude · 9:38 AM Done
Reachdesk Create a Reachdesk campaign send Ryan Hayes · Cursor · 9:35 AM Done

How to connect Reachdesk to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

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

Reachdesk MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Reachdesk 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. The plugin directory lives at chatgpt.com/plugins.

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

Reachdesk MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

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

What teams do with Reachdesk through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Reachdesk is logged.

  • Sales

    Send a gift right after the call

    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.

  • Marketing

    Launch a bulk send to an event list

    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.

  • Customer Success

    Check whether the renewal gift arrived

    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.

  • Sales Operations

    See every send from the last quarter

    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.

  • Finance

    Reconcile gifting spend against transactions

    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.

  • Legal

    Raise a GDPR request for a contact

    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.

Try asking

  • “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”

See all 9 Reachdesk tools →

What connecting Reachdesk gets you

6 screens from Elaichi, each doing one job for your Reachdesk account.

Elaichi Agent

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Reachdesk sends in plain language.

Type a question and get answers from live Reachdesk contacts, sends and transactions.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

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

AI apps

Reachdesk in Claude, ChatGPT and Cursor, connected once.

One governed endpoint for every MCP client, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
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.

Tool catalog

9 Reachdesk tools, ready with no code.

Contacts, sends, transactions, organizations and GDPR requests, covered without writing a connector.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Reachdesk · campaign sends and contacts

Reachdesk starter 18 Mar 4, 2026

Marketing toolbox

Reachdesk · bulk sends and event lists

— 9 Mar 2, 2026

Customer Success toolbox

Reachdesk · renewal gifts and send status

— 24 Feb 27, 2026

Sales Operations toolbox

Reachdesk · sends and organizations

Reachdesk starter 6 Feb 19, 2026

Finance toolbox

Reachdesk · transactions and gifting spend

— 31 Jan 30, 2026

Legal toolbox

Reachdesk · GDPR requests

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Reachdesk toolbox.

Sales sends gifts, Finance reviews transactions, Legal handles GDPR requests, each from a scoped toolbox.

ElaichiConnections
Connection Scope Status Access
RE

Reachdesk (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RE

Reachdesk (Sales US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RE

Reachdesk (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RE

Reachdesk (Customer Success)

Connected by Tyler Reed

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

Reachdesk (Finance)

Connected by Ryan Hayes

Personal • Active Not shared
RE

Reachdesk (Legal)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Reachdesk account, never the key.

See who connected each Reachdesk account and which teams and members work through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Reachdesk Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Reachdesk Sends Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Reachdesk Sends List Toolbox

Audit log

Know who sent what, and when.

Every Reachdesk send, lookup and request is logged with who, what, type and resource.

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.

Reachdesk digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch sends

    Reachdesk

    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 Jake Morgan

    Approve
  6. Post the digest

    Reachdesk

    Queued

Workflows

A schedule starts the Reachdesk digest, you approve.

Sends are fetched, grouped and drafted into a digest, approved by a person, then posted back.

Reachdesk health

Refreshed 4 minutes ago · every 15 minutes · from the sends collection

Live

Sends

1,284 ↓ 12%

Contacts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sends created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales US 27%

Marketing 21%

Customer Success 18%

Collections and dashboards

Reachdesk health, counted on a schedule, no model.

Four metrics, 14 days of sends created and a team breakdown, refreshed without asking.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Reachdesk, 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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Reachdesk tools for your AI agents

9 tools are ready to call through Elaichi's MCP endpoint the moment you connect Reachdesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put Reachdesk 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