What's New at Linkly

We've revamped how AI assistants connect to the hosted Linkly MCP server at https://mcp.linklyhq.com. The new flow uses OAuth 2.1 with PKCE and dynamic client registration — there's no API key to paste into a config file anymore.

When Claude Desktop, Claude Code, or any other MCP-compatible client connects for the first time, a browser window opens asking you to sign in to Linkly and approve access. After that, your assistant stays connected with a workspace-scoped token, and the model itself never sees your credentials.

For Claude Desktop, the config is now just:

{
  "mcpServers": {
    "linkly": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.linklyhq.com"]
    }
  }
}

See the updated setup guide for full instructions.

Click notifications can now be delivered as browser push notifications in addition to email. Push notifications appear instantly on your desktop or mobile device, even when Linkly isn't open in a tab.

To enable push notifications, go to Account Settings and toggle on Browser Notifications. Once enabled, any link with click notifications turned on will also send push notifications to your device. Clicking a notification takes you directly to that link's traffic report.

Push notifications work in Chrome, Safari, Firefox, and Edge. They use the same 15-minute debouncing as email notifications. Learn more about click notifications.

You can now add a TikTok Pixel to your links with a dedicated Pixel ID field — no need to paste the full tracking script manually.

In the link editor, expand the TikTok Pixel section, enter your Pixel ID, and save. When someone clicks the link, the TikTok Pixel fires automatically before they're redirected to the destination.

This works alongside the existing Meta Pixel and Google Analytics integrations. You can use all of them on the same link.

See 'Add TikTok Pixel to a Link' for the full guide.