Displaybuddy MCP

What displaybuddy-mcp MCP server does

displaybuddy-mcp MCP server connects an MCP-compatible AI client to DisplayBuddy on macOS. It provides monitor discovery and control operations without requiring the agent to interact with the DisplayBuddy interface directly. An agent can inspect connected displays, change supported settings, apply saved presets, manage schedules, and check or change multi-display synchronization.

The server is intended for Macs where DisplayBuddy is installed and running. It can support tasks such as identifying available monitors, changing an external display to a different input, dimming multiple screens, or activating a saved viewing setup.

How it works

The MCP process wraps the displaybuddy command-line tool. That CLI communicates with the running DisplayBuddy application through its URL scheme, which then controls the monitors. The request path is local: an AI agent sends an MCP call, the server invokes the CLI, and DisplayBuddy applies the operation to the displays.

The displaybuddy-mcp MCP server does not describe a remote service or cloud API.

Setup and configuration

Before starting the server, use macOS, install DisplayBuddy, and leave the application running. In DisplayBuddy, open Settings, choose General, and install the CLI Tool. Node.js 18 or later is also required.

For clients that launch local MCP servers, configure the server with npx and the package name:

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

The README provides this configuration for Claude Desktop and Cursor. Smithery can install it with npx -y @smithery/cli install displaybuddy-mcp --client claude. No environment variables are documented. Developers can build the project with npm install followed by npm run build, then inspect it with the MCP Inspector and node ./build/index.js.

Tools and capabilities

The displaybuddy-mcp MCP server exposes these operations:

• displaybuddy_status provides a quick overview of all displays and is intended as the initial check.
• displaybuddy_list returns detailed display information, including UUID, type, and capabilities.
• displaybuddy_get reads properties for one display.
• displaybuddy_set changes brightness, contrast, volume, input source, or rotation.
• displaybuddy_preset_list lists saved presets.
• displaybuddy_preset_activate activates a preset and accepts an optional delay.
• displaybuddy_schedule_list lists automation schedules.
• displaybuddy_schedule_toggle enables or disables a schedule.
• displaybuddy_sync checks, enables, or disables synchronization across displays.

Limitations and notes

This server depends on DisplayBuddy rather than controlling monitors independently. DisplayBuddy must be installed and running, and its CLI tool must be available before requests can work. The material does not specify monitor models, operating systems other than macOS, or additional configuration through environment variables. Supported settings may also depend on the capabilities reported for a particular display.