DMWire Docs
Early access

Connect Claude to WhatsApp and Telegram

Claude adds remote MCP servers as custom connectors. DMWire signs in with an API key, so you add the key as a request header. That option is still rolling out on Claude's side, so this page also gives a route that works on every Claude desktop install today.

Option A: custom connector with a request header

Use this if your Claude shows a Request headers section when you add a custom connector. Anthropic describes it as a beta available to a limited set of organizations; if you do not see the section, your account does not have it yet and Option B is for you. On Free, Pro and Max you add connectors yourself (Free allows one custom connector); on Team and Enterprise an Owner adds it for the organization (Anthropic's guide).

  1. In Claude, open Customize, Connectors and click Add custom connector.
  2. Name: DMWire. Remote MCP server URL: https://mcp.dmwire.ai/mcp
  3. Authentication: choose No sign-in.
  4. Open Request headers, pick the header name x-api-key, and paste your DMWire API key as the value. Mark it Required.
  5. Click Add. In a chat, open the + menu, Connectors, and make sure DMWire is on.

Claude does not show a header value again after you save it, and you cannot edit it later. To change the key, remove the connector and add it again.

Using authorization as the header name works too; then the value must be Bearer followed by your key, with the space.

Option B: Claude desktop config file (works today)

Claude desktop can start a small local bridge that forwards to DMWire with your key. You need Node.js installed (the current LTS version is fine).

  1. In Claude desktop open Settings, Developer, Edit Config. This opens claude_desktop_config.json.
  2. Add DMWire under mcpServers and put in your key:
claude_desktop_config.json
{
  "mcpServers": {
    "dmwire": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.dmwire.ai/mcp", "--header", "X-API-Key:${DMWIRE_API_KEY}"],
      "env": { "DMWIRE_API_KEY": "paste your dmw_live_ key here" }
    }
  }
}
  1. Quit Claude completely and open it again. DMWire now shows up in the tools and connectors menu of a new chat.

Write X-API-Key:${DMWIRE_API_KEY} exactly like that, with no space after the colon: on Windows, Claude desktop does not pass spaces inside arguments correctly (mcp-remote notes).

We ran this bridge against the live server. The first two lines it returned (the instructions text is shortened here):

Real output of the bridge (initialize, then get_usage)
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{}},"serverInfo":{"name":"dmwire","title":"DMWire","version":"1.0.0"},"instructions":"DMWire connects you, the agent, to the user's own WhatsApp and Telegram ..."}}
{"jsonrpc":"2.0","id":2,"result":{"content":[{"type":"text","text":"HTTP 200\n{\"plan\":\"free\",\"day\":\"2026-10-17\",\"sends\":0,\"sends_cap\":50,\"new_contacts\":0,\"new_contacts_cap\":10}"}],"isError":false}}

Try it

Start a new chat and ask:

Ask Claude
Use DMWire to check which of my accounts are connected and how many messages I can still send today.

Then follow the Quickstart from step 2 to link WhatsApp or Telegram.

Coming later: sign in instead of a key

A sign in flow, where you paste only the address and log in to DMWire, is planned. It is not live yet; today DMWire needs the key in a header.

Troubleshooting

  • "Missing DMWire API key": the header did not reach DMWire. Check the header name (x-api-key) and that the value is the full key starting with dmw_live_.
  • "Invalid API key": the key is wrong or was replaced. For a new one, use the form on dmwire.ai with the email your invite went to, and we get back to you.
  • No Request headers section: your account does not have that Claude beta yet. Use Option B, or Claude Code.
  • Option B only works in Claude desktop, not on claude.ai in the browser.

Last checked against the live service on 2026-10-17.