
LinkBit
io.github.yutotanakastarv1.0.3Updated Oct 2, 2026
Shorten URLs, bulk create, QR, and click analytics for LinkBit.
Overview
Lets an assistant create and manage LinkBit short links, generate QR codes, and read click analytics.
- What it does
- Wraps the LinkBit REST API so an assistant can shorten a single URL or many at once, with optional slug, note and UTM parameters. It can list links, update or disable them, delete them permanently, and produce QR codes as PNG or SVG, including print versions. It also returns per-link statistics such as countries, devices, referrers and daily counts, plus an account-level analytics overview.
- When to use it
- Useful when you want link creation and campaign tracking handled inside a chat or agent workflow, for example shortening campaign URLs with UTM tags, checking clicks for a link, or generating a QR code for print. It fits marketing and content workflows more than general development tasks.
- Requirements
- Runs locally over stdio via npx from the npm package linkbit-mcp, so Node.js 18 or newer is required. It needs a LinkBit account and an API key passed in the API_KEY environment variable; APP_URL sets the API origin and defaults to the LinkBit site. Network access to the LinkBit API is required.
Installation
In SourceWeft
- Open LinkBit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
linkbit-mcp
MCP server for LinkBit: shorten links, bulk create, QR codes, and click analytics from Claude, ChatGPT, Cursor, and n8n.
Public docs: linkbit.live/docs · linkbit.live/mcp
Setup
- Sign in at linkbit.live and create an API key (
slk_...) on the API Keys page. - Node.js 18+ is required (
fetch).
Auth against the REST API uses either Authorization: Bearer slk_... or x-api-key: slk_.... This server sends Bearer.
Install
Claude Code:
Claude Desktop / Cursor (mcp.json):
Example prompts
- Shorten https://example.com/campaign as slug spring and utm_source newsletter
- List my links and show clicks for the first id since 2026-01-01
- Disable link
<id>then generate a print PNG QR
Tools
Errors
Tool failures (missing key, 401, invalid URL, daily limit, unsafe destination) are returned as tools/call with isError: true so the model can explain them. Protocol errors (unknown method, bad JSON) stay JSON-RPC errors.
- 401 — API key missing or wrong (
slk_...). Create a key under API Keys. - 400 — invalid URL, slug taken, daily create limit, blocked or unsafe destination.
- 404 — unknown link id.
- Process fails at start if Node is older than 18 (
fetchis required).
n8n, Make, and custom agents can also call /api/v1 with the same headers.
Local development (ShortLinks monorepo)
Until npm publish, Cursor can run the copy in this folder:
- Copy
mcp/cursor.mcp.json.exampleto.cursor/mcp.json(gitignored) or~/.cursor/mcp.json. - Paste the
slk_…key intoenv.API_KEY. - For this repo before publish, use
"command": "node"and"args": ["mcp/src/index.js"].
Source: README.md at commit d78ba38
Tools
0Version history
1- v1.0.3LatestOct 2, 2026


