Brummer

Brummer includes an MCP server that exposes process, log, and tool access to external clients. You can monitor and control your local development environment from editors and automation tools, while keeping logs centralized, actions asynchronous, and work across multiple packages and languages streamlined through a unified MCP interface.

How to use

You run Brummer in a project directory containing a package manifest and then connect external MCP clients to its server. The MCP server lets tools like editors or automation scripts discover running processes, stream logs, and issue commands to manage scripts across multiple workspaces. From an MCP client you can list available scripts, start and stop processes, monitor status, and pull real-time log updates. You can also access log output and errors from running tasks, enabling automated workflows and integrations.

How to install

Prerequisites: you should have a supported runtime installed on your system (Go for building Brummer, and Node.js if you plan to install via npm/npx). Ensure you have a working internet connection to fetch dependencies.

Basic setup steps to get Brummer running in your project:

1. Install via one of the supported methods (choose one):

bash
# Quick install for Unix-like systems (Linux/macOS)
curl -sSL https://raw.githubusercontent.com/standardbeagle/brummer/main/quick-install.sh | bash

# Or via wget
wget -qO- https://raw.githubusercontent.com/standardbeagle/brummer/main/quick-install.sh | bash

# Windows PowerShell (administrative privileges may be required)
ir https://raw.githubusercontent.com/standardbeagle/brummer/main/quick-install.ps1 | iex

How to install

2. Install as a Go binary (if you prefer building from source or using Go tooling):

# Go installation of the latest Brummer binary
go install github.com/standardbeagle/brummer/cmd/brum@latest

How to install

3. Run Brummer in your project directory to start the TUI and MCP server (default port is 7777):

# Run in current directory
brum

# Run with a specific working directory
brum -d /path/to/your/project

# Run with a custom MCP port
brum -p 8888

# Run without the MCP server (TUI only)
brum --no-mcp

Available tools

scripts_list

List available scripts across workspaces for quick reference and execution.

scripts_run

Start a selected script and monitor its process through the MCP interface.

scripts_stop

Stop a running script from the MCP client.

scripts_status

Query the status of scripts and their processes.

logs_stream

Stream real-time logs from active processes to the MCP client.

logs_search

Search and filter logs to quickly locate errors or important events.

browser_open

Open a URL in a connected browser context via MCP tools.

browser_screenshot

Capture screenshots from a remote browser session through MCP.

browser_navigate

Navigate to a URL within the connected browser controlled by MCP.

repl_execute

Execute a REPL or commands in a remote environment via MCP.

proxy_requests

Proxy tool to forward requests through the MCP environment.

telemetry_sessions

Track user sessions and collect telemetry data for the MCP server.

telemetry_events

Record and report events for MCP usage analytics.