Developer · Local MCP server
Flarelink
Build on the Flarelink stack - Cloudflare auth, D1, and R2 - from your AI coding tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.flarelink/mcp- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-17
- Updated
- 2026-06-17
- Publisher
- dev.flarelink
- Namespace
- Namespace verified by the MCP Registry via the domain flarelink.dev · how
- Listed under
- Cloudflare MCP servers
- Website
- flarelink.dev
- Repository
- github.com/flarelink-dev/mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @flarelink/mcp | 0.1.2 | stdio |
How to connect Flarelink
Flarelink runs locally from a Node.js package published to the npm registry: @flarelink/mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @flarelink/mcp@0.1.2. It reads the environment variable FLARELINK_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp@0.1.2"
],
"env": {
"FLARELINK_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| FlagrixScan GitHub repos and profiles for malware before cloning - commit-pinned risk verdicts for agents. | Local · stdio |
| Flakiness Knowledge Graph MCPMCP server + Playwright reporter that builds a flakiness knowledge graph from test run history. | Local · stdio |
| Flaky History MCPLocal aggregate test-history stability analysis without test names or raw result contents. Tools... | Local · stdio |
| FlareScan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys. | Local · stdio |
| Flathub MCPSearch Linux apps on Flathub. No key required. | Local · stdio |
| Fleet MCPAn MCP server that provides tools for managing and monitoring your Fleet Device Management instance. | Local · stdio |
| FleximManage Flexim CMS content and Suggested Topics from compatible AI clients. | Remote · HTTP |
| Flipside MCPFlipside Crypto SQL API: run queries, check status, fetch results. | Local · stdio |