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, desktop Linux, Android, and iOS. All platforms can share clipboard content with each other over your local network — copy on a Mac, paste on a phone, 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. The Android app supports Android 8.0 and later; the iOS app supports iOS 16 and later.

Linux requires a graphical desktop session. The clipboard backend connects to an X11 display (Wayland desktops are supported via XWayland). Headless and server Linux installs are not supported — without a display server there is no clipboard to sync, and ClipMesh exits on startup with a message to that effect. If you're running a desktop Linux distribution with a standard X11 or Wayland session, it works.

Yes, the ClipMesh mobile apps are free on the Google Play Store and Apple App Store. No license, account, or sign-in is required. The mobile apps pair with your existing desktop installation (or with each other) using the same shared encryption secret. If you have already purchased a desktop license, the mobile apps require no additional purchase.

On the desktop, run clipmesh setup to display a QR code containing your cluster's shared secret. (The secret itself is derived automatically from your license — you don't generate or pick it.) In the ClipMesh mobile app, tap "Scan QR" during onboarding (or in Settings) and point the camera at the QR code. The phone imports the secret and immediately begins sending and receiving on the local network. You can also enter the base64 secret manually if you prefer not to use the camera.

To pair an additional phone, you can either scan the desktop QR again, or display the QR from an already-paired phone (Settings → Show Secret / QR Code) and scan that from the new phone.

This is expected. iOS aggressively suspends apps that are not in the foreground, and Apple does not grant background networking entitlements for general LAN UDP listeners. ClipMesh on iOS therefore syncs only while the app is open and on screen. To copy something on a Mac and paste it on the iPhone, open the ClipMesh app on the iPhone, then perform the copy on the Mac — the content will appear in ClipMesh and you can then paste it into your destination app.

The Android app does not have this restriction and can run while other apps are in the foreground.

Confirm the phone and the desktop are on the same Wi-Fi network and the same subnet (some routers separate "guest" networks or 2.4 GHz / 5 GHz bands into different subnets — UDP broadcast does not cross subnet boundaries). Some routers also have an "AP isolation" or "client isolation" setting that blocks devices on the same Wi-Fi from talking to each other; disable it if it's enabled.

On iOS, make sure ClipMesh has been granted the Local Network permission (Settings → ClipMesh → Local Network). On Android, the camera permission is only needed for QR pairing — the app does not need any other permission to sync once paired.

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.

ClipMesh derives the cluster's shared encryption secret automatically from your installed license. Any desktop with the same license file installed will join the same cluster — no manual key exchange between desktops needed. Just install the license on each machine with clipmesh install-license /path/to/your.key, restart ClipMesh, and the desktops will automatically see each other on the local network.

For mobile devices (Android, iOS) — which don't use a license — run clipmesh setup on any of your desktops. This opens a local web page showing a QR code; scan it from the ClipMesh mobile app to pair. You can also display the QR from an already-paired phone (Settings → Show Secret / QR Code) and scan it from another phone.

If you want to run multiple separate clusters from the same license — for example, a "home" cluster and a "work" cluster on the same laptop's two profiles — set a security.cluster_label value in ~/.clipmesh/config.json on each desktop you want grouped together. Desktops sharing a license and a cluster label join the same cluster; differing labels derive different secrets.

All clipboard transfers are encrypted with AES-256-GCM. The cluster's shared secret is a 32-byte key derived from your license email via HKDF-SHA256 with a ClipMesh-specific domain-separation tag, optionally salted with a cluster_label from your config. The derivation is deterministic: two desktops with the same license — and the same cluster label, if set — produce identical secrets without exchanging anything over the network.

The secret never leaves your devices. ClipMesh does not transmit it to Miller-Lange LLC or any third party. Only devices in your cluster can decrypt your clipboard payloads.

If you want to rotate the secret without replacing your license, change (or add) the security.cluster_label in ~/.clipmesh/config.json (or %APPDATA%\.clipmesh\config.json on Windows). All desktops sharing the new label will derive a fresh secret together. Mobile devices need to re-scan the QR code from a desktop to pick up the new secret.

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 all desktops in the cluster are running with the same installed license and the same security.cluster_label (or no label on any of them). Run clipmesh show-secret on each desktop to see the derived secret — if the secrets don't match, the licenses or cluster labels differ. For mobile devices, the secret comes from the QR code you last scanned; re-scan from a desktop in the right cluster to re-pair.
• 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.