Flow Nexus MCP Server

What the code does

We read the source, 17 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

      const result = execSync(ghCommand, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add flow-nexus -- npx -y flow-nexus

{
  "mcpServers": {
    "flow-nexus": {
      "args": [
        "-y",
        "flow-nexus"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.flow-nexus]
command = "npx"
args = ["-y", "flow-nexus"]

{
  "mcpServers": {
    "flow-nexus": {
      "args": [
        "-y",
        "flow-nexus"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "flow-nexus": {
      "args": [
        "-y",
        "flow-nexus"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: FLOW_NEXUS_API_KEY (API key for Flow Nexus authentication), FLOW_NEXUS_BASE_URL (Base URL for Flow Nexus API), E2B_API_KEY (E2B API key for sandbox creation), ANTHROPIC_API_KEY (Anthropic API key for Claude integration). The author declared them in the registry entry; get the values from the project itself.