Five of the fourteen tools are statistics, including a period-over-period comparison — that is the part you cannot do by pasting a URL into a web form. The hosted endpoint means setup is a URL and a bearer token, and self-hosting stays available if you would rather the token never leave your network.
A Node server in front of the Firelinks link-shortening platform, reachable as a hosted endpoint. It covers link creation and editing, several shapes of click reporting, custom domains, and the list of available servers.
- Short links created with a custom code, a chosen redirect type — 301, 302, 303 or META Refresh — and optional keywords and grouping — `firelinks_create_link`
- Links read individually or listed, with the destination URL updated in place and reserve URLs added — `firelinks_get_link`, `firelinks_list_links`, `firelinks_update_link_url`, `firelinks_add_reserve_url`
- Click statistics by day, totals over a period, per-link breakdowns, detailed click records, and a two-period comparison — `firelinks_stat_days`, `firelinks_stat_total`, `firelinks_stat_links`, `firelinks_stat_clicks`, `firelinks_stat_compare`
- Custom domains listed and added — `firelinks_list_domains`, `firelinks_create_domain`
- The available servers listed — `firelinks_list_servers`
A Firelinks account and its API token, sent as `Authorization: Bearer` on the connection. Point the client at `https://mcp.firelinks.cc/mcp` over HTTP transport and there is nothing to install. Self-hosting is supported too: Node.js 20.0.0 or higher, or the Docker image, with `LARAVEL_API_URL` pointing at the Firelinks API and a `/health` endpoint for checks.
One command plus a key — npx -y github:djeknet/firelinks-mcp, then supply credentials
