LabscoMCP early access ↗
djeknetMCP SERVER

Firelinks.cc MCP

Create and manage Firelinks short links and read their click statistics — run with npx and your Firelinks API token.

by djeknet ↗SEO, Web & Product AnalyticsCommunity

LABSCO SUMMARY

Reporting is the deeper half of this, not link creation.

Five of the thirteen tools are statistics, including a period-over-period comparison — that is the part you cannot do by pasting a URL into a web form. Setup is one npx line with the token in your client configuration.

What it is

A Node server in front of the Firelinks link-shortening platform, run on your own machine. It covers link creation and editing, several shapes of click reporting, custom domains, and the list of available servers.

What you get

  • 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

Requirements

A Firelinks account and its API token, set as FIRELINKS_API_TOKEN in the client configuration, and Node.js 20.0.0 or higher. The repository also has a Docker image and an HTTP mode with a /health check for running it as a service. The README names a hosted endpoint at mcp.firelinks.cc, but in September 2026 that address served an unrelated web page, not MCP.

Setup effort

One command plus a key — npx -y github:djeknet/firelinks-mcp, then supply credentials