Flarelink runs on your own machine — the client starts it, so there is no endpoint to ping. 52 installs a week from npm. Last commit 18 Jun 2026.
Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.
Today is the operative word: we check Flarelink every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -- npx -y @flarelink/mcp
{
"mcpServers": {
"mcp": {
"args": [
"-y",
"@flarelink/mcp"
],
"command": "npx"
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@flarelink/mcp"]
{
"mcpServers": {
"mcp": {
"args": [
"-y",
"@flarelink/mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"mcp": {
"args": [
"-y",
"@flarelink/mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
FLARELINK_API_KEY (Optional. Personal API key from dash.flarelink.dev → API keys. Enables the project-management tools; the knowledge & scaffolding tools work without it.).
The author declared them in the registry entry; get the values from the project itself.
Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.
Build and test FaceSign step-up verification flows from your AI coding tool
Build and publish full-stack apps from your coding agent: models, rules, pages, auth, per-app MCP.
MCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE
Build browser games on gamedev.pl from your coding agent.
Deploy from your terminal, and give an AI coding agent the same abilities over MCP.
Drive the Godot engine from an AI coding agent: build, run, play, and verify your game live.
Give your AI agents the tools to build, manage, and run automation workflows.
Answers built from our own checks of this server.