Flarelink MCP server
✓ VerifiedEnables AI coding tools to build applications using the Flarelink stack, including Cloudflare auth, D1, and R2, with built-in security and cost rules.
Also known as flarelink-dev/mcp, mcp, @flarelink/mcp
- Stars
- 1
- Tools
- 11
- Downloads, 30 days
- 268
- Latest version
- 0.1.2
- Last commit
- Jun 17, 2026
- License
- MIT
What is Flarelink MCP?
Flarelink enables AI coding tools to build applications using the Flarelink stack, including Cloudflare auth, D1, and R2, with built-in security and cost rules. It exposes 11 tools, such as flarelink_stack_overview, flarelink_scaffold, flarelink_list_patterns.
Summary generated from the project's README
About Flarelink MCP server
Building applications on the Flarelink stack becomes more accurate when AI coding tools like Cursor, Claude Code, or Windsurf use this server to understand specific security and cost constraints. It provides agents with the necessary knowledge regarding Cloudflare auth using better-auth and KV sessions, D1 databases, and R2 storage. By providing these rules upfront, the server helps prevent common mistakes in user-scoping, SQL safety, and R2 presigned URLs.
Developers can run the server using npx without a formal installation. While the knowledge and scaffolding tools work without credentials, providing a FLARELINK_API_KEY enables management capabilities. This allows an agent to interact directly with live projects by listing databases, querying D1 with parameterized SQL, or managing R2 buckets. The server acts as a bridge between the AI agent and the Flarelink dashboard API, turning the editor into a command center for Cloudflare-based development.
Written from the project's README. Every use case is checked against a quote from it.
How to install Flarelink MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Flarelink MCP in Claude Code
$ claude mcp add --env 'FLARELINK_API_KEY=<YOUR_FLARELINK_API_KEY>' mcp -- npx -y @flarelink/mcpInstall Flarelink MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
],
"env": {
"FLARELINK_API_KEY": "<YOUR_FLARELINK_API_KEY>"
}
}
}
}Install Flarelink MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
],
"env": {
"FLARELINK_API_KEY": "<YOUR_FLARELINK_API_KEY>"
}
}
}
}Install Flarelink MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@flarelink/mcp"],"env":{"FLARELINK_API_KEY":"<YOUR_FLARELINK_API_KEY>"}}'Install Flarelink MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
],
"env": {
"FLARELINK_API_KEY": "<YOUR_FLARELINK_API_KEY>"
}
}
}
}Install Flarelink MCP in Codex
$ codex mcp add mcp --env 'FLARELINK_API_KEY=<YOUR_FLARELINK_API_KEY>' -- npx -y @flarelink/mcpInstall Flarelink MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@flarelink/mcp"] [mcp_servers.mcp.env] FLARELINK_API_KEY = "<YOUR_FLARELINK_API_KEY>"
Install Flarelink MCP in Gemini CLI
$ gemini mcp add -s user -e 'FLARELINK_API_KEY=<YOUR_FLARELINK_API_KEY>' mcp npx -- -y @flarelink/mcpInstall Flarelink MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
],
"env": {
"FLARELINK_API_KEY": "<YOUR_FLARELINK_API_KEY>"
}
}
}
}Flarelink MCP tools 11
Detected from the READMEflarelink_stack_overviewflarelink_scaffoldflarelink_list_patternsflarelink_get_patternflarelink_sdk_referenceflarelink_cost_patternsflarelink_whoamiflarelink_list_projectsflarelink_list_databasesflarelink_query_databaseflarelink_list_buckets
| flarelink_stack_overview | — | |
| flarelink_scaffold | — | |
| flarelink_list_patterns | — | |
| flarelink_get_pattern | — | |
| flarelink_sdk_reference | — | |
| flarelink_cost_patterns | — | |
| flarelink_whoami | — | |
| flarelink_list_projects | — | |
| flarelink_list_databases | — | |
| flarelink_query_database | — | |
| flarelink_list_buckets | — |
Configuration
FLARELINK_API_KEYSecretOptional. Personal API key from dash.flarelink.dev → API keys. Enables the project-management tools; the knowledge & scaffolding tools work without it.
| Name | Description | |
|---|---|---|
| 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. | Secret |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableflarelink-dev/mcp is public and reachablegithub.com/flarelink-dev/mcp ↗Pass
- Package names this repository as its source@flarelink/mcp names flarelink-dev/mcp as sourcenpmjs.com/package/@flarelink/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-06-17github.com/flarelink-dev/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @flarelink/mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model11 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@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.
Flarelink MCP questions
How do I add Flarelink MCP to Claude Code?
Run claude mcp add --env 'FLARELINK_API_KEY=<YOUR_FLARELINK_API_KEY>' mcp -- npx -y @flarelink/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Flarelink MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Flarelink MCP provide?
It exposes 11 tools, including flarelink_stack_overview, flarelink_scaffold, flarelink_list_patterns, flarelink_get_pattern, flarelink_sdk_reference.
How can I install the Flarelink MCP server?
You can run it using npx without a traditional installation.
What management tools are available with an API key?
With an API key, you can list projects, list D1 databases, run parameterized SQL queries, and list R2 buckets.