🐝 Brummer

Your Terminal UI Development Buddy with intelligent monitoring

A TUI (Terminal User Interface) for managing npm/yarn/pnpm/bun scripts with integrated MCP server for external tool access. Brummer provides intelligent log management, real-time monitoring, and seamless integration with development tools.

📖 Documentation

📚 Full documentation available at:

Quick links:

• Getting Started Guide

• Installation Options

• MCP Integration

Related MCP server: mcp-wcgw

Features

• Multi-Package Manager Support: Automatically detects and uses npm, yarn, pnpm, or bun

• Monorepo Support: Full support for pnpm workspaces, npm workspaces, yarn workspaces, Lerna, Nx, and Rush

• Multi-Language Detection: Auto-detects commands for Node.js, Go, Rust, Java (Gradle/Maven), .NET, Python, Ruby, PHP, Flutter, and more

• Interactive TUI: Navigate through scripts, monitor processes, and view logs in real-time

• Smart Log Management:

  • Automatic error detection and prioritization

  • Log filtering and search capabilities

  • Build event and test result detection

• MCP Server Integration: Allows external tools (VSCode, Claude Code, etc.) to:

  • Access log output and errors

  • Execute commands asynchronously

  • Monitor process status

• Process Management: Start, stop, and monitor multiple processes simultaneously

• VS Code Tasks: Detects and runs VS Code tasks from .vscode/tasks.json

• Environment Variable Management (Planned):

  • Unified .env file management with multi-format support

  • TUI view for browsing and editing environment variables

  • Automatic injection for scripts and AI agents

  • Secret detection and masking for security

Installation

Quick Install (One-Liner)

Or with wget:

Package Managers

Install from Source

Usage

Basic Usage

In a directory with a package.json file:

Options

TUI Navigation

• Tab: Switch between views (Scripts, Processes, Logs, Errors, URLs, Settings)

• ↑/↓ or j/k: Navigate items

• Enter: Select/execute

• n: Open run command dialog (from Scripts tab)

• Esc or q: Go back

• /: Search logs

• p: Toggle high-priority logs

Process Management

• Navigate: Use ↑/↓ arrows to select a process (shows status with colored indicators)

• s: Stop selected process (only works on running processes 🟢)

• r: Restart selected process (stops then starts the same script)

• Ctrl+R: Restart all running processes

• Enter: View logs for selected process

Process Status Indicators:

• 🟢 Running - Process is active (can stop/restart)

• 🔴 Stopped - Process was manually stopped

• ❌ Failed - Process exited with error

• ✅ Success - Process completed successfully

• ⏸️ Pending - Process is starting up

Automatic Cleanup:

• All running processes are automatically stopped when Brummer exits

• Use Ctrl+C or 'q' to quit with graceful cleanup

• Process count shown in header: "Running Processes (2)"

Log Management

• c: Copy most recent error to clipboard

• f: View/manage filters

Other

• ?: Show help

• Ctrl+C: Quit

Configuration

Brummer supports hierarchical configuration through .brum.toml files. Configuration is loaded in the following order (later values override earlier ones):

1. ~/.brum.toml (global user settings)

2. Project root and parent directories (walking up to root)

3. Current working directory .brum.toml

Viewing Current Configuration

Configuration Options

Create a .brum.toml file in your project or home directory:

Settings Tab

The Settings tab provides:

• Package Manager Selection: Choose between npm, yarn, pnpm, or bun

• MCP Server Installation: One-click installation for development tools:

  • Claude Desktop ✓

  • Claude Code ✓

  • Cursor ✓

  • VSCode (with MCP extension) ✓

  • Cline ✓

  • Windsurf ✓

  • Roo Code (experimental)

  • Augment (experimental)

  • Cody (experimental)

MCP Hub Mode 🆕

Brummer Hub Mode enables MCP clients to discover and control multiple brummer instances through a single connection:

Quick Setup

1. Configure your MCP client once:

   { "servers": { "brummer-hub": { "command": "brum", "args": ["--mcp"] } } }

2. Run brummer in each project:

   cd ~/projects/frontend && brum cd ~/projects/backend && brum

3. Use hub tools in your MCP client:

   • instances/list - See all running instances

   • instances/connect - Connect to a specific instance

   • All instance tools become available with prefixes

📚 Full Hub Mode Documentation

MCP Server Integration

The MCP server runs on port 7777 by default and implements the official MCP Streamable HTTP transport protocol:

Transport Protocol

Single Endpoint: http://localhost:7777/mcp

Connection Types:

1. Standard JSON-RPC (POST with Accept: application/json)

2. Server-Sent Events (GET with Accept: text/event-stream)

3. SSE Response (POST with Accept: text/event-stream)

Example Connection

Available Tools

Script Management: scripts_list, scripts_run, scripts_stop, scripts_status Log Management: logs_stream, logs_search Browser Tools: browser_open, browser_screenshot, browser_navigate, repl_execute Proxy Tools: proxy_requests Telemetry: telemetry_sessions, telemetry_events

Examples

Run in a specific directory

Run with custom MCP port

Run without MCP server (TUI only)

Run in headless mode (MCP server only)

Development

Project Structure

Building

Testing

License

MIT