# MeshCommander: managing Intel AMT machines from a browser > MeshCommander is Intel's AMT remote management console, built as a set of HTML and JavaScript files small enough to be uploaded into an AMT device's own flash and served by the device, with remote desktop, Serial over LAN and IDER redirection. The project now carries a notice that Intel has discontinued support for it and asks users to contact Intel support for alternatives. **Ylianst/MeshCommander** — MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve. - Repository: https://github.com/Ylianst/MeshCommander - Stars: 688 · Forks: 121 - Language: HTML - License: Apache-2.0 - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/ylianst-meshcommander ## A management console that fits in 64 kilobytes MeshCommander is an Intel Active Management Technology remote management tool, and the feature list is the starting point: a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and more. What makes it unusual is the delivery model. MeshCommander is built on web technologies and runs on many platforms, so it can be a stand-alone tool, a browser application, or something served directly by the managed device itself. The README states that it was built to be very space efficient so that it can be uploaded into Intel AMT flash space to have it served directly from the Intel AMT web server. That constraint, the 64k limit on Intel AMT file storage, explains almost every design decision in the project. It is why the code is plain HTML, CSS and JavaScript with no build-time framework, why the localisation lives in separate language files rather than in a bundler, and why there is a compilation step at all. For Intel AMT 11.6 and higher, you can load MeshCommander directly into the AMT storage flash space, and depending on the activation mode it can replace the default Intel AMT web page on HTTP/16992 or HTTPS/16993, making the built-in web site much more capable. The project is Apache 2.0 licensed and the author in the package manifest is Intel Corporation. The repository is not archived, and the last push was on 2026-07-28. There are no GitHub releases. The context for all of this is the notice at the top of the README, which says in plain words that Intel has discontinued support for this tool and asks you to contact Intel support for alternatives. That is the first thing a reader should know. ## Three ways to install it, from npm to AMT flash There are three installation paths documented, and they suit different situations. On Windows, the simplest route is the MSI installer downloaded from the MeshCommander site. On Windows, Linux and MacOS, it installs from the Node Package Manager, and the README gives the sequence: ``` mkdir meshcommander cd meshcommander npm install meshcommander node node_modules\meshcommander ``` That starts a small web server on port 3000, reachable at http://127.0.0.1:3000 from a browser. The third path is the firmware installation described earlier, where MeshCommander is loaded into the AMT device's own flash for Intel AMT 11.6 and higher, either through the firmware installer on Windows or through MeshCMD on other platforms. MeshCMD is worth separating out, because it is a tool in its own right rather than an installer. On Windows and Linux you can download it, and it is a command line tool for performing many Intel AMT management operations, with MeshCommander included in it: ``` meshcmd meshcommander ``` Like the npm version, this starts an HTTP web server on port 3000 that you access from any browser at http://127.0.0.1:3000. So all three routes end in the same place: a local web server on port 3000 serving a browser interface. The difference is who hosts it and where the files live, which matters when the target machine has no operating system you can install anything on. ## The compilation step and the WebSite Compiler MeshCommander is a set of HTML web pages that can be used in many different ways: run it in a browser or in nw.js, run it as a stand-alone application, or serve it from Intel AMT. Because of the different roles it can take and the unique requirement of fitting within the 64k limit of Intel AMT file storage, the project has to be compiled with the WebSite Compiler tool, which currently only runs on Windows. What the compiler does is described in one sentence: it merges all of the html, css and js files into a single big file, runs a pre-processor to remove portions that are not needed, and then minifies and compresses the output as needed. That single-file output is what gets uploaded into the AMT device. The constraint that a managed device with no OS, limited flash and no installable package manager can serve a useful management console is unusual enough that the whole toolchain is shaped around it, and the Windows-only requirement for the compiler is the direct consequence. The repository root shows the shape of the source. There is a VSSolution.sln, which points to a Visual Studio solution, and the JavaScript files are named by subsystem and version, amt-wsman-0.2.0.js for the WS-Management layer, amt-desktop-0.2.0.js and agent-desktop-0.0.2.js for the remote desktop, amt-terminal-0.0.2.js for the terminal, amt-redir-node-0.1.0.js, amt-redir-ws-0.1.0.js and agent-redir-rtc-0.1.0.js for redirection, amt-lms-0.1.0.js, amt-scanner-0.1.0.js, amt-ider-node-0.0.1.js and its server and websocket companions, amt-script-0.2.0.js, amt-setupbin-0.1.0.js, amt-certificates-0.0.1.js, and a meshcentral-server-0.2.0.js. There are also per-language copies of the main file, amt-0.2.0.js alongside amt-0.2.0_de.js and the same for es, fr, it, ja, ko, nl, pt, ru and zh-chs, each paired with an index page in the same language, and a closure-externs/ directory. A fork/ directory and images-commander/ round out the tree. The version suffixes on each file are the versioning of the tool itself in practice. The package manifest carries version 0.9.6, and the individual modules carry their own versions, which means a module can be updated independently of the whole. ## What the package manifest reveals about the build The package.json is short and tells you how the pieces fit together. The package is named MeshCommander with the description Intel(R) Active Management Technology console tool, the main entry point is index-nw.html, and the author is Intel Corporation. The keywords are Intel, Intel AMT, Active Management Technology, Remote Management, Hardware Management and Manageability Commander. The window block describes the nw.js stand-alone mode: an icon of favicon.png, no toolbar, a frame, a width and minimum width of 970, and a height and minimum height of 640 and 760 respectively. single-instance is false, which for a tool that manages many devices is the sensible default, since you would expect to open a second console for a second set of machines rather than have the application refuse to start. The dependencies are three, and all three are build-time rather than runtime: html-minifier at version 4, jsdom at 16.4 and minify-js at 0.0.4. That is the npm side of the compilation step described in the README, and the fact that the runtime list is empty tells you the shipped artefact is the static files, not a Node program. The Node install path exists to run the server and to produce the compressed bundle, and the WebSite Compiler is the tool for the firmware path. So there are two build tools for one output, and they are not interchangeable. The npm path is what a developer uses to get a console running locally, and the Windows-only WebSite Compiler is what produces the file you can load into an AMT device. ## Where MeshCommander stops being the right answer The first limitation is the one the README leads with. Intel has discontinued support for the tool, and the project asks you to contact Intel support for alternatives. Nothing in the repository contradicts that, and a tool for managing a hardware platform whose vendor has stepped away is a dependency on a moving target: the AMT firmware will change, the API surface will change, and nobody is obliged to update this code to match. The second limitation is platform. The WebSite Compiler runs only on Windows, which means the firmware installation path, the one that makes MeshCommander distinctive, is not reproducible on a Linux build machine. Teams that standardise on Linux workstations can still run the npm version and MeshCMD, but they cannot produce the flash artefact themselves, so they depend on a Windows machine or on a prebuilt file. The third limitation is that this is a console for one platform's manageability technology. It talks to Intel AMT, through WS-Management and AMT-specific redirection, terminal and desktop mechanisms. There is no equivalent for AMD or Arm-based out-of-band controllers, and the architecture does not generalise to them: MeshCommander is a client for a specific vendor's remote management stack rather than a generic out-of-band management tool. The real alternative, and the project points at it directly, is to contact Intel support for alternatives. The difference in approach is the important part. MeshCommander is a self-hosted console that you compile, host and run yourself, which means you keep control of the interface and can extend it, but you also keep the maintenance of it. A vendor-supported console is the opposite trade: you get compatibility guarantees and a support path, and you give up the ability to change how it works. For an organisation that has AMT hardware in production and a mandate to keep it manageable, the vendor path is the safer one. For a lab, a security researcher, or anyone who wants to understand what the AMT web interface can do, the source here remains the most complete public description available, and reading it is still worth the time even though running it in anger is a different decision. ## Conclusion Read MeshCommander as a well documented reference implementation of the Intel AMT web interface, and use it as a workbench for a lab of AMT-capable machines, since the remote desktop, terminal and redirection pieces are the clearest public description of what the platform offers. Do not adopt it as the basis of a new fleet management product, because the project states that Intel has discontinued support for the tool. Before you use it, check the firmware version of the AMT devices you plan to target, since the flash installation path is documented for Intel AMT 11.6 and higher, and confirm with Intel what the supported alternative is for the devices you actually need to manage. ## FAQ ### What is MeshCommander? It is an Intel Active Management Technology remote management tool, feature rich, with a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal and IDER-Redirection support. It is built on web technologies and runs on many platforms, and it is licensed under Apache 2.0. ### Is MeshCommander still supported by Intel? No. The README states that Intel has discontinued support for this tool and asks you to contact Intel support for alternatives. The repository itself is not archived, with the last push on 2026-07-28, and it has no GitHub releases. ### How do I install MeshCommander without the MSI installer? On Windows, Linux and MacOS it installs from npm: create a directory, change into it, run npm install meshcommander and then node node_modules\meshcommander. That starts a small web server on port 3000, which you open at http://127.0.0.1:3000 in a browser. ### What is the 64k limit that shapes MeshCommander? It is the Intel AMT file storage limit. Because MeshCommander has to fit inside it, it is compiled with the WebSite Compiler, which merges the html, css and js files into one file, strips unneeded portions with a pre-processor, then minifies and compresses the output. For Intel AMT 11.6 and higher that compiled file can be loaded into the device's own flash. ### What is MeshCMD and how does it relate to MeshCommander? MeshCMD is a command line tool for performing many Intel AMT management operations, and MeshCommander is included in it. Starting it with meshcmd meshcommander starts an HTTP web server on port 3000, so you can reach MeshCommander from any browser. ## Sources - [Issues](https://github.com/Ylianst/MeshCommander/issues) - [License: Apache-2.0](https://github.com/Ylianst/MeshCommander/blob/master/LICENSE) - [README](https://github.com/Ylianst/MeshCommander/blob/master/README.md) - [Ylianst/MeshCommander on GitHub](https://github.com/Ylianst/MeshCommander) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ylianst-meshcommander