Firelinks MCP Server

MCP Server for Firelinks API - allows LLM clients to interact with Firelinks platform. The firelinks mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

MCP (Model Context Protocol) server for the Firelinks platform, allowing external LLMs (Large Language Models) to interact with the Firelinks API - https://firelinks.cc/p/api

This server implements the MCP protocol developed by Anthropic and provides a set of tools for working with the Firelinks platform:

Its toolset

Everything the assistant can do here goes through one of these:

• Endpoints — The Endpoints tool exposed by this server
• Authentication — All requests to /mcp require an authentication token in the header:
• Cursor — The Cursor tool exposed by this server
• Links — 1. firelinks_create_link - create short link 2. firelinks_get_link - get link information 3. firelinks_list_links - list all links 4
• Statistics — 1. firelinks_stat_days - statistics by days 2. firelinks_stat_total - total statistics for period 3. firelinks_stat_links - statistics for all links
• Domains — 1. firelinks_list_domains - list domains 2. firelinks_create_domain - add domain
• Servers — The Servers tool exposed by this server
• Initialize — The Initialize tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 2 environment variables: LARAVEL_API_URL, YOUR_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 20.0.0 - Docker and Docker Compose (for containerization) - Firelinks API token

When to reach for it

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Firelinks MCP's toolset — Endpoints, Authentication, Cursor and 5 more — is a fair guide to whether it matches your workflow. It is maintained by djeknet; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the firelinks mcp mcp server does with a few real requests.