# Flarelink

Flarelink gives coding agents stack guidance and code patterns for Cloudflare auth, D1, and R2. Use it when building an app on the Flarelink stack.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 1
- Author: flarelink-dev
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/flarelink-dev/mcp
- Updated: 2026-06-17
- HTML: https://affpapa.org/en/nevibecode/mcp/flarelink

## What it does

Flarelink supplies an MCP client with practical context for the Flarelink stack: better-auth with KV-backed sessions, D1 databases, and R2 storage. Its tools cover safe identifier handling in SQL, user-scoped data, presigned uploads, Wrangler bindings, and `@flarelink/client` signatures. The stack guide is also available as `flarelink://stack-guide`.

The server can outline the stack, scaffold an application, list standard recipes, and suggest Cloudflare cost patterns. With a key, management tools can inspect projects, D1 databases, and R2 buckets or run parameterized SQL through the dashboard API. `FLARELINK_API_KEY` is required for those management actions; the reference and scaffolding tools remain available without it.

## Requirements
- Needs: Node.js (commands run via npx)
- Environment variables: `FLARELINK_API_KEY` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add mcp -e FLARELINK_API_KEY=<FLARELINK_API_KEY> -- npx -y @flarelink/mcp
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add flarelink --env FLARELINK_API_KEY=<FLARELINK_API_KEY> -- npx -y @flarelink/mcp
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "flarelink": {
            "command": "npx",
            "args": [
                "-y",
                "@flarelink/mcp"
            ],
            "env": {
                "FLARELINK_API_KEY": "<FLARELINK_API_KEY>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "flarelink": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@flarelink/mcp"
            ],
            "env": {
                "FLARELINK_API_KEY": "<FLARELINK_API_KEY>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e FLARELINK_API_KEY=<FLARELINK_API_KEY> flarelink npx -y @flarelink/mcp
```
Replace <…> with your own values

## When to use it
- scaffold a Flarelink application
- set up auth with KV sessions
- find a safe D1 SQL recipe
- add presigned uploads to R2

## Example prompts
- Build a Flarelink app with auth, D1, and R2, and start by reading the stack guidance.
- Find the canonical pattern for a user-scoped D1 query and adapt it to my route.
- Check my active Flarelink project, then list its D1 databases and R2 buckets.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 392262
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89609
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74569
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89899

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md