MCP server for controlling Mac monitors via DisplayBuddy — adjust brightness and more.
{
"mcpServers": {
"io-github-biocross-displaybuddy-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for controlling Mac monitors via DisplayBuddy — adjust brightness and more.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 25 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for io.github.biocross/displaybuddy-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"displaybuddy": {
"command": "npx",
"args": ["-y", "displaybuddy-mcp"]
}
}
}
Add to your MCP settings:
{
"mcpServers": {
"displaybuddy": {
"command": "npx",
"args": ["-y", "displaybuddy-mcp"]
}
}
}
npx -y @smithery/cli install displaybuddy-mcp --client claude
| Tool | Description |
|------|-------------|
| 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 |
Once connected, you can ask your AI assistant things like:
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
npm install
npm run build
# Test with MCP Inspector
npx -y @modelcontextprotocol/inspector node ./build/index.js
MIT