Flarelink

dev.flarelinkPublished by flarelink.devv0.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDatabasesCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives AI coding tools Flarelink stack guidance (Cloudflare auth, D1, R2) plus optional tools to inspect and query your Flarelink projects.

What you can do
  • Read stack overview, cardinal rules and deployment shapes
  • Get scaffolding steps and a file map for a working app
  • Browse and fetch canonical code patterns for auth, route guards, identifier-safe D1, R2 upload/presign and wrangler bindings
  • Look up SDK signatures and return shapes, and cost-optimization guidance
  • With an API key: verify the key, list projects, D1 databases and R2 buckets, and run parameterized SQL against a project database
  • Attach the stack guide as a resource for context
When to use it
Useful when you are building an app on the Flarelink stack in Cursor, Claude Code, Windsurf or a similar MCP-capable editor and want the agent to follow the stack's security and cost rules instead of guessing. Add the API key only if you also want the assistant to inspect and query your real projects.
Requirements
Runs locally over stdio via npx from the npm package @flarelink/mcp, so Node.js is needed. No install step. The knowledge and scaffolding tools work without credentials; the management tools need FLARELINK_API_KEY, obtained from the Flarelink dashboard, set in the MCP config environment.
Before you install
FLARELINK_API_KEY is optional but grants the same access as your Flarelink login, so treat it like a password and keep it out of shared configs. With the key, the assistant can run SQL statements against a project's D1 database, which can change data; review queries before approving. Management calls go through the Flarelink dashboard API.

Installation

In SourceWeft

  1. Open Flarelink in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@flarelink/mcp

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

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

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

json
{  "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.

Management tools (need FLARELINK_API_KEY)

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.

Source: README.md at commit 6835582

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts