Connect LinkToDM to Claude
LinkToDM ships a hosted MCP server (Model Context Protocol) so any MCP-compatible AI client (Claude, ChatGPT, Cursor, VS Code, and others) can read your LinkToDM account, contacts, automations, and analytics, and act on your behalf. Connection takes about a minute and uses your existing LinkToDM login (OAuth), with no API keys to copy or rotate.
The MCP URL
Section titled “The MCP URL”Every client uses the same URL. Copy it once and paste it where the client asks for the server endpoint.
https://api.linktodm.com/v1/mcp/Authentication is handled automatically over OAuth. When the client first connects, you’ll be sent to a LinkToDM sign-in page in your browser to approve access.
Set up Claude
Section titled “Set up Claude”-
Open Claude and go to Settings → Connectors.
-
Click Add custom connector.
-
Enter LinkToDM as the name and paste the MCP URL into the Server URL field.
-
Click Connect. Claude opens a LinkToDM sign-in page in your browser. Sign in with the account you use at console.linktodm.com and approve the requested permissions.
-
Back in Claude, LinkToDM appears as a connected source. Start a new chat and ask something like “How many automations did I run last week?”
On Claude Desktop the same Settings → Connectors flow applies on recent versions. If your version doesn’t show that menu, update Claude Desktop or use claude.ai in the browser.
What you can do once connected
Section titled “What you can do once connected”Whatever the client lets you do in natural language. Common asks:
- “List my LinkToDM automations and which ones are active.”
- “How many DMs did my comment-to-DM automations send last week?”
- “Show me the latest contacts that opted in to my list.”
- “Pause the automation for my last reel.”
- “Export my conversion analytics for the past 30 days as CSV.”
Troubleshooting
Section titled “Troubleshooting”“401 Unauthorized” after connecting
Section titled ““401 Unauthorized” after connecting”The OAuth token expired or was revoked. In the client, disconnect the LinkToDM server and reconnect. You’ll be sent through the sign-in flow again.
Client says “could not connect to server”
Section titled “Client says “could not connect to server””Confirm you copied the full URL (it ends with /v1/mcp/). If you’re behind a corporate proxy, allow outbound HTTPS to https://api.linktodm.com/v1/mcp/.
Tools aren’t showing up in the chat
Section titled “Tools aren’t showing up in the chat”Most clients require you to explicitly enable the connector for the conversation. Claude: toggle the connector chip; ChatGPT: enable it in the connector menu; Cursor and VS Code: switch to Agent mode. Check the client’s MCP panel to confirm the server shows as connected before asking the AI to use it.
Sign-in page doesn’t open
Section titled “Sign-in page doesn’t open”Pop-up blockers can swallow the OAuth window. Allow pop-ups for the AI client’s domain and try again.
Still stuck?
Section titled “Still stuck?”Email us at support@linktodm.com with the client name, the version, and a screenshot of the error. We usually reply the same business day.