Urlicer API v1

MCP server

Let an AI assistant make and find short links in your workspace, with the same API key as the REST API.

Urlicer runs a remote Model Context Protocol server. Connect an assistant to it and you can ask, in plain words, for a short link to a page, for the newest links and their clicks, or to point an existing link somewhere else.

It signs in with an ordinary API key, so it works in the one workspace the key belongs to, on every plan, and everything a plan allows or refuses through the API applies here too.

Endpoint

https://urlicer.com/mcp

Transport: Streamable HTTP. Each request is one JSON-RPC message in a POST, answered with JSON. There is no event stream, so a GET answers 405.
Auth: Authorization: Bearer url_live_…. Without a working key every request answers 401.
Each tool call counts as one request against the key's rate limit. Connecting and listing the tools do not.

Connect your assistant

Create a key on the workspace's Developers page first, then:

Claude Code

claude mcp add --transport http urlicer https://urlicer.com/mcp \
  --header "Authorization: Bearer url_live_YOUR_KEY"

Cursor

{
  "mcpServers": {
    "urlicer": {
      "url": "https://urlicer.com/mcp",
      "headers": { "Authorization": "Bearer url_live_YOUR_KEY" }
    }
  }
}

VS Code (GitHub Copilot agent mode)

{
  "servers": {
    "urlicer": {
      "type": "http",
      "url": "https://urlicer.com/mcp",
      "headers": { "Authorization": "Bearer url_live_YOUR_KEY" }
    }
  }
}

Claude Desktop, through the mcp-remote bridge, which needs Node.js:

{
  "mcpServers": {
    "urlicer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://urlicer.com/mcp",
               "--header", "Authorization: Bearer url_live_YOUR_KEY"]
    }
  }
}

claude.ai and ChatGPT on the web add custom connectors with an OAuth sign-in, which this server does not offer yet. Use one of the clients above for now.

Tools

create_link: shortens a URL. Optional custom name (Pro and above), custom domain, folder (paid plans), title and notes.
list_links: the newest links first, with click counts; page, size (up to 100) and folder.
get_link: one link by its short link or code, with its destination and clicks.
update_link: change the destination, title, notes or folder, or switch the link off and on. Only the fields given change. A new destination also re-points every printed QR code for that link, so a careful assistant asks first.
get_workspace: which workspace the key belongs to, and links made this month against the plan's limit.

There is no delete tool, on purpose: a link may already be printed, and switching it off with update_link can be undone.

When a tool is refused

A refusal comes back as a tool result marked as an error, with a sentence the assistant can pass on, such as "Custom names start on the Pro plan" or "No such link in this workspace". The reasons are the same as the API's errors.