Skip to main content

MK850, MX Keys, and MX Master 3 Notes

Not all three devices are equal

MX Keys and MX Master 3 fit Logitech's current public Actions Ring and Marketplace story much better than MK850 Performance.

1. MX Master 3​

Best expectations:

  • use Logi Options+,
  • use app-specific profiles,
  • use Smart Actions,
  • use Actions Ring,
  • consume Marketplace plugins,
  • potentially target it as part of your plugin user base.

What not to assume:

  • public haptics support,
  • raw firmware scripting,
  • device-specific low-level API access from Logitech.

2. MX Keys​

Best expectations:

  • use Logi Options+,
  • use app-specific function-key customization,
  • use Smart Actions,
  • use Actions Ring,
  • consume Marketplace plugins.

This makes it a good target for workflow-oriented plugins, especially when the user triggers plugin actions from the current Logitech software experience rather than from raw keyboard firmware.

3. MK850 Performance​

This is the caution device.

I could not verify MK850 in Logitech's current public Logi Actions SDK device guidance or current Options+-centered developer material.

That means you should assume:

  • basic software customization may still exist,
  • current Actions Ring / Marketplace plugin support is not guaranteed,
  • it is a poor first target for a new plugin project.

4. Practical planning advice​

If you want to build one integration for your own desk setup:

  1. Design it around MX Keys and MX Master 3.
  2. Treat MK850 as optional or unsupported.
  3. Use Smart Actions first if the workflow is local.
  4. Build an Actions SDK plugin if the workflow needs external services or distribution.