MCP server: One MCP server.

Flarelink

@flarelinkRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

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

Databasesv0.1.1MITTypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: creates or changes data: records, files, settings.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@flarelink/mcpv0.1.2

Run

npx -y @flarelink/mcp

MCP client config

{
  "mcpServers": {
    "flarelink": {
      "command": "npx",
      "args": [
        "-y",
        "@flarelink/mcp"
      ]
    }
  }
}
README2 min read

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

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.

Similar modules

Browse Databases