LinkBit MCP

What LinkBit MCP MCP server does

LinkBit MCP provides agent-facing access to a LinkBit account. It can turn destination URLs into short links, optionally assign slugs and notes, and attach UTM campaign fields. Existing UTM parameters in a destination are preserved rather than replaced, and URL fragments remain intact.

The server also supports creating multiple links in one request, listing links with the newest entries first, and modifying an existing link. An agent can change a destination, slug, note, UTM values, or disabled state. Disabling a link stops redirects, while deletion permanently removes it, so both operations should be treated carefully.

For reporting and distribution, LinkBit MCP can return QR codes in SVG or PNG format, with options for color, a logo, and print output. Link-level statistics cover countries, devices, referrers, and daily activity. Account-level analytics are available separately.

How it works

The LinkBit MCP MCP server communicates with LinkBit's REST API. It sends the API key as a Bearer credential and exposes the API operations as MCP tools. Tool failures, such as an invalid URL, missing credentials, an unavailable slug, a daily creation limit, or an unsafe destination, are returned as tool-call errors so the model can report the problem. Protocol failures, including malformed JSON or an unknown method, remain JSON-RPC errors.

The available operations are shorten_url, shorten_urls, list_links, update_link, disable_link, delete_link, get_qr, get_link_stats, and get_analytics. Date filters for link statistics use YYYY-MM-DD values. QR requests can ask for SVG or PNG; PNG is returned as an image block when the client supports that response type.

Setup and configuration

Create an API key in the API Keys section of LinkBit after signing in. The key uses the slk_ format. Set these environment variables before starting the process:

• APP_URL, normally https://linkbit.live
• API_KEY, containing the LinkBit API key

Install and run the package with Node.js 18 or later:

npx -y linkbit-mcp

Node.js 18 is required because the process uses the built-in fetch implementation. Claude Code can register the process with claude mcp add; Claude Desktop and Cursor can use an mcp.json entry with npx, the package name, and the two environment variables. Until the package is published, the repository's local development setup uses node mcp/src/index.js and a local Cursor configuration.

Tools and capabilities

LinkBit MCP MCP server exposes these capabilities:

• Create one short link or bulk-create several links.
• List links in reverse chronological order.
• Patch link properties and toggle the disabled state.
• Disable redirects or permanently delete a link.
• Generate configurable SVG or PNG QR codes.
• Retrieve per-link and account-level analytics.

The API can also be called directly by n8n, Make, and custom agents through /api/v1, using the same authentication headers. The MCP implementation itself sends the Bearer form of authentication.

Limitations and notes

A missing or incorrect key produces a 401 response. Invalid URLs, occupied slugs, daily creation limits, and blocked or unsafe destinations produce 400 responses; an unknown link ID produces 404. Disabling and deleting are marked as destructive operations, and deletion is permanent. The README does not specify a license for the package.