Brummer MCP

MCPAI代理

提供方 standardbeagle

AI代理 HTTP · 远程 无需鉴权 社区 / 第三方
查看接入方式

Allows external tools (VSCode, Claude Code, etc.) to access log output and errors, execute commands asynchronously, and monitor process status.

一句话选型结论

按资料字段整理

Brummer MCP 属于AI代理类 MCP 服务器,HTTP · 远程,无需鉴权,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权无需鉴权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 无需鉴权
连远程 HTTPS 端点,通常为 Streamable HTTP
npx 运行(无需安装)

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Brummer MCP当前 未标注 HTTP · 远程 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方standardbeagle上游标注的维护方 standardbeagle
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.5 KB
来自项目仓库与上游目录的原文,未做删改

🐝 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: https://dev.standardbeagle.com/brummer/

Quick links:
- Getting Started Guide
- Installation Options
- MCP Integration

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
  • 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)

🐧 Linux/macOS```bash
curl -sSL https://raw.githubusercontent.com/standardbeagle/brummer/main/quick-install.sh | bash


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

🪟 Windows (PowerShell)```powershell
irm https://raw.githubusercontent.com/standardbeagle/brummer/main/quick-install.ps1 | iex


### Package Managers

📦 NPM/NPX```bash
# Run directly with npx (no installation)
npx @standardbeagle/brum

# Install globally
npm install -g @standardbeagle/brum

# Or with yarn
yarn global add @standardbeagle/brum

# Or with pnpm
pnpm add -g @standardbeagle/brum

🐹 Go Install```bash
go install github.com/standardbeagle/brummer/cmd/brum@latest


### Install from Source

Build from source```bash
# Clone the repository
git clone https://github.com/standardbeagle/brummer
cd brummer

# Using Make (recommended)
make install-user    # Install for current user (~/.local/bin)
# OR
make install        # Install system-wide (requires sudo)

# Using the interactive installer
./install.sh

# Manual build
go build -o brum ./cmd/brum
mv brum ~/.local/bin/  # Add to PATH

Usage

Basic Usage

In a directory with a package.json file:```bash
brum


### Options```bash
brum [flags]

Flags:
  -d, --dir string   Working directory containing package.json (default ".")
  -p, --port int     MCP server port (default 7777)
      --no-mcp       Disable MCP server
      --settings     Show current configuration settings with sources
  -h, --help         help for brum

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```bash

Show current settings with source files

brum --settings

Create a configuration file from current settings

brum --settings > .brum.example.toml


### Configuration Options

Create a `.brum.toml` file in your project or home directory:```toml
# Package manager preference
preferred_package_manager = "pnpm"  # npm, yarn, pnpm, bun

# MCP Server settings
mcp_port = 7777
no_mcp = false

# Proxy settings
proxy_port = 19888
proxy_mode = "reverse"  # "reverse" or "full"
proxy_url = "http://localhost:3000"  # Optional: auto-proxy this URL
standard_proxy = false
no_proxy = false

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:json { "servers": { "brummer-hub": { "command": "brum", "args": ["--mcp"] } } }

  2. Run brummer in each project:bash 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```javascript

// SSE streaming connection
const eventSource = new EventSource('http://localhost:7777/mcp');
eventSource.onmessage = (event) => {
const msg = JSON.parse(event.data);
console.log('Received:', msg);
};

// Send JSON-RPC requests
fetch('http://localhost:7777/mcp', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Accept': 'application/json'
},
body: JSON.stringify({
jsonrpc: '2.0',
id: 1,
method: 'tools/list'
})
});


### 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```bash
brum -d ~/projects/my-app

Run with custom MCP port```bash

brum -p 8888


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

Run in headless mode (MCP server only)```bash

brum --no-tui


## Development

### Project Structure```
brummer/
├── cmd/brum/            # Main application entry point
├── internal/
│   ├── tui/             # Terminal UI components
│   ├── process/         # Process management
│   ├── mcp/             # MCP server implementation
│   ├── logs/            # Log storage and detection
│   └── parser/          # Package.json parsing
├── pkg/
│   ├── events/          # Event system
│   └── filters/         # Log filtering
└── go.mod

Building```bash

go build -o brum ./cmd/brum


### Testing```bash
go test ./...

License

MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Brummer MCP 怎么安装?

在客户端按下面的安装命令接入:npx 运行(无需安装)。装完在客户端配置里引用同一个包或端点。

Brummer MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Brummer MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Brummer MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Brummer MCP 能提供哪些能力?

资料显示能力标签包括 日志管理、实时监控、JavaScript、HTTP。具体工具清单以官方文档为准。

Brummer MCP 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

Brummer MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。