Developer · Local MCP server
Flow Nexus
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ruvnet/flow-nexus- Version
- 0.1.121
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2025-09-10
- Updated
- 2025-09-10
- Publisher
- ruvnet (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ruvnet) · how
- Repository
- github.com/ruvnet/flow-nexus
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | flow-nexus | 0.1.121 | stdio |
How to connect Flow Nexus
Flow Nexus runs locally from a Node.js package published to the npm registry: flow-nexus version 0.1.121. 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 flow-nexus@0.1.121. It reads these environment variables: FLOW_NEXUS_API_KEY (secret), FLOW_NEXUS_BASE_URL, E2B_API_KEY (secret) and ANTHROPIC_API_KEY (secret); set them 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": {
"flow-nexus": {
"command": "npx",
"args": [
"-y",
"flow-nexus@0.1.121"
],
"env": {
"FLOW_NEXUS_API_KEY": "<secret>",
"FLOW_NEXUS_BASE_URL": "<value>",
"E2B_API_KEY": "<secret>",
"ANTHROPIC_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 from ruvnet (GitHub)
| Server | Runs |
|---|---|
| Claude FlowAI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev. | Local · stdio |
| Ruv SwarmNeural network swarm orchestration with WebAssembly acceleration and MCP integration. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| 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 |
| FloomDeploy Python functions as web apps with auto-generated UI, REST API, and shareable links. | Local · stdio |
| FlootBuild and publish full-stack web and mobile apps on Floot from any MCP client. Building is free. | Remote · HTTPLive check: sign-in required |
| FlowboardDiscover cloud shapes and create, inspect, validate, patch, and review architecture diagrams. | Remote · HTTPLive check: ✓ handshake |
| FlowCastleBuild, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. | Remote · HTTPLive check: ✓ handshake |
| FlowSentrySecurity scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API. | Remote · HTTPLive check: ✗ no handshake |
| FluidTalkCreate AI Characters and generate their DM and comment replies from any MCP client. | Remote · HTTPLive check: sign-in required |