English Français العربية

Flarelink

Official registry Developer tools

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

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
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "flarelink": {
            "command": "npx",
            "args": [
                "-y",
                "@flarelink/mcp@0.1.1"
            ],
            "env": {
                "FLARELINK_API_KEY": "<your flarelink_api_key>"
            }
        }
    }
}

Environment variables

  • 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

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  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.

Frequently asked questions

What is Flarelink?

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

How do I install Flarelink?

It runs on your machine. In Claude Code: claude mcp add flarelink -e 'FLARELINK_API_KEY=<your flarelink_api_key>' -- npx -y @flarelink/mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Flarelink need an API key?

Yes. It expects FLARELINK_API_KEY, which you set in its configuration.

Is Flarelink open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Flarelink?

It is published by flarelink-dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.