Displaybuddy MCP Server

MCP server for controlling Mac monitors via DisplayBuddy — adjust brightness and more.

Local serverstdio

What is the Displaybuddy MCP server?

If you already use Displaybuddy, the displaybuddy mcp server is the piece that lets your assistant work with it directly. MCP server for controlling Mac monitors via DisplayBuddy — adjust brightness and more.

What the server does

Works with Claude Desktop, Cursor, Windsurf, Cline, and any MCP-compatible client.

Installation

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • displaybuddy_status — Quick overview of all displays (call this first)
  • displaybuddy_list — Full display details including UUID, type, capabilities
  • displaybuddy_get — Get properties of a specific display
  • displaybuddy_set — Set brightness, contrast, volume, input, rotation
  • displaybuddy_preset_list — List saved presets
  • displaybuddy_preset_activate — Activate a preset (with optional delay)
  • displaybuddy_schedule_list — List automation schedules
  • displaybuddy_schedule_toggle — Enable or disable a schedule
  • displaybuddy_sync — Check/enable/disable multi-display sync
  • Cursor — The Cursor tool exposed by this server
  • Smithery — The Smithery tool exposed by this server

Credentials and setup notes

  1. macOS with DisplayBuddy installed and running 2. DisplayBuddy CLI installed: open DisplayBuddy > Settings > General > Install CLI Tool 3. Node.js 18+

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Displaybuddy.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Displaybuddy's toolset — displaybuddy_status, displaybuddy_list, displaybuddy_get and 8 more — is a fair guide to whether it matches your workflow. It is maintained by biocross; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
displaybuddy_statusQuick overview of all displays (call this first)
displaybuddy_listFull display details including UUID, type, capabilities
displaybuddy_getGet properties of a specific display
displaybuddy_setSet brightness, contrast, volume, input, rotation
displaybuddy_preset_listList saved presets
displaybuddy_preset_activateActivate a preset (with optional delay)
displaybuddy_schedule_listList automation schedules
displaybuddy_schedule_toggleEnable or disable a schedule
displaybuddy_syncCheck/enable/disable multi-display sync
CursorThe Cursor tool exposed by this server.
SmitheryThe Smithery tool exposed by this server.

How to install the Displaybuddy MCP server

{
  "mcpServers": {
    "displaybuddy": {
      "command": "npx",
      "args": ["-y", "displaybuddy-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  1. macOS with DisplayBuddy installed and running 2. DisplayBuddy CLI installed: open DisplayBuddy > Settings > General > Install CLI Tool 3. Node.js 18+

Example prompts to try

  • Use Displaybuddy to displaybuddy status.
  • Use Displaybuddy to displaybuddy list.
  • Use Displaybuddy to displaybuddy get.

Frequently asked questions

It connects Displaybuddy to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (displaybuddy_status, displaybuddy_list, displaybuddy_get, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Displaybuddy directly.