Displaybuddy MCP vs Mirroir MCP
A side-by-side look at the Displaybuddy MCP and Mirroir MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Displaybuddy MCP for os automation work as a local process; choose Mirroir MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Displaybuddy MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
displaybuddy_status, displaybuddy_list, displaybuddy_get.
Choose Mirroir MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 51/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 256 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Displaybuddy MCP | View Mirroir MCP |
Tools & capabilities
Displaybuddy MCP tools 9
displaybuddy_statusQuick overview of all displays (call this first)displaybuddy_listFull display details including UUID, type, capabilitiesdisplaybuddy_getGet properties of a specific displaydisplaybuddy_setSet brightness, contrast, volume, input, rotationdisplaybuddy_preset_listList saved presetsdisplaybuddy_preset_activateActivate a preset (with optional delay)displaybuddy_schedule_listList automation schedulesdisplaybuddy_schedule_toggleEnable or disable a scheduledisplaybuddy_syncCheck/enable/disable multi-display sync
Mirroir MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Displaybuddy MCP
{
"mcpServers": {
"displaybuddy-mcp": {
"command": "npx",
"args": [
"-y",
"displaybuddy-mcp"
]
}
}
}
Mirroir MCP
{
"mcpServers": {
"mirroir-mcp": {
"command": "npx",
"args": [
"-y",
"mirroir-mcp"
]
}
}
}
Frequently asked questions
Displaybuddy MCP is categorized under OS Automation and uses a local stdio subprocess. Mirroir MCP belongs to OS Automation and uses a local stdio subprocess. Pick Displaybuddy MCP for os automation work and Mirroir MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Displaybuddy MCP has no declared pricing — check the project's own site. Mirroir MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add displaybuddy-mcp and mirroir-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Displaybuddy MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 7 GitHub stars. Mirroir MCP has 51/100 (Good) with 1 views, 0 installs and 256 GitHub stars.