Server data from the Official MCP Registry
Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.
Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.
Valid MCP server (2 strong, 2 medium validity signals). 1 known CVE in dependencies Package registry verified. Imported from the Official MCP Registry.
7 files analyzed · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: FLARELINK_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"dev-flarelink-mcp": {
"env": {
"FLARELINK_API_KEY": "your-flarelink-api-key-here"
},
"args": [
"-y",
"@flarelink/mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.
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.
| 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.
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.
MIT. Part of Flarelink — the dashboard for the Cloudflare developer stack.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.