How to Use EnoSend with Claude Desktop via MCP

Claude Desktop supports the Model Context Protocol, which means you can give it tools to call. EnoSend operates a hosted MCP server, so the only thing you need to do is point Claude at it.

There are two ways to plug EnoSend into Claude, Pick one.

• Claude.ai (web) → use the Custom connector form. Easiest, no install.

• Claude Desktop (Mac / Windows app) → edit a local config file. Needed if you want tools available in the desktop app.

Option A — Claude.ai (Custom connector)

This is the fastest path. Everything happens in the browser.

1. Get your API key
In the EnoSend dashboard: API Keys → Create new key. Copy the wa_live_… value.

2. Open the connector form on Claude.ai
Go to claude.ai → Settings → Connectors → Add custom connector.

3. Fill in the three fields

• Remote MCP URL

  https://mcp.enosend.com/mcp

• OAuth Client ID (same for every EnoSend account)

  enosend-mcp

• Client Secret (this is your API key)

  wa_live_YOUR_KEY

Replace wa_live_YOUR_KEY with the key you copied in step 1.

Heads up: the Client ID is not your API key. Only the Client Secret field carries wa_live_…. People mix these up all the time.

4. Save and start a new chat
The enosend tools (list_instances, send_message, send_bulk_messages, …) will show up in the tool picker.

Option B — Claude Desktop (config file)

Claude Desktop's MCP support is stdio-only, so you connect through a tiny local bridge called mcp-remote. It runs via npx — no global install.

1. Get your API key
EnoSend dashboard → API Keys → Create new key → copy the wa_live_… value.

2. Make sure Node.js is installed
Open Terminal and run:

node -v

If you get "command not found", install the LTS build from nodejs.org.

3. Open the Claude Desktop config
The safe way (works on Mac and Windows, creates the file if it doesn't exist):

1. Open Claude Desktop

2. Claude → Settings… (Mac) or File → Settings (Windows)

3. Go to the Developer tab

4. Click Edit Config

For reference, the file lives at:

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

Use the Settings button — don't go hunting in Finder. The folder may not exist until Claude Desktop creates it.

4. Paste the EnoSend block
If the file is empty, paste the whole thing. If you already have other mcpServers, just add the enosend entry inside the existing object.

{
 "mcpServers": {
    "enosend": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.enosend.com/mcp",
        "--header",
        "Authorization:Bearer wa_live_YOUR_KEY"
      ]
   }
  }
}

Replace wa_live_YOUR_KEY with your key. Save.

5. Fully quit and reopen Claude Desktop
On Mac, ⌘Q — closing the window isn't enough. On reopen, click the tools icon in the composer; you'll see the enosend tool group.

Try it (either option)

Ask Claude:

Which WhatsApp numbers do I have connected on EnoSend? Send a test message to +233200000000 from the first one.

Claude will call list_instances, then send_message. You'll see the tool calls in the transcript, the result in your EnoSend dashboard, and the message land on the phone.

Your key never leaves your account — Claude.ai stores it as an OAuth secret, or mcp-remote reads it from your local config. The model only ever sees the tool surface, not the secret.