Void Stack

by Mague

387 downloads

Not rated

GitHub

About

DSM for developers — start, stop, audit, and analyze your entire dev stack with one command. MCP server with 27 tools for Claude Desktop & Claude Code. Supports Windows, WSL, macOS, Linux, and Docker. Built in Rust.

Details

Author: Mague
Downloads: 387
Categories: Other, Developer Tools, Infrastructure

- Multi-service start/stop individually or together
- Cross-platform: Windows, macOS, Linux (WSL, Docker)
- Auto-detection of Python, Node, Rust, Go, Flutter, Docker
- Smart commands for FastAPI, Flask, Django, Vite, Next.js, Express, and more
- Dependency checking and pre-launch hooks (venv creation, pip/npm install)
- Live logs with automatic URL detection from all services
- Code analysis: dependency graphs, anti-patterns, cyclomatic complexity, coverage
- Security audit: vulnerabilities, hardcoded secrets, injection patterns
- Technical debt tracking with metric snapshots and trend comparison
- MCP server with 20+ tools for AI integration

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Void Stack

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

From the repository

Install a pre-built binary from the Releases page, or build from source using Cargo. Register a project with void add my-app /path/to/project (auto-detects services) and start it with void start my-app. For an interactive dashboard, run void-tui my-app. Void Stack also provides a desktop app (void-stack-desktop) and an MCP server (void-stack-mcp) for AI tools.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "void stack": {
            "void-stack": {
                "command": "cargo",
                "args": [
                    "install",
                    "--git",
                    "https://github.com/mague/void-stack",
                    "void-stack-mcp"
                ]
            }
        }
    }
}

McpServers

{
    "void-stack": {
        "command": "cargo",
        "args": [
            "install",
            "--git",
            "https://github.com/mague/void-stack",
            "void-stack-mcp"
        ]
    }
}

<p align="center">

</p>

<h1 align="center">Void Stack</h1>

[]()
[]()

Got 10 projects with backends, frontends, workers, and databases — and you can't remember how to start any of them?

Void Stack fixes that. One command to start your entire dev stack — backend, frontend, database, workers — on Windows, WSL, or Docker. No memorizing ports, no opening 5 terminals, no reading outdated READMEs.

``bash void add my-app F:\projects\my-app # Auto-detects services void start my-app # Starts everything`That's it. Void Stack scans your project, detects which frameworks you're using (FastAPI, Vite, Express, Django...), generates the right commands, and runs them. If there's a Python venv, it finds it. Ifnode_modulesis missing, it tells you. > High Performance — Built with Rust. Zero runtime overhead, instant startup, minimal memory footprint. > Agentic Workflow — MCP server with 20+ tools lets Claude Desktop / Claude Code manage your services, analyze code, and audit security autonomously. > Cloud-Native Roadmap — Deploy to Vercel, DigitalOcean, and more from the same config (coming soon). Leer en español | void-stack.dev <div align="center"> <br/><br/> </div> ---

`Dogfooding: Void Stack analyzes itself`






Void Stack's own analysis and audit tools are used to maintain the quality of its codebase. Here's what running

void analyze void-stack --compare and void audit void-stack

 on the project itself revealed — and how we used those findings to improve the code:



Security audit

bash

void audit void-stack

Risk Score: 2/100



2 low findings (innerHTML usage — already mitigated with DOMPurify)





The initial audit found 6 issues (risk score 25/100), but 4 were false positives — regex patterns and templates in the detection code flagged as "secrets". This led us to add smart false-positive filtering (self-referencing file allowlist, regex metacharacter detection, template line filtering), dropping the false positive rate from 83% to 0%.



Code analysis

bash

void analyze void-stack --compare --label v0.17.0

Pattern: Clean / Hexagonal (85% confidence)



115 modules, 20,735 LOC, 30 external deps



Max complexity: 42 (analyze_best_practices) — now refactored to ~15



Anti-patterns: 23 → reduced High severity from 7 to 3





Findings that drove refactoring:



| Finding | Action taken |

|---------|-------------|

| God Class:

cli/main.rs

 (1202 LOC, 25 fn) | Split into 6 command modules (~250 LOC main) |

| God Class:

mcp/server.rs

 (1197 LOC, 35 fn) | Split into 10 tool modules (~340 LOC server) |

| God Class:

manager.rs

 (30 fn) | Split into 4 submodules (process, state, logs, url) |

| God Class + Fat Controller:

vuln_patterns.rs

 (789 LOC) | Split into 5 category modules (injection, xss, network, crypto, config) |

| God Class:

db_models.rs

 (1065 LOC) | Split into 7 submodules by DB format (python, sequelize, gorm, drift, proto, prisma) |

| God Class:

generate_dockerfile.rs

 (821 LOC) | Split into 6 submodules by language (python, node, rust, go, flutter) |

| God Class:

api_routes.rs

 (747 LOC) | Split into 5 submodules by protocol (python, node, grpc, swagger) |

| God Class:

architecture.rs

 (788 LOC) | Split into 4 submodules (externals, crates, infra) |

| God Class:

classifier.rs

 (759 LOC, 44 fn) | Split into 3 submodules (logic, signals/data tables, tests) |

| Fat Controller:

cli/analysis.rs

 (580 LOC) | Split into 4 submodules (analyze, diagram, audit, suggest) |

| CC=42:

analyze_best_practices

 | Table-driven linter registry (CC ~15) |

| CC=41:

cmd_analyze

 | Extracted 11 helper functions (CC ~10) |



Technical debt tracking

bash

void analyze void-stack --compare --label v0.22.0

Pattern: Clean / Hexagonal (85% confidence)



Coverage: 80.5% (26268/32609 lines) [lcov]



Explicit debt: 15 markers (TODO: 8, FIXME: 4, HACK: 2, OPTIMIZE: 1)



669 tests passing





New in v0.22.0: explicit debt markers (TODO/FIXME/HACK/XXX/OPTIMIZE/BUG/TEMP/WORKAROUND) are now scanned from source comments and shown in CLI output, markdown reports, and the desktop Debt tab. Complex functions (CC≥10) are cross-referenced with coverage data — uncovered critical functions get

[!]

 warnings in CLI and 🔴 indicators in markdown.



---



Interfaces






Void Stack has 4 interfaces — use whichever you prefer:



| Interface | Description |

|-----------|-------------|

| CLI (

void

) | Fast commands from terminal |

| TUI (

void-stack-tui

) | Interactive terminal dashboard: services, analysis, security audit, debt, space |

| Desktop (

void-stack-desktop

) | Desktop app with GUI (Tauri + React) — Windows (.msi), macOS (.dmg), Linux (.deb) |

| MCP Server (

void-stack-mcp

) | Integration with Claude Desktop / Claude Code |



End-to-end example: FastAPI + React in 30 seconds






Say you have a project with a FastAPI backend and a React frontend:



my-app/

├── backend/       # FastAPI with venv

│   ├── main.py    # from fastapi import FastAPI

│   └── .venv/

├── frontend/      # React with Vite

│   ├── package.json

│   └── src/

└── .env

bash

1. Register the project (scans and detects services)



void add my-app F:\projects\my-app



Void Stack detects:



  ✓ backend  → uvicorn main:app --host 0.0.0.0 --port 8000



  ✓ frontend → npm run dev



  ✓ .venv    → auto-resolves python to virtualenv






2. Check dependencies



void check my-app

  ✅ Python 3.11 (venv detected)



  ✅ Node 20.x (node_modules up to date)



  ✅ .env complete vs .env.example






3. Start everything



void start my-app

  [backend]  → http://localhost:8000



  [frontend] → http://localhost:5173






4. Or open the interactive dashboard



void-tui my-app





Installation






Binaries (recommended)






Download pre-built binaries from the Releases page — no Rust required.



| Platform | File |

|----------|------|

| Windows  |

.msi / .exe

 (NSIS) |

| macOS    |

.dmg

 |

| Linux    |

.deb / .AppImage

 |



> macOS note: If you get "cannot be opened because the developer cannot be verified", run:

>

bash

> xattr -cr /Applications/Void\ Stack.app

>





From source (Cargo)

``bash

Core CLI (the main tool)

cargo install --git https://github.com/mague/void-stack void-stack-cli

TUI Dashboard

cargo install --git https://github.com/mague/void-stack void-stack-tui

MCP Server (for AI integration with Claude Desktop / Claude Code)

cargo install --git https://github.com/mague/void-stack void-stack-mcp

gRPC Daemon (optiona

…

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

Dogfooding: Void Stack analyzes itself

Security audit

Risk Score: 2/100

2 low findings (innerHTML usage — already mitigated with DOMPurify)

Code analysis

Pattern: Clean / Hexagonal (85% confidence)

115 modules, 20,735 LOC, 30 external deps

Max complexity: 42 (analyze_best_practices) — now refactored to ~15

Anti-patterns: 23 → reduced High severity from 7 to 3

Technical debt tracking

Pattern: Clean / Hexagonal (85% confidence)

Coverage: 80.5% (26268/32609 lines) [lcov]

Explicit debt: 15 markers (TODO: 8, FIXME: 4, HACK: 2, OPTIMIZE: 1)

669 tests passing

Interfaces

End-to-end example: FastAPI + React in 30 seconds

1. Register the project (scans and detects services)

Void Stack detects:

✓ backend → uvicorn main:app --host 0.0.0.0 --port 8000

✓ frontend → npm run dev

✓ .venv → auto-resolves python to virtualenv

2. Check dependencies

✅ Python 3.11 (venv detected)

✅ Node 20.x (node_modules up to date)

✅ .env complete vs .env.example

3. Start everything

[backend] → http://localhost:8000

[frontend] → http://localhost:5173

4. Or open the interactive dashboard

Installation

Binaries (recommended)

From source (Cargo)

Core CLI (the main tool)

TUI Dashboard

MCP Server (for AI integration with Claude Desktop / Claude Code)

gRPC Daemon (optiona

Install

More like this

Sequential Thinking

Sentry

Github

Filesystem

EverArt

Google Drive

`Dogfooding: Void Stack analyzes itself`