LabscoMCP early access ↗
gojueMCP SERVER · OFFICIAL PROJECT

MoLing MCP Server

A single binary that gives an assistant your files, your terminal and a browser — nothing else to install.

by gojue ↗Desktop & OS Automation✓ Official

LABSCO SUMMARY

Dependency-free is the whole argument — and the terminal tool is why you should read the config before starting it.

Nothing to install means no Node, Python or Docker version conflicts, which is genuinely the friction most local servers create. The trade is scope: this hands an assistant shell command execution, and the project says so plainly. Testing so far has been on macOS, so other platforms may surprise you.

What it is

A computer-use and browser-use server written in Go, talking to the operating system directly. One downloaded binary, no runtime to set up.

What you get

  • File system operations — reading, writing, merging, statistics and aggregation
  • A command-line terminal for executing system commands
  • Browser control powered by chromedp, which needs Chrome installed
  • Stdio mode for interactive use and SSE mode for headless or automated environments
  • Moling client --install, which detects your MCP client — Cline, Claude, Roo Code — and writes the configuration for you

Requirements

The binary, from the install script or the releases page — no Node.js, Python or Docker anywhere in the setup. Chrome for the browser tools; on Windows its full path must be in the system environment variables. Configuration is generated at ~/.moling/config/config.json, or created with moling config --init. The project notes it has only been tested on macOS.

Setup effort

One command — /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/gojue/moling/HEAD/install/install.sh)"

See installation options