Connect LinkToDM to Cursor

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

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.

The AI only sees what your account can see

Permissions follow your existing LinkToDM role, and you can revoke access at any time from console.linktodm.com → Settings → Connected apps.

Set up Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.json at your project root. Add the linktodm entry, then restart Cursor.

~/.cursor/mcp.json

{
  "mcpServers": {
    "linktodm": {
      "url": "https://api.linktodm.com/v1/mcp/"
    }
  }
}

On the next launch, open Settings → MCP Servers. You’ll see linktodm listed; click Sign in to complete OAuth in your browser. Once it shows green, ask Cursor’s agent “Use linktodm to list my recent automations.”

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

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

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

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

Pop-up blockers can swallow the OAuth window. Allow pop-ups for the AI client’s domain and try again.

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.