npm @flarelink/mcpstdioMITupdated 2mo ago
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.
What can you do with Flarelink?
@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.
Install
Add Flarelink to your client. Pick the one you use.
claude mcp add mcp -- npx -y @flarelink/mcpcodex mcp add mcp -- npx -y @flarelink/mcpamp mcp add mcp -- npx -y @flarelink/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp","command":"npx","args":["-y","@flarelink/mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @flarelink/mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
6 tools
Flarelink exposes 6 tools to a connected 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.
Score
72 / 100
Good
- Documentation22/25
- Maintenance16/25
- Trust16/20
- Capability6/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 75 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 6 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.1.2Latest | Jun 17, 2026 |