Skip to main content

Logi Options+ Developer Guide

What is actually possible

Yes, you can build custom integrations for Logitech's current productivity ecosystem, but the public developer path is not a low-level "program the keyboard or mouse firmware" API. The official path is the Logi Actions SDK, plus no-code automation with Smart Actions and app-specific profiles inside Logi Options+.

Source scope as of July 1, 2026

This guide is based on Logitech's current Logi Options+ product pages, Smart Actions, Marketplace, and the public Logi Actions SDK documentation. The current SDK supports C# and Node.js, packages plugins as .lplug4, and targets Logitech's Logi Plugin Service ecosystem.

1. Short answer​

For your devices, the practical answer is:

DeviceCan you customize it?Can you build for it?Best path
MX KeysYesYes, within the Logi Actions ecosystemSmart Actions, app-specific profiles, Actions Ring, Marketplace plugins
MX Master 3YesYes, within the Logi Actions ecosystemSmart Actions, app-specific profiles, Actions Ring, Marketplace plugins
MK850 PerformanceLikely basic customization onlyNot verified as a Logi Actions SDK targetOlder Logitech Options-era customization, not the current plugin path

The biggest nuance is this:

  • MX devices participate in the current Options+ / Actions Ring / Marketplace story.
  • MK850 is not an MX device, and I could not verify it in Logitech's current Actions SDK supported-device path.

2. What "developing for Logi+" means​

There are three different levels:

LevelWhat you buildBest for
Smart ActionsNo-code or low-code automations inside Options+Quick keyboard/mouse workflows, app launches, text insertion, macros
App-specific customizationPer-app button/key behavior and profilesProductivity tuning without shipping software
Logi Actions SDK pluginReal plugin packaged for Options+ / MarketplaceThird-party integrations, services, custom actions, shared plugins

If your goal is:

  • "When I press a key/button, do a sequence of tasks" -> use Smart Actions.
  • "Give me an integration with my app/service/tool" -> build a Logi Actions SDK plugin.

3. Important platform model​

The public developer model is centered on:

  • Actions Ring
  • MX Creative Console
  • Logi Marketplace
  • Logi Plugin Service

That means plugin actions are part of the Logi Actions ecosystem, not a raw HID or firmware SDK for every Logitech device.

4. What this guide covers​

GoalStart hereWhy
Decide what is supportedArchitecture and Device SupportSeparates Smart Actions, Actions Ring, Marketplace plugins, and device scope
Build without code firstSmart Actions and ProfilesBest for MX Keys and MX Master 3 workflows
Build a real pluginPlugin Development with Actions SDKOfficial SDK path
Use JavaScript / TypeScriptNode.js Plugin GuideFastest route for web or automation developers
Use C# / .NETC# Plugin GuideStrongest route for mature desktop integrations
Check your exact devicesMK850, MX Keys, and MX Master 3 NotesDevice-specific guidance
Publish and distributeMarketplace and Packaging.lplug4, approval, review

5. Primary references​