mcplsb

Give your MCP-enabled coding assistant the code intelligence of your installed language servers. mcplsb finds symbols, follows definitions and references, inspects types, and returns diagnostics and bounded source context.

mcplsb supports Node.js 22.0.0 or newer. On Node 22.0.0, use its compatible bundled npm 10. The npm 12 examples below require a Node version that meets npm's own runtime requirements.

Install with a compatible Node.js version and npm 12:

npm install --global [email protected] --allow-scripts=mcplsb
mcplsb --version

With npm 10 or 11, omit --allow-scripts=mcplsb and keep installation scripts enabled. For a one-off npm 12 command, use:

npx --yes --allow-scripts=mcplsb [email protected] --version

The installation hook downloads one verified, exact-version native archive from GitHub for Linux, macOS, or Windows on x64 or ARM64. Linux uses static musl binaries that include their C runtime; retained GNU archives remain available separately. The npm package bundles only its small installer dependency tree, rather than native executables for every machine. Supported hosts need no Rust compiler. Fresh installs require GitHub release access as well as the npm registry. Once installed, serving stays offline. Install language servers yourself.

Only a host without a matching prebuilt target attempts a source build. That path needs Cargo/Rust 1.98.0 or newer and native build prerequisites. It verifies the matching source crate, uses locked dependencies and the native Rust target, and builds inside the package. Cargo may fetch locked dependencies. Untested hosts have no automatic-build compatibility promise. Download or verification errors on a supported host fail instead of starting a source build.

For a local npm 12 dependency, install [email protected], run npm approve-scripts mcplsb, then npm rebuild mcplsb --foreground-scripts in the project. Approval normally covers the installed version; approve again after an upgrade if npm blocks the new hook. See npm's approval command. If a global npm 12 hook was skipped, run npm rebuild --global mcplsb --foreground-scripts --allow-scripts=mcplsb. For npm 10/11, enable scripts and omit the permission flag. Scripts-disabled installs and other package managers need manual setup. Existing 0.2.x packages retain their original bundled behavior.

To place a verified preferred-host release binary manually, run node bin/install.cjs --binary PATH_TO_BINARY from the installed mcplsb package directory; use mcplsb.exe on Windows. The helper checks the exact version and manifest binary hash. See the full installation guide for package locations and recovery.

Configure your MCP client to run mcplsb with --workspace and your project directory as separate arguments. The server communicates through stdin and stdout; running it directly waits for an MCP client. Use mcplsb --help to see the command-line options.

mcplsb runs locally for one workspace and exposes seven read-only tools. Your assistant keeps using its usual file tools to make changes; mcplsb synchronizes those changes before answering a new query.

See getting started, configuration, and platform compatibility.