Flarelink

Registre officiel Outils de développement

Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @flarelink/mcp
Claude Code
claude mcp add flarelink -e 'FLARELINK_API_KEY=<your flarelink_api_key>' -- npx -y @flarelink/mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "flarelink": {
            "command": "npx",
            "args": [
                "-y",
                "@flarelink/mcp@0.1.1"
            ],
            "env": {
                "FLARELINK_API_KEY": "<your flarelink_api_key>"
            }
        }
    }
}

Variables d'environnement

  • FLARELINK_API_KEY secret Optional. Personal API key from dash.flarelink.dev → API keys. Enables the project-management tools; the knowledge & scaffolding tools work without it.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. @flarelink/mcp
  2. Install
  3. Tools
  4. License

An MCP server that teaches your AI coding tool to build correctly on the Flarelink stack — Cloudflare auth (better-auth + KV sessions), D1, and R2 — from inside Cursor, Claude Code, Windsurf, and anything else that speaks MCP.

It hands the agent the security and cost rules up front (user-scoping, identifier-safe SQL, KV sessions, presigned R2) so the generated code is right the first time, instead of the agent guessing and you debugging.

Install

No install needed — run it with npx. Add it to your tool's MCP config:

Claude Code

claude mcp add flarelink -- npx -y @flarelink/mcp

Cursor / Windsurf / Claude Desktop (mcp.json / config):

{
  "mcpServers": {
    "flarelink": {
      "command": "npx",
      "args": ["-y", "@flarelink/mcp"],
      "env": { "FLARELINK_API_KEY": "flk_…" }
    }
  }
}

The FLARELINK_API_KEY is optional. Without it you still get all the knowledge + scaffolding tools. With it, the management tools (below) can drive your actual Flarelink projects. Mint a key at dash.flarelink.dev → API keys.

Tools

ToolWhat it gives the agent
flarelink_stack_overviewThe stack, cardinal rules, and deployment shapes. Read first.
flarelink_scaffoldHow to bootstrap a complete working app (clone / one-click deploy) + file map.
flarelink_list_patternsThe catalog of canonical code patterns.
flarelink_get_patternCopy-pasteable code for one recipe (auth setup, route guards, identifier-safe D1, R2 upload/presign, wrangler bindings, SDK usage).
flarelink_sdk_reference@flarelink/client signatures + return shapes (auth / storage / db).
flarelink_cost_patternsCloudflare cost-optimization guidance, with targeted hints for the feature you describe.

It also exposes the stack guide as a resource (flarelink://stack-guide) you can attach as context.

Drive your actual Flarelink projects from the editor. These route through the Flarelink dashboard API and act exactly as you would in the UI.

ToolWhat it does
flarelink_whoamiVerify the key; show the user + active connection/project.
flarelink_list_projectsList projects on the active Cloudflare connection.
flarelink_list_databasesList the project's D1 databases.
flarelink_query_databaseRun a (parameterized) SQL statement against a project D1.
flarelink_list_bucketsList the project's R2 buckets.

Without a key they return a clear "set FLARELINK_API_KEY" message. The key has the same access as your Flarelink login — treat it like a password.

License

MIT. Part of Flarelink — the dashboard for the Cloudflare developer stack.

Questions fréquentes

Qu'est-ce que Flarelink ?

Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.

Comment installer Flarelink ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add flarelink -e 'FLARELINK_API_KEY=<your flarelink_api_key>' -- npx -y @flarelink/mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Flarelink ?

Oui. Il attend FLARELINK_API_KEY, à renseigner dans sa configuration.

Flarelink est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Flarelink ?

Il est publié par flarelink-dev. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.