lnwjud MCP

A local agent runtime and MCP gateway with 298 tools: files, Git, processes, Chrome browser, Windows and Office

  • 209 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Tools run commands, edit files and start processes on your computer with user permissions
  • Remote MCP through ngrok or Cloudflare exposes control of the computer at a public HTTPS address protected by OAuth
  • Windows tools read the registry, the event log and Outlook mail, and community installers may be unsigned
All reasons and checks

engasnm111/lnwjud

Install

Manual install

Text for your agent

Download the installer from `https://github.com/engasnm111/lnwjud/releases/latest` (Windows) and verify the SHA-256 checksums, then add the project workspace and choose the MCP connection: local stdio or Desktop loopback. For remote MCP warn the user that a public address gets opened.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Tools run commands, edit files and start processes on your computer with user permissions
  • Remote MCP through ngrok or Cloudflare exposes control of the computer at a public HTTPS address protected by OAuth
  • Windows tools read the registry, the event log and Outlook mail, and community installers may be unsigned

This is third-party code. Review the repository files before installing.

What it does

lnwjud gives an agent 298 tool definitions through one local process and MCP gateway. They include working with the workspace and files, Git, processes and background tasks, checks (tests, lint, types, build), a managed Chrome over CDP with screenshots, backups and recovery, a work log and diagnostics. Windows adds WSL, the registry, Windows Sandbox, the event log, OCR and Outlook. Connections split into a local MCP (stdio or a loopback on the same computer) and a remote MCP through ngrok with OAuth, Cloudflare or your own HTTPS address. Every tool works within the active project, the permission policy and mutation approval, and on an unknown platform it refuses instead of substituting another implementation.

Who it is for. People who want to give an AI client such as Codex or Claude broad, controlled access to their Windows, macOS or Linux computer through a single MCP gateway.

Good fit when

  • An agent needs files, Git, tests and a project build on the local machine in one place
  • A task requires a managed browser: open a page, read the DOM and take a screenshot
  • A session lasts for hours and needs backups, checkpoints and crash recovery
  • An AI client must be connected over a protected HTTPS address to a computer at home

Not a fit when

  • A handful of tools is enough: 298 definitions crowd the list and widen access
  • The computer is shared or corporate and policy forbids remote access and tunnels
  • A signed installer is needed: community Windows artifacts are built unsigned when credentials are missing

Example request

Run the tests and build in the active project folder and show a report of the failing tests.

MCP

Transport
stdio, http
Authentication
OAuth

Limitations

Node.js 24 and the installer from the Releases page (Windows) or a source build are required. The default set advertises 286 tools, and all 298 turn on together with Codex delegation and Agent Swarm. Some capabilities depend on the OS: Windows tools work only on Windows. Community installers may be unsigned, and authenticity is verified with SHA-256 checksums. Texts are mostly in English, with some greetings in Thai. The latest commit in the repository is from November 2026.

How to disable. Uninstall lnwjud the usual way for your OS, then remove the MCP entry from the client configuration and shut down the ngrok or Cloudflare tunnel if one was set up. Project working folders stay.

FAQ

How do I connect lnwjud to a client?

For the local setup use the packaged stdio launcher or the Desktop loopback MCP address. This needs no ngrok, public address or OAuth.

What is the difference between 286 and 298 tools?

The default advertised set is 286. All 298 are available with Codex delegation and Agent Swarm turned on.

Which platforms are supported?

Windows, macOS and Linux, but some tools are tied to the OS: the registry, WSL, Outlook and Windows Sandbox exist only on Windows.

Can I do without ngrok?

Yes. Remote MCP also works through a Cloudflare Tunnel or your own HTTPS address that you manage yourself. The local MCP needs no tunnel.

What limits agent access?

The active project scope, permission policy, mutation approval, recovery and OS permissions. A tool does not bypass them, and an unsupported platform gets a refusal.

Discussion

No questions or reviews yet.

Official

A self-hosted gateway routes internal MCP tools, authenticates users and records requests for later review.

MCP serverBroad access587Repository stars

A secure MCP runtime through which an agent operates local machines, servers and containers

MCP serverBroad access1.3KRepository stars

Console Automation MCP gives an agent local shells and SSH sessions: input, output, error detection, long processes

MCP serverBroad access54Repository stars

An MCP server giving ChatGPT and agents a terminal, files, Playwright and remote machines inside an isolated workspace.

MCP serverBroad access106Repository stars

A local stdio MCP server for self-hosted Jira, Confluence, Bitbucket Server and Jenkins, with mTLS support and write tools disabled by default

MCP serverExtended access1Repository stars

Your machine's terminal, windows and desktop in a browser, plus an MCP server for agents to read and type into other sessions

MCP serverBroad access304Repository stars

README in short

The README lists the tool areas, MCP connection choices (local, ngrok, Cloudflare, custom URL, OpenAI tunnel), downloads for three OSes and the security boundary. A bundled set of Ponytail developer documents and documentation links are described separately.

README badge

Report a problem