That is the specific gap this fills: stock YOURLS refuses a second keyword for a URL it already has, so campaign links to the same page collide. Two approaches are offered and the server chooses based on whether the plugin is present, which is also why each plugin-backed tool names its dependency.
A Node MCP server that bridges Claude Desktop to your own YOURLS installation. It shortens and expands links, reads click statistics, and — unusually for YOURLS — creates several different short URLs for the same destination.
- Core — `shorten_url`, `expand_url`, `url_stats`, `db_stats`, `create_custom_url`, `shorten_with_analytics` (adds UTM source, medium, campaign, term and content)
- create_custom_url takes a keyword even when the destination is already in the database, with `bypass_shortshort` and `force_url_modification` switches for the awkward cases
- Duplicate destinations handled two ways: the bundled Force Allow Duplicates plugin for true duplicates, or a timestamp-parameter fallback; the server picks based on your setup
- Plugin-backed tools, each stating the YOURLS plugin it needs: `url_analytics` (date-range clicks), `contract_url`, `update_url`, `change_keyword`, `get_url_keyword`, `delete_url`, `list_urls` (sortable, paginated, filterable), `generate_qr_code` (size, border, error-correction level, format)
Node and a clone of the repository — you point your client at `yourls-mcp.js` directly. `YOURLS_API_URL` is required. Authentication is either signature-based, which needs `YOURLS_SIGNATURE_TOKEN`, or password-based with `YOURLS_USERNAME` and `YOURLS_PASSWORD`; `YOURLS_AUTH_METHOD` defaults to `signature` and `YOURLS_SIGNATURE_TTL` to 43200 seconds. Seven of the tools depend on a YOURLS plugin being installed on your instance — the API ShortURL Analytics, API Contract, API Edit URL, API Delete, API List Extended and YOURLS-IQRCodes plugins.
Build from source — clone the repository and build it, then point your client at the binary