How do I install Flarelink?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Flarelink need an API key?

The publisher lists these environment variables: FLARELINK_API_KEY.

What transport does Flarelink use?

Flarelink runs locally over stdio.

When was Flarelink last checked?

Last checked 2026-11-09. Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.

Flarelink MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @flarelink/[email protected]

Credentials from the publisher

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

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1FLARELINK_API_KEY=<secret> claude mcp add io.github.flarelink-dev-mcp -- npx -y @flarelink/mcp@0.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.flarelink-dev-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@flarelink/[email protected]"8      ],9      "env": {10        "FLARELINK_API_KEY": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.1.1
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@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

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

Tool	What it gives the agent
`flarelink_stack_overview`	The stack, cardinal rules, and deployment shapes. Read first.
`flarelink_scaffold`	How to bootstrap a complete working app (clone / one-click deploy) + file map.
`flarelink_list_patterns`	The catalog of canonical code patterns.
`flarelink_get_pattern`	Copy-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_patterns`	Cloudflare 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.

Tool	What it does
`flarelink_whoami`	Verify the key; show the user + active connection/project.
`flarelink_list_projects`	List projects on the active Cloudflare connection.
`flarelink_list_databases`	List the project's D1 databases.
`flarelink_query_database`	Run a (parameterized) SQL statement against a project D1.
`flarelink_list_buckets`	List 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.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Flarelink?

Does Flarelink need an API key?

What transport does Flarelink use?

When was Flarelink last checked?

Documentation

@flarelink/mcp

Install

Tools

Management tools (need FLARELINK_API_KEY)

License

Management tools (need `FLARELINK_API_KEY`)