Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Static dataflow analysis, program slicing, linting, and dependency extraction for R code.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"flowr": {
"command": "npx",
"args": [
"-y",
"@eagleoutice/flowr-mcp"
]
}
}
}Run this in your terminal
claude mcp add flowr -- npx -y @eagleoutice/flowr-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"flowr": {
"command": "npx",
"args": [
"-y",
"@eagleoutice/flowr-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"flowr": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@eagleoutice/flowr-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account flowr-analysis, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 15 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server with a single query tool that lets LLM clients analyze R code with flowR: slicing, linting, dependencies, version guessing, signature database search, and every other query of the Query API. No R installation is needed.
On its first start, the server downloads flowR's signature database (about 66 MB) from the flowR releases into ~/.cache/flowr and checks its hash. Version guessing and signature search need this database. Everything else also works offline. The server never runs the analyzed code. It contacts no other server, unless a query asks the linter to check the URLs in the code (checkUrls, which is never allowed over HTTP).
In Claude Code, one plugin installs both this server and the flowR skill:
/plugin install flowr --marketplace flowr-analysis/flowr
Other local clients start it over stdio:
claude mcp add flowr -- npx -y --omit=optional --ignore-scripts @eagleoutice/flowr-mcp # Claude Code
codex mcp add flowr -- npx -y --omit=optional --ignore-scripts @eagleoutice/flowr-mcp # OpenAI Codex gemini mcp add flowr npx -y --omit=optional --ignore-scripts @eagleoutice/flowr-mcp # Gemini CLI
or, configured by JSON (Claude Desktop, Cursor, VS Code, ...):
{ "mcpServers": { "flowr": { "command": "npx", "args": ["-y", "--omit=optional", "--ignore-scripts", "@eagleoutice/flowr-mcp"] } } }
The flags keep the install small. They skip the optional dependencies flowR does not need here, and they run no install scripts. The package's npm-shrinkwrap.json pins every dependency.
Remote clients (ChatGPT, claude.ai, ...) need the server running over HTTP behind HTTPS:
npx -y --omit=optional --ignore-scripts @eagleoutice/flowr-mcp --http 1042
cloudflared tunnel --url http://localhost:1042
Then add https:// /mcp as a connector (in ChatGPT, this needs developer mode). Without a port, the server uses $PORT or 1042. It listens on 127.0.0.1 unless HOST says otherwise, for example HOST=0.0.0.0 in a container. Setting FLOWR_MCP_PATH=/mcp/ replaces /mcp with a secret path. A secret path is the only access control that every remote client supports.
Over HTTP, the server treats the code as untrusted:
files argument, source() is ignored, and the config query is refused.Put a rate limit in front of a public instance.
SKILL.md is an agent skill (Claude, Codex, Gemini CLI, ...) that says when and how to use flowR, with or without this server. To use it, copy it to, for example, ~/.claude/skills/flowr/SKILL.md.