{
  "markdown": "# @flarelink/mcp\n\nAn [MCP](https://modelcontextprotocol.io) 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.\n\nIt 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.\n\n## Install\n\nNo install needed — run it with `npx`. Add it to your tool's MCP config:\n\n**Claude Code**\n\n```bash\nclaude mcp add flarelink -- npx -y @flarelink/mcp\n```\n\n**Cursor / Windsurf / Claude Desktop** (`mcp.json` / config):\n\n```json\n{\n  \"mcpServers\": {\n    \"flarelink\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@flarelink/mcp\"],\n      \"env\": { \"FLARELINK_API_KEY\": \"flk_…\" }\n    }\n  }\n}\n```\n\nThe `FLARELINK_API_KEY` is **optional**. Without it you still get all the\nknowledge + scaffolding tools. With it, the **management tools** (below) can\ndrive your actual Flarelink projects. Mint a key at\n[dash.flarelink.dev → API keys](https://dash.flarelink.dev).\n\n## Tools\n\n| Tool | What it gives the agent |\n| --- | --- |\n| `flarelink_stack_overview` | The stack, cardinal rules, and deployment shapes. Read first. |\n| `flarelink_scaffold` | How to bootstrap a complete working app (clone / one-click deploy) + file map. |\n| `flarelink_list_patterns` | The catalog of canonical code patterns. |\n| `flarelink_get_pattern` | Copy-pasteable code for one recipe (auth setup, route guards, identifier-safe D1, R2 upload/presign, wrangler bindings, SDK usage). |\n| `flarelink_sdk_reference` | `@flarelink/client` signatures + return shapes (auth / storage / db). |\n| `flarelink_cost_patterns` | Cloudflare cost-optimization guidance, with targeted hints for the feature you describe. |\n\nIt also exposes the stack guide as a resource (`flarelink://stack-guide`) you can attach as context.\n\n### Management tools (need `FLARELINK_API_KEY`)\n\nDrive your actual Flarelink projects from the editor. These route through the Flarelink dashboard API and act exactly as you would in the UI.\n\n| Tool | What it does |\n| --- | --- |\n| `flarelink_whoami` | Verify the key; show the user + active connection/project. |\n| `flarelink_list_projects` | List projects on the active Cloudflare connection. |\n| `flarelink_list_databases` | List the project's D1 databases. |\n| `flarelink_query_database` | Run a (parameterized) SQL statement against a project D1. |\n| `flarelink_list_buckets` | List the project's R2 buckets. |\n\nWithout 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.\n\n## License\n\nMIT. Part of [Flarelink](https://flarelink.dev) — the dashboard for the Cloudflare developer stack.\n",
  "bytes": 2868,
  "sha": "7a957c21ce7632fcebfb79aa070b9a2d61e785a36a63d044b6b505a6021a2269",
  "repo_slug": "flarelink-dev/mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_flarelink_dev_mcp_22cf80db/readme"
}