Skip to content

MCP & Agents

You can connect dynm.link to AI agents (such as Claude Desktop, Cursor, or Antigravity) using the Model Context Protocol (MCP). Running dynm.link mcp starts a stdio-based MCP server.

Installation & Configuration

Install the CLI (see the CLI docs), then add it to your agent's MCP configuration file (e.g., claude_desktop_config.json):

json
{
  "mcpServers": {
    "dynm-link": {
      "command": "dynm.link",
      "args": ["mcp"],
      "env": {
        "DYNM_API_KEY": "dynm_..."
      }
    }
  }
}

Available Tools

The MCP server exposes the following tools:

  • list_links — List links in a folder (requires domain).
  • get_link — Get details of a single link by slug and domain.
  • create_link — Create a new link.
  • update_link — Update an existing link.
  • delete_link — Delete a link by slug and domain.
  • check_slug — Check if a slug is available on a domain.

File Upload Note

The create_link and update_link tools take a generic content body whose shape depends on the link's type (redirect rules, bio links, text, or file) — the same shape used by every other dynm.link surface (CLI, dashboard, REST API).

For file type links, the MCP server does not support direct binary upload via stdio. Instead, you must specify an already-uploaded r2Key in the content configuration. Full local binary file uploads are CLI-only today.

One short link: redirect, page, file, or QR.