On a surface level, the MX Keypad is a very simple device. Nine LCD buttons, accompanied by two additional buttons used to flip between pages—that is it. The value comes from the software integration, which is realized through Logitech Options+. Anyone familiar with other current Logitech MX devices will likely have some experience with Options+ already, which is capable but also rather resource-hungry, occupying upwards of 100 MB even when only the bare minimum of necessary background processes are running. Through Options+, one can assign actions to each LCD button, grouped across pages and profiles. Fundamentally, Options+ is structured around applications installed on one's system, in that the plugins which allow one to access the functions of an application require said applications to be installed. For instance, if, for whatever reason, one would want to interact with the VS Code web client for GitHub through the MX Keypad, this isn't possible, as the VS Code plugin only works with the VS Code desktop application. The upside of this is that Options+ is capable of context switches, such that application-specific functions are automatically switched whenever the application in question is active. As a result, when switching between VS Code and Claude Desktop, the MX Keypad will swap its functions accordingly.

These plugins are what elevate the MX Keypad above a mere button panel. Basically, anything the application for which a plugin exists can do, the MX Keypad can also do, and if the application in question is an AI agent, the possibilities multiply exponentially. For instance, if I want to know the weather, I can set up a prompt through Codex, and have GPT tell me about the weather. Merely through simple prompting, the MX Keypad is capable of anything the AI agent of my choice is capable of. Even though not strictly required, deep AI integration is what takes the MX Keypad to the next level, which is underlined by the fact that Logitech bundles a three-month GitHub Copilot Pro+ subscription with the MX Keypad. While somebody who hasn't really incorporated AI into their workflow will still get some mileage out of the MX Keypad, AI integration is what the MX Keypad is ultimately all about. That having been said, through suitable plugins the MX Keypad can also interact with hardware, such as displaying hardware monitors on its LCD buttons. Starting a benchmark session through NVIDIA's Project G-Assist at the press of a button? With a bit of tinkering, pretty much anything is possible.

This experimental spirit is further reflected in the Logi marketplace, through which plugins are distributed. Logitech provides the SDK for plugins, which is why a steady supply of new plugins can be expected, and one is in fact encouraged to try one's hand at writing new plugins. At the time of writing, however, the marketplace is still rather barebones: one cannot sort plugins by most popular, there is no tag system, no rating system, and directly giving feedback or reporting bugs to the developer of a plugin isn't possible, either. Yet arguably the most significant omission is the fact that Options+—and, by extension, the Logi marketplace—lacks Linux support, which is odd to say the least given the focus on developing. In time, this platform will hopefully mature further.

There are also a few minor issues with the physical design of the MX Keypad. The nine LCD buttons are rather large, which is why their actuation point not being entirely even is expected. When pressed at the edges, actuation is rather light, yet when pressed at the center, the required actuation force is significantly greater. The MX Keypad comes with a rubber-base stand which mounts the MX Keypad at a roughly 45° angle, but when pressing the right or left edge rows of buttons centrally, moving the stand and the MX Keypad along with it can happen regardless. Another issue is that the button edges are beveled, which is appreciated from an ergonomic and aesthetic point of view, yet introduces reflections from whatever is displayed on the LCD. Lastly, the pages through which one can flip with the two additional buttons at the bottom don't loop, so when I want to go from page 15 to page 1, I have to manually flip back through pages 14 to 2 first.

If anything, my main issue with the MX Keypad isn't with what it is, but rather with what it isn't. Pretty much all the complaints I have about the physical part of the MX Keypad would be completely resolved if the MX Keypad were to use a touchpad: I would not be restricted to nine physical buttons, I could easily swipe through pages, re-arrange icons right on the pad, and not be bothered by actuation points or reflections. As such, I sincerely hope that Logitech will eventually release a touchpad version of the MX Keypad.

Obviously, there is an argument to be made that with enough effort, anything the MX Keypad can do can also be realized through desktop and application UIs, macros, or self-developed solutions. Yet what the MX Keypad offers is convenience, along with a fairly high level of execution. Not everybody will find use in what the MX Keypad brings to the table, but those already using other MX devices in general and for developing and AI workflows in particular may appreciate the wealth of functions provided by the MX Keypad. For $99.99, the MX Keypad is certainly "pushing it" compared to similar products, though at the same time, the MX Keypad is, in a manner of speaking, the more professional product. With that in mind, the MX Keypad gets our Recommended award along with our Expensive badge.