Stream Deck alternatives
for Microsoft Teams.
Microsoft retired the interface the official Teams plugin used, so the plugin is gone. Five things people reach for instead, what each one is genuinely good at, and where it runs out of road.
Before comparing tools, it helps to be precise about the job. Controlling a Teams meeting from outside Teams needs three things, and most options deliver one or two:
- Reach. The button works while you're in another app. That's the whole point, and it's where Teams' own shortcuts stop.
- The right kind of mute. Muting the microphone at the OS level silences you, but Teams still shows you as unmuted to everyone else. Toggling Teams' own mute keeps both in agreement.
- State you can see. A button that can't read the meeting is a button you have to double-check, which is how you end up talking into a muted mic anyway.
Teams keyboard shortcuts
Ctrl+Shift+M on Windows, Cmd+Shift+M on Mac, plus
Ctrl+Space / Option+Space for push-to-talk. Nothing to install,
nothing to configure, and they toggle Teams' real mute, so your tile matches reality.
Where it stops: they're in-app shortcuts. Click into your browser or your notes and the keystroke goes there instead. That's the single most common reason people think their mute shortcut is broken. If you spend meetings inside the Teams window, this is genuinely all you need. More in why the Teams mute shortcut stops working.
The system mic toggle
Win+Alt+K toggles the microphone for apps wired into the taskbar call
indicator, Teams included on most setups. It does work from other apps, it's free, and it's
one keystroke.
Where it stops: Windows 11 only, and it's a microphone toggle rather than a meeting toggle, so what your colleagues see on your tile can disagree with what your mic is doing. Details in global mute keys for Windows and muting Teams from any app.
AutoHotkey and friends
On Windows, AutoHotkey binds a global hotkey and sends keystrokes. On macOS, Keyboard Maestro and Hammerspoon fill the same role. If you like owning your tooling, this is satisfying work: free, scriptable, and it can do far more than mute.
Where it stops: the keystroke it sends is still Teams' in-app shortcut, so the script has to bring the Teams window to the front first. That works, and it also drags you out of your slides or your editor every time you mute. Scripts also can't read the meeting, so nothing can light up to tell you your current state, and if you mute from inside Teams the script has no idea.
Worth it if you already write scripts and mostly need one key. Frustrating if you wanted the old plugin's lit-up button back.
Power Automate and Companion
Power Automate is excellent at workflows: post this message, file that record, notify a channel. Its Teams building blocks work at the service level, not on the meeting running on your desk, so there's no "mute me" to call. Power Automate Desktop can send keystrokes, which puts you back in the scripting story above.
Bitfocus Companion is a great control surface, and if you already run it for streaming gear you'd rather not add another one. Companion drives things that expose a control interface, though, and the one Teams offered is the one Microsoft removed. That's the same wall the official plugin hit.
If Companion is your control surface of choice, you can keep it: MuteDeck exposes an HTTP API, so a Companion button can call MuteDeck and MuteDeck deals with Teams.
MuteDeck
This is our tool, so read this section with that in mind. MuteDeck runs on your machine, follows what your meeting is doing, and hands that to a Stream Deck key, a global hotkey, or your phone. It toggles Teams' own mute rather than your microphone, and the key shows the live state, red for muted, including when you mute from inside Teams.
It also isn't Teams-specific: the same keys work in Zoom, Meet, Webex, Discord, Slack huddles and more, which is the part scripts tend to struggle with once your week involves three different meeting apps.
Where it stops: it's a paid app, one purchase per computer. It has to be running to do its job. And because it reads the Teams interface, Teams needs to run in a language it supports, which the setup article lists.
The short version
| Feature | Shortcuts | Win+Alt+K | Scripts | MuteDeck |
|---|---|---|---|---|
| Works from another app |
No.
|
Yes.
|
Partly.
Steals focus first
|
Yes.
|
| Toggles Teams' own mute |
Yes.
|
No.
Mic only
|
Yes.
|
Yes.
|
| Shows live mute state |
No.
|
No.
|
No.
|
Yes.
|
| Works on macOS |
Yes.
|
No.
|
Partly.
Different tooling
|
Yes.
|
| Same keys in other meeting apps |
No.
|
Partly.
|
Partly.
One script per app
|
Yes.
|
| Setup effort |
Yes.
None
|
Yes.
None
|
Partly.
You maintain it
|
Yes.
App plus plugin
|
Physical mute buttons are a category of their own, and worth a look if you want dedicated hardware rather than keys on a deck you already own.
Put the keys back on your deck.
Seven days free, no account and no card. If a script already does the job for you, keep the script: this is only worth paying for if you want the state on the key.
What is the best alternative to the Teams Stream Deck plugin?
For most people, something that toggles Teams' own mute from outside Teams. Scripting tools can press keys for you, but they can't read your meeting state, so the key never tells you whether you're muted. MuteDeck is built for this specific job, which is why we think it's the closest replacement, but the honest comparison is on this page.
Can AutoHotkey mute Microsoft Teams?
It can press the shortcut for you, but the shortcut still needs Teams focused, so most scripts activate the Teams window first. That works, at the cost of yanking you out of whatever you were doing. AutoHotkey also can't see your mute state, so it can't light up a key.
Can Power Automate control a Teams meeting?
Power Automate is built for workflows: messages, approvals, records. It isn't designed to reach into the meeting running on your desk and mute you. Power Automate Desktop can send keystrokes, which lands you in the same place as a script.
I already use Bitfocus Companion. Can it do this?
Companion drives things that expose a control interface. Microsoft removed the one Teams offered, which is the same wall the official plugin hit. If you want to keep Companion as your control surface, MuteDeck has an HTTP API you can point a Companion button at.
Do I need a Teams API token for any of this?
No. That system existed once and Microsoft removed it. Here's what changed.
How much does MuteDeck cost?
A one-time purchase per computer, with a 7-day trial that needs no account and no card. Current pricing is on the pricing page.
What actually replaces the Teams Stream Deck plugin
Hotkeys, scripts, automation platforms, and MuteDeck compared for controlling Teams meetings.