Back to Directory/Developer Tools

io.github.biocross/displaybuddy-mcp

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

Developer ToolsJavaScriptv1.0.0

DisplayBuddy MCP Server

An MCP (Model Context Protocol) server that lets AI agents control Mac monitors via DisplayBuddy — adjust brightness, contrast, volume, input source, apply presets, sync displays, and more.

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

Prerequisites

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

Installation

Claude Desktop

Add to your claude_desktop_config.json:

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

Cursor

Add to your MCP settings:

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

Smithery

npx -y @smithery/cli install displaybuddy-mcp --client claude

Available Tools

ToolDescription
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

Example Prompts

Once connected, you can ask your AI assistant things like:

  • "Dim all my monitors to 30%"
  • "What displays are connected?"
  • "Switch my Dell monitor to HDMI"
  • "Activate my Night Mode preset"
  • "Sync all displays to my main monitor"
  • "Turn up the brightness on my external display"
  • "Set up my coding environment — brightness 70, contrast 60"

How It Works

The MCP server wraps the displaybuddy CLI, which communicates with the running DisplayBuddy app via URL scheme. All operations are local — no data leaves your machine.

AI Agent → MCP Server → displaybuddy CLI → DisplayBuddy App → Your Monitors

Development

npm install
npm run build

# Test with MCP Inspector
npx -y @modelcontextprotocol/inspector node ./build/index.js

License

MIT

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @biocross/displaybuddy-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-biocross-displaybuddy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@biocross/displaybuddy-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@biocross/displaybuddy-mcpnpm

Compatible MCP Clients

io.github.biocross/displaybuddy-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More