Miller-Lange LLC

Download the installer for your platform from the portal dashboard, run it, and enter your license key when prompted. See the getting started guide for detailed per-platform instructions.

ML-EPM collects CPU utilization, memory usage, disk usage, and WiFi signal strength at 5-minute intervals. No personal files, browsing history, or keystrokes are ever collected. See our privacy policy for full details.

Add the ML-EPM MCP server configuration to your Claude Desktop settings file with your MCP API key (available on the portal dashboard). The documentation has the exact JSON configuration and file locations for each platform.

ML-EPM supports macOS (Intel and Apple Silicon, macOS 13+), Windows 10/11, and Linux (amd64, arm64, and arm32). All platforms report the same telemetry and work with the same account and license key.

Yes. Sign in to the billing page to manage your subscription through Stripe. You can upgrade, downgrade, or cancel at any time. If you cancel, your agents continue collecting data for a 7-day grace period.

WiFi SSID detection requires Location Services to be enabled on macOS and Windows. On Linux, the agent tries multiple methods (nmcli, iw, /proc/net/wireless) in order. WiFi signal strength (RSSI) may work even without SSID access on some platforms.

Commute Coach is currently in development. Contact us to be notified when it launches.

ClipMesh runs on macOS, Windows 10/11, and Linux. All three platforms can share clipboard content with each other — copy on macOS, paste on Windows, and vice versa. The macOS build is a universal binary (Apple Silicon and Intel). The Linux build is a single statically-linked binary with no external dependencies.

Download the installer for your platform from the download page (requires a valid license key).

• macOS: Open the .pkg installer. ClipMesh installs to /usr/local/bin/ and sets up a LaunchAgent so it starts automatically at login.
• Windows: Run ClipMesh-Setup.exe. It installs to %PROGRAMFILES%\ClipMesh\, adds a Windows Firewall rule for UDP port 9876, and registers an autostart entry. No admin account is needed for day-to-day use — only during install for the firewall rule.
• Linux: Run sudo sh ClipMesh-<version>.run. It installs to /usr/local/bin/ and sets up a systemd user service.

On the first device, run clipmesh setup. This opens a local web page showing your shared encryption key as text and a QR code. The key is also saved to ~/.clipmesh/SETUP_KEY.txt (or %APPDATA%\.clipmesh\SETUP_KEY.txt on Windows).

On each additional device, install ClipMesh and run:

clipmesh import-secret <your-shared-key>

To share the key over the local network without manually copying it, run clipmesh setup --lan on the first device. This generates a one-time PIN-protected URL that other devices on the same network can open to import the key automatically.

All clipboard transfers are encrypted with AES-256-GCM. The shared secret is a 32-byte random key (displayed as base64) that you configure on each device. The secret never leaves your network — ClipMesh does not transmit it to any server. Only devices that share the same secret can decrypt each other's clipboard data.

To generate a new secret at any time, run clipmesh --generate-secret --save and then re-import it on your other devices.

No. ClipMesh is entirely LAN-based. Clipboard data travels directly between devices over your local network using UDP broadcast on port 9876. Nothing is routed through external servers, and no internet connection is required for clipboard sync to work. The only time ClipMesh contacts the internet is during the initial license verification at install time.

ClipMesh is sold as a perpetual license — pay once and use it on all your machines, forever. There are no subscriptions or recurring fees. The license is tied to your purchase email and delivered as a .key file. Install it with:

clipmesh install-license /path/to/your.key

Licenses can be floating (valid on any machine) or machine-bound. See the purchase page for pricing and options.

Work through these in order:

• Confirm all devices are on the same local network (same subnet). ClipMesh uses UDP broadcast, which does not cross subnet boundaries.
• Verify the shared secret is identical on all devices — even a single character difference will prevent decryption. Run clipmesh show-secret on each device to compare.
• Check that the ClipMesh service is running: on macOS, launchctl list | grep clipmesh; on Linux, systemctl --user status clipmesh.service; on Windows, Get-Process -Name clipmesh.
• If you're on a managed Wi-Fi network with client isolation enabled, UDP broadcast between devices will be blocked. Try connecting devices to the same wired switch, or check with your network administrator about enabling intra-VLAN broadcast.
• On Linux, if you use ufw, make sure UDP port 9876 is allowed: sudo ufw allow 9876/udp.
• On Windows, confirm the Windows Firewall inbound rule for UDP 9876 is present. The installer creates it automatically, but security software may have removed it.

• macOS: tail -f /tmp/clipmesh.out.log or tail -f /tmp/clipmesh.err.log
• Linux: journalctl --user -u clipmesh.service -f
• Windows: Add a logging.file path to %APPDATA%\.clipmesh\config.json to enable file logging.

Run clipmesh uninstall from any terminal. This stops the service and removes the autostart entry. Your configuration and encryption keys are preserved in ~/.clipmesh.

To remove everything including your keys and config: clipmesh uninstall --purge

On Windows you can also use Add/Remove Programs.