mcpField
F
Firelinks.cc

Firelinks.cc

Remote
github.com/djeknetBusiness & Marketing3Updated 1w ago
Repository

About Firelinks.cc

Firelinks.cc is an MCP server for LLM clients that manage links and review their performance on the Firelinks platform. It also provides custom-domain management and a list of available servers.

Key features

  1. 01Create, retrieve, and edit short links
  2. 02View click statistics
  3. 03Compare statistics across periods
  4. 04Manage custom domains
  5. 05List available servers

Use cases

  1. 01Create and update campaign links
  2. 02Review link click activity
  3. 03Compare traffic between periods

MCP support

The server exposes Firelinks API operations as MCP tools over HTTP or SSE. MCP clients authenticate with a Firelinks API token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.firelinks.cc/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.firelinks.cc/mcpAuth required

Tools

Details

From the project README

Firelinks MCP Server

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

Description

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

  • Link Management: create, retrieve, edit short links
  • Statistics: get detailed click statistics, compare periods
  • Domains: manage custom domains
  • Servers: get list of available servers

Architecture

LLM client → HTTPS (mcp.firelinks.cc) → Node.js MCP Server → Firelinks API Backend

Requirements

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

Installation

Local Development
  1. Install dependencies:
cd mcp-server
npm install
  1. Create .env file based on .env.example:
cp .env.example .env
  1. Configure environment variables in .env:
PORT=3000
LARAVEL_API_URL=https://firelinks.cc/api
NODE_ENV=development
  1. Start the server:
npm start

Or for development mode with auto-reload:

npm run dev
Docker
  1. Build the image:
docker build -t firelinks-mcp-server .
  1. Run the container:
docker run -d \
  -p 3000:3000 \
  -e LARAVEL_API_URL=https://firelinks.cc/api \
  --name firelinks-mcp-server \
  firelinks-mcp-server
Docker Compose
docker-compose up -d

Usage

Endpoints
  • GET /health - server health check
  • POST /mcp - main MCP endpoint (JSON-RPC 2.0)
  • GET /sse - Server-Sent Events for streaming
Authentication

All requests to /mcp require an authentication token in the header:

Authorization: Bearer YOUR_API_TOKEN

You can get an API token in your Firelinks account.

Integration with LLM Clients

Claude Desktop

Add to Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "firelinks": {
      "url": "https://mcp.firelinks.cc/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Cursor

Add to Cursor configuration (mcp.json):

{
  "mcpServers": {
    "firelinks": {
      "url": "https://mcp.firelinks.cc/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Other MCP Clients

For connecting to other MCP-compatible clients use:

  • URL: https://mcp.firelinks.cc/mcp
  • Transport: HTTP
  • Authentication: Bearer token in Authorization header

Available Tools

Links
  1. firelinks_create_link - create short link
  2. firelinks_get_link - get link information
  3. firelinks_list_links - list all links
  4. firelinks_update_link_url - update link URL
  5. firelinks_add_reserve_url - add reserve URL
Statistics
  1. firelinks_stat_days - statistics by days
  2. firelinks_stat_total - total statistics for period
  3. firelinks_stat_links - statistics for all links
  4. firelinks_stat_clicks - detailed click statistics
  5. firelinks_stat_compare - compare two periods
Domains
  1. firelinks_list_domains - list domains
  2. firelinks_create_domain - add domain
Servers
  1. firelinks_list_servers - list available servers

Request Examples

Initialize
curl -X POST https://mcp.firelinks.cc/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "initialize",
    "params": {},
    "id": 1
  }'
List Tools
curl -X POST https://mcp.firelinks.cc/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/list",
    "params": {},
    "id": 1
  }'
Create Link
curl -X POST https://mcp.firelinks.cc/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "firelinks_create_link",
      "arguments": {
        "url": "https://example.com",
        "type": "url",
        "redirect_type": 0,
        "code": "my-link"
      }
    },
    "id": 1
  }'

Required parameters:

  • url - Valid link with http or https
  • type - The type of link (use "url" for web links)
  • redirect_type - Redirect type: 0 (301), 1 (302), 2 (303), 4 (META Refresh)

Optional parameters:

  • link_name - Link name
  • code - Custom link code (must be unique)
  • domain_id - Domain ID
  • sub_domain - Subdomain
  • keywords - Keywords for search
  • keywords_mode - Keyword search logic (1, 2, or 3)
  • group_id - Link group ID
  • options - Additional settings string
Get Statistics
curl -X POST https://mcp.firelinks.cc/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "firelinks_stat_days",
      "arguments": {
        "date_from": "2024-01-01",
        "date_to": "2024-01-31"
      }
    },
    "id": 1
  }'
Project Structure
mcp-server/
├── src/
│   ├── index.js              # Main Express server file
│   ├── lib/
│   │   ├── laravel-api.js    # HTTP client for Laravel API
│   │   └── mcp-handler.js    # MCP protocol handler
│   └── tools/
│       ├── links.js          # Tools for links
│       ├── statistics.js     # Tools for statistics
│       ├── domains.js        # Tools for domains
│       └── servers.js        # Tools for servers
├── package.json
├── Dockerfile
├── docker-compose.yml
├── .env.example
└── README.md

Troubleshooting

Authentication Error

Problem: Missing or invalid Authorization header

Solution: Make sure the request header contains a valid token:

Authorization: Bearer YOUR_API_TOKEN
Request Timeout

Problem: Requests to Laravel API timeout

Solution:

  1. Check Laravel API availability
  2. Increase timeout in src/lib/laravel-api.js
  3. Check network connectivity between containers
Server Won't Start

Problem: Error on startup

Solution:

  1. Check logs: docker logs firelinks-mcp-server
  2. Make sure port 3000 is not in use
  3. Check environment variables are correct

License

MIT

Support

For questions and support contact [email protected]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.