Connect Reachdesk MCP with Claude

  • Updated

To use this feature, please sign up to our early access program. 

Reachdesk MCP is not yet listed in Anthropic's built-in connector directory, so you'll add it as a custom connector using the URL from your Reachdesk account. This takes about 3 minutes.

Before you start

  • You'll need login to Reachdesk as an admin.
  • You'll need a Claude.ai account (Claude Pro, Team, or Enterprise) with permission to add connectors.
  • Have both Reachdesk and Claude open in your browser — you'll switch between them a few times.

Connection steps

STEP 1

Copy your Reachdesk MCP URL

In Reachdesk, go to Settings → API & MCP. Under the Reachdesk MCP section, copy the Reachdesk MCP URL — you'll paste this into Claude in the next step.

Reachdesk → Settings → API & MCP

Tip: This URL is the same for every user on your Reachdesk account, so you only need to look it up once. If you can't see the API & MCP tab, ask a Reachdesk admin to enable it or generate the URL for you.

STEP 2

Start adding a custom connector

In Claude, go to Settings → Connectors, then click Add in the top-right corner to open the Add custom connector dialog. Give it a clear name (e.g. "Reachdesk MCP") and paste the URL you copied in Step 1 into the server address field. Click Continue.

Add custom connector — name and URL

STEP 3

Confirm authentication settings

Claude will detect that Reachdesk MCP uses OAuth and pre-select the recommended options: "Sign in now" under Authentication, and "Use Claude's published identity" under OAuth client. These defaults work for most teams — leave them as-is unless your Reachdesk admin has told you otherwise. Click "Add".

Add custom connector — authentication options

STEP 4

Connect the new connector

Reachdesk MCP now appears in your connectors list, but it isn't linked to your account yet. Open it and click "Connect".

Reachdesk MCP connector — not connected yet

STEP 5

Continue connecting

You'll be taken to a confirmation screen checking that you intended to connect a service. Since you just started this from Claude, click "Continue connecting".

Finish connecting a connector confirmation screen

Caution:  Only click "Continue connecting" if you were the one who started this flow. If this screen appears unexpectedly, click "Not now" and check with your Reachdesk or Claude admin.

STEP 6

Authorize Claude

Reachdesk will ask you to confirm the permissions Claude is requesting — typically "Read" (view Reachdesk campaigns and sends data according to your role) and "Write" (create and cancel sends based on your role permissions). Review these, then click "Authorize".

Reachdesk — Authorize Claude

STEP 7

Set tool permissions

Back in Claude, you'll land on the Tool permissions screen for Reachdesk MCP. Here you choose when Claude can use each tool:

  • Read-only tools — for example, getting or listing campaign or send details or wallet balances
  • Write/delete tools — for example, sending a gift or cancelling a send

Even if a user has access to all of these tools, they can only perform actions and view data based on their permissions and role in Reachdesk. For example, a sender role will only see their own sends, campaigns and wallets, while an admin can see everything.

For each group (or individual tool), set "Always allow," "Ask each time," or "Never allow." Most teams set read-only tools to "Always allow" and keep write/delete tools on "Ask each time," so Claude checks with you before sending a gift or cancelling anything.

Claude — Reachdesk MCP tool permissions

Troubleshooting

I don't see the API & MCP tab in Reachdesk

This tab is role-restricted. Ask a Reachdesk admin on your team to retrieve the MCP URL or grant you access.

The "Finish connecting a connector?" page appeared without me starting the flow

Don't click Continue connecting. Close the tab and repeat the steps above from Claude directly.

Claude says a Reachdesk tool call failed with an authentication error

Go back to Settings → Connectors → Reachdesk MCP and reconnect — your session with Reachdesk may have expired.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.