Connect LinktoDM to Claude, ChatGPT, Cursor & other AI clients

The MCP URL

Every client below uses the same URL. Copy it once and paste it where the client asks for the server endpoint.

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.

1. Connect to Claude (claude.ai or Claude Desktop)

1. Open Claude and go to Settings → Connectors.
2. Click Add custom connector.
3. Enter LinktoDM as the name and paste the MCP URL above into the Server URL field.
4. Click Connect. Claude will open a LinktoDM sign-in page in your browser — sign in with the account you use at console.linktodm.com and approve the requested permissions.
5. Back in Claude, you should see LinktoDM listed as a connected source. Start a new chat and ask things like “How many automations did I run last week?” or “Show me my latest contacts.”

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.

2. Connect to ChatGPT

1. Open ChatGPT and go to Settings → Connectors (Plus, Pro, Team, Enterprise, or Edu plan required).
2. Click Create (or Add custom connector).
3. Set the name to LinktoDM, paste the MCP URL above into the MCP server URL field, and choose OAuth as the authentication method (ChatGPT auto-discovers our OAuth endpoints — no client ID or secret to enter).
4. Save the connector, then click Connect and approve access on the LinktoDM sign-in page that opens.
5. In a new chat, enable the LinktoDM connector for the conversation and start asking about your account.

3. Connect to Cursor

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

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

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

4. Connect to VS Code (Copilot Chat, Cline, Continue)

VS Code 1.99+ supports MCP servers natively in Copilot Chat. Add this to your settings.json (User or Workspace):

{
  "mcp": {
    "servers": {
      "linktodm": {
        "type": "http",
        "url": "https://api.linktodm.com/v1/mcp/"
      }
    }
  }
}

Reload the window. In Copilot Chat, switch to Agent mode and the linktodm tools will be available. The first call triggers OAuth in your browser.

Cline and Continue use a similar JSON shape — paste the same URL into their MCP server configuration UI.

5. Connect any other MCP client

The LinktoDM MCP server speaks Streamable HTTP with OAuth 2.0 (Dynamic Client Registration). Any client that supports remote MCP servers can connect with just the URL — no client ID, secret, or local bridge process is needed.

• Endpoint: the MCP URL shown above
• Transport: Streamable HTTP (the modern MCP HTTP transport)
• Auth: OAuth 2.0 — discovery at /.well-known/oauth-authorization-server, dynamic client registration at /register
• Scopes: read, write

What you can do once connected

Whatever the client lets you do via 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.”

The AI only sees what your account can see. Permissions follow your existing LinktoDM role. Revoke access at any time from console.linktodm.com → Settings → Connected apps.

Troubleshooting

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.