{
  "markdown": "# DDC/CI Control Bridge\n\n![DDC/CI Control Bridge](docs/banner.png)\n\n[![NPM Version](https://img.shields.io/npm/v/ddc-ci-control-bridge?color=red)](https://www.npmjs.com/package/ddc-ci-control-bridge) [![MIT licensed](https://img.shields.io/github/license/Defozo/ddc-ci-control-bridge)](./LICENSE) [![GitHub Release](https://img.shields.io/github/v/release/Defozo/ddc-ci-control-bridge)](https://github.com/Defozo/ddc-ci-control-bridge/releases)\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=ddc-ci-bridge&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRkYy1jaS1jb250cm9sLWJyaWRnZSJdfQ%3D%3D) [<img alt=\"Install in VS Code\" src=\"https://img.shields.io/badge/Install%20in%20VS%20Code-0098FF?style=for-the-badge&logo=visualstudiocode&logoColor=white\">](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%7B%22name%22%3A%22ddc-ci-bridge%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22ddc-ci-control-bridge%22%5D%7D)\n\nMulti-protocol server for DDC/CI monitor control with MCP and MQTT support.\n\n## Features\n\n- **DDC/CI Monitor Control**: Read and write VCP codes to control monitor brightness, contrast, input source, and more\n- **Model Context Protocol (MCP)**: Server with resources and tools for AI/agent integration\n- **MQTT Client**: Connect to any MQTT broker for IoT/automation platforms\n  - Home Assistant auto-discovery support\n  - Generic MQTT pub/sub for custom integrations\n- **Cross-Platform**: Works on Windows, Linux, and macOS\n- **Dual Distribution**: Available as standalone executable or npm package\n\n## Quick Start\n\n### Installation\n\n**Option 1: NPM Package (Global)**\n```bash\nnpm install -g ddc-ci-control-bridge\nddc-ci-bridge\n```\n\n**Option 2: NPX (No Install)**\n```bash\nnpx ddc-ci-control-bridge\n```\n\n**Option 3: Standalone Executable**\n\nDownload the binary for your platform from [GitHub Releases](https://github.com/Defozo/ddc-ci-control-bridge/releases):\n\n- **Windows**: `ddc-ci-bridge-win.exe`\n- **Linux**: `ddc-ci-bridge-linux`\n- **macOS**: `ddc-ci-bridge-macos`\n\n**⚠️ Note:** The executable requires `DDC_API_KEY` environment variable to be set, or it will exit immediately.\n\n**Windows:**\n```cmd\n# Set API key (required)\nset DDC_API_KEY=your-secret-key\n\n# Run the executable\nddc-ci-bridge-win.exe\n\n# Or set multiple environment variables\nset DDC_API_KEY=your-secret-key\nset MQTT_ENABLED=true\nset MQTT_HOST=192.168.1.100\nddc-ci-bridge-win.exe\n```\n\n**Linux/macOS:**\n```bash\n# Make executable (first time only)\nchmod +x ddc-ci-bridge-linux  # or ddc-ci-bridge-macos\n\n# Run with API key (required)\nDDC_API_KEY=your-secret-key ./ddc-ci-bridge-linux\n\n# Or with multiple environment variables\nDDC_API_KEY=your-secret-key MQTT_ENABLED=true MQTT_HOST=192.168.1.100 ./ddc-ci-bridge-linux\n```\n\n**Using with MCP Clients:**\n\nConfigure your MCP client to use the executable path:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"C:\\\\path\\\\to\\\\ddc-ci-bridge-win.exe\",\n      \"args\": [],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n### MCP Client Setup\n\nChoose between **Local (stdio)** or **Remote (HTTP)** setup depending on your needs:\n\n- **Local Setup**: Run MCP server on the same machine as your monitors (recommended for most users)\n- **Remote Setup**: Run MCP server on a monitor-connected machine, access from other devices\n\n---\n\n#### 🖥️ Local Setup (stdio - Same Machine)\n\nUse this if your MCP client is on the same machine as your monitors.\n\n<details>\n<summary><b>Install in Cursor (Local)</b></summary>\n\nGo to: `Settings` → `Cursor Settings` → `MCP` → `Add new global MCP server`\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=ddc-ci-bridge&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRkYy1jaS1jb250cm9sLWJyaWRnZSJdfQ%3D%3D)\n\nOr paste the following configuration into your `~/.cursor/mcp.json` file:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\",\n        \"MQTT_HOST\": \"localhost\",\n        \"MQTT_PORT\": \"1883\"\n      }\n    }\n  }\n}\n```\n\n**Optional MQTT**: Set `MQTT_ENABLED=true` and configure `MQTT_HOST` to your MQTT broker IP for automation platform integration.\n\n</details>\n\n<details>\n<summary><b>Install in VS Code (Local)</b></summary>\n\n[<img alt=\"Install in VS Code\" src=\"https://img.shields.io/badge/VS_Code-Install%20DDC/CI%20Bridge-0098FF?style=flat-square\">](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%7B%22name%22%3A%22ddc-ci-bridge%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22ddc-ci-control-bridge%22%5D%7D)\n\nAdd this to your VS Code MCP config file:\n\n```json\n\"mcp\": {\n  \"servers\": {\n    \"ddc-ci-bridge\": {\n      \"type\": \"stdio\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Claude Desktop (Local)</b></summary>\n\nOpen Claude Desktop developer settings and edit your `claude_desktop_config.json` file:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Claude Code (Local)</b></summary>\n\nRun this command:\n\n```sh\nclaude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge\n```\n\n</details>\n\n<details>\n<summary><b>Install in Windsurf (Local)</b></summary>\n\nAdd this to your Windsurf MCP config file:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Cline (Local)</b></summary>\n\nAdd this to your Cline MCP configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Zed (Local)</b></summary>\n\nAdd this to your Zed `settings.json`:\n\n```json\n{\n  \"context_servers\": {\n    \"DDC/CI Bridge\": {\n      \"source\": \"custom\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Roo Code (Local)</b></summary>\n\nAdd this to your Roo Code MCP configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Augment Code (Local)</b></summary>\n\n**Option A: Using the UI**\n\n1. Click the hamburger menu\n2. Select **Settings**\n3. Navigate to **Tools** section\n4. Click **+ Add MCP** button\n5. Enter command: `npx -y ddc-ci-control-bridge`\n6. Name: **DDC/CI Bridge**\n7. Click **Add**\n\n**Option B: Manual Configuration**\n\nAdd to `settings.json`:\n\n```json\n\"augment.advanced\": {\n  \"mcpServers\": [\n    {\n      \"name\": \"ddc-ci-bridge\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  ]\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in JetBrains AI Assistant (Local)</b></summary>\n\n1. Go to `Settings` → `Tools` → `AI Assistant` → `Model Context Protocol (MCP)`\n2. Click `+ Add`\n3. Select **As JSON** from the dropdown\n4. Add this configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n5. Click `Apply` to save changes\n\n</details>\n\n<details>\n<summary><b>Install in Warp (Local)</b></summary>\n\n1. Navigate `Settings` → `AI` → `Manage MCP servers`\n2. Click `+ Add` button\n3. Paste this configuration:\n\n```json\n{\n  \"DDC/CI Bridge\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n    \"env\": {\n      \"FASTMCP_API_KEY\": \"your-api-key-here\",\n      \"MQTT_ENABLED\": \"false\"\n    },\n    \"working_directory\": null,\n    \"start_on_launch\": true\n  }\n}\n```\n\n4. Click `Save`\n\n</details>\n\n<details>\n<summary><b>Install in OpenAI Codex (Local)</b></summary>\n\nAdd to your Codex MCP configuration:\n\n```toml\n[mcp_servers.ddc-ci-bridge]\ncommand = \"npx\"\nargs = [\"-y\", \"ddc-ci-control-bridge\"]\n\n[mcp_servers.ddc-ci-bridge.env]\nMQTT_ENABLED = \"false\"\n```\n\n**Windows Users**: Use full paths if you encounter timeout errors:\n\n```toml\n[mcp_servers.ddc-ci-bridge]\ncommand = \"cmd\"\nargs = [\"/c\", \"npx\", \"-y\", \"ddc-ci-control-bridge\"]\nstartup_timeout_ms = 20_000\n\n[mcp_servers.ddc-ci-bridge.env]\nSystemRoot = \"C:\\\\Windows\"\nFASTMCP_API_KEY = \"your-api-key-here\"\nMQTT_ENABLED = \"false\"\n```\n\n</details>\n\n<details>\n<summary><b>Install in LM Studio (Local)</b></summary>\n\n1. Navigate to `Program` (right side) → `Install` → `Edit mcp.json`\n2. Add this configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"DDC/CI Bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n3. Click `Save`\n4. Toggle the MCP server on/off from the right side panel\n\n</details>\n\n<details>\n<summary><b>Install in Qodo Gen (Local)</b></summary>\n\n1. Open Qodo Gen chat panel in VSCode or IntelliJ\n2. Click **Connect more tools**\n3. Click **+ Add new MCP**\n4. Add this configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Install in Perplexity Desktop (Local)</b></summary>\n\n1. Navigate `Perplexity` → `Settings`\n2. Select `Connectors`\n3. Click `Add Connector`\n4. Select `Advanced`\n5. Enter Server Name: **DDC/CI Bridge**\n6. Paste this JSON:\n\n```json\n{\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n  \"env\": {\n    \"FASTMCP_API_KEY\": \"your-api-key-here\",\n    \"MQTT_ENABLED\": \"false\"\n  }\n}\n```\n\n7. Click `Save`\n\n</details>\n\n<details>\n<summary><b>Install in Kiro (Local)</b></summary>\n\n1. Navigate `Kiro` → `MCP Servers`\n2. Click `+ Add` button\n3. Paste this configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"DDC/CI Bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      },\n      \"disabled\": false,\n      \"autoApprove\": []\n    }\n  }\n}\n```\n\n4. Click `Save`\n\n</details>\n\n<details>\n<summary><b>Install in BoltAI (Local)</b></summary>\n\n1. Open **Settings** → **Plugins**\n2. Enter this JSON:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n3. Save and restart if needed\n\n</details>\n\n<details>\n<summary><b>Install in Zencoder (Local)</b></summary>\n\n1. Go to Zencoder menu (...)\n2. Select **Agent tools**\n3. Click **Add custom MCP**\n4. Add name and server configuration:\n\n```json\n{\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n  \"env\": {\n    \"FASTMCP_API_KEY\": \"your-api-key-here\",\n    \"MQTT_ENABLED\": \"false\"\n  }\n}\n```\n\n5. Click **Install**\n\n</details>\n\n<details>\n<summary><b>Install in Amazon Q Developer CLI (Local)</b></summary>\n\nAdd to your Amazon Q configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Using Bun or Deno</b></summary>\n\n**Bun:**\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"bunx\",\n      \"args\": [\"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n**Deno:**\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"deno\",\n      \"args\": [\n        \"run\",\n        \"--allow-env\",\n        \"--allow-net\",\n        \"npm:ddc-ci-control-bridge\"\n      ],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      }\n    }\n  }\n}\n```\n\n</details>\n\n<details>\n<summary><b>Windows-Specific Configuration</b></summary>\n\nOn Windows, use this format (example with Cline):\n\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"command\": \"cmd\",\n      \"args\": [\"/c\", \"npx\", \"-y\", \"ddc-ci-control-bridge\"],\n      \"env\": {\n        \"MQTT_ENABLED\": \"false\"\n      },\n      \"disabled\": false,\n      \"autoApprove\": []\n    }\n  }\n}\n```\n\n</details>\n\n---\n\n#### 🌐 Remote Setup (HTTP - Different Machines)\n\nUse this if you want to access monitor controls from a different machine on your network.\n\n<details>\n<summary><b>Step 1: Set up the MCP Server on Monitor-Connected Machine</b></summary>\n\n1. On the machine with monitors, create a `.env` file:\n\n```bash\nDDC_API_KEY=your-secure-random-api-key-here\nMCP_TRANSPORT=sse\nMCP_PORT=8000\n\n# Optional: Enable MQTT for automation platforms\nMQTT_ENABLED=false\nMQTT_HOST=localhost\nMQTT_PORT=1883\n```\n\n2. Start the server:\n\n```bash\nnpm install -g ddc-ci-control-bridge\nddc-ci-bridge\n```\n\nOr using npx:\n\n```bash\nnpx ddc-ci-control-bridge\n```\n\n3. The server will display:\n```\n🔌 MCP Server: http://192.168.1.100:8000\n   Transport: sse\n   API Key: your-api...\n```\n\nNote the IP address and port for client configuration.\n\n</details>\n\n<details>\n<summary><b>Step 2: Configure MCP Clients (Remote Connection)</b></summary>\n\n**Cursor:**\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"url\": \"http://192.168.1.100:8000\",\n      \"headers\": {\n        \"Authorization\": \"Bearer your-secure-random-api-key-here\"\n      }\n    }\n  }\n}\n```\n\n**VS Code:**\n```json\n\"mcp\": {\n  \"servers\": {\n    \"ddc-ci-bridge\": {\n      \"type\": \"http\",\n      \"url\": \"http://192.168.1.100:8000\",\n      \"headers\": {\n        \"Authorization\": \"Bearer your-secure-random-api-key-here\"\n      }\n    }\n  }\n}\n```\n\n**Claude Desktop:**\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"url\": \"http://192.168.1.100:8000\",\n      \"headers\": {\n        \"Authorization\": \"Bearer your-secure-random-api-key-here\"\n      }\n    }\n  }\n}\n```\n\n**Windsurf:**\n```json\n{\n  \"mcpServers\": {\n    \"ddc-ci-bridge\": {\n      \"serverUrl\": \"http://192.168.1.100:8000\",\n      \"headers\": {\n        \"Authorization\": \"Bearer your-secure-random-api-key-here\"\n      }\n    }\n  }\n}\n```\n\n**Note:** Replace `192.168.1.100` with the actual IP address of your monitor-connected machine, and use the same API key you configured in the server's `.env` file.\n\n</details>\n\n---\n\n### Configuration\n\n1. Create a `.env` file:\n```bash\ncp .env.example .env\n```\n\n2. Edit `.env` and configure:\n```bash\nDDC_API_KEY=your-secret-api-key-here\n\n# Enable MQTT for automation platforms (optional)\nMQTT_ENABLED=false\nMQTT_HOST=localhost\nMQTT_PORT=1883\n```\n\n**To enable MQTT**: Set `MQTT_ENABLED=true` and change `MQTT_HOST` to your MQTT broker IP (e.g., Home Assistant IP).\n\n3. Start the server:\n```bash\nnpm run dev\n```\n\n## MQTT Integration\n\nThis server acts as an MQTT client and can connect to any MQTT broker.\n\n### Supported Platforms\n\n- **Home Assistant**: Auto-discovery via MQTT Discovery Protocol → See [Home Assistant Guide](./docs/README-HOMEASSISTANT.md)\n- **openHAB**: MQTT binding with manual thing configuration\n- **Node-RED**: Subscribe to topics for custom flows\n- **Domoticz**: MQTT integration\n- **Generic MQTT**: Any platform that supports MQTT pub/sub\n\n### MQTT Topics\n\n```\nddc-monitor/{index}/brightness/set|get\nddc-monitor/{index}/contrast/set|get\nddc-monitor/{index}/vcp/{code}/set|get\nddc-monitor/{index}/power/set\nddc-monitor/{index}/state\nddc-monitor/bridge/status\n```\n\n## MCP Resources\n\n- `monitor://list` - List all available monitors\n- `monitor://{index}/capabilities` - Full VCP code scan results\n- `monitor://{index}/current-values` - Current values of all supported codes\n- `monitor://{index}/info` - Monitor metadata\n\n## MCP Tools\n\n- `get_vcp_code` - Read a specific VCP code value\n- `set_vcp_code` - Write a value to a VCP code\n- `get_brightness` - Get monitor brightness (0-100)\n- `set_brightness` - Set monitor brightness (0-100)\n- `refresh_monitors` - Re-scan monitors and VCP capabilities\n\n## Development\n\n### Build\n\n```bash\nnpm run build\n```\n\n### Build Executables\n\n```bash\nnpm run build:executables\n```\n\nThis creates standalone executables in `dist/bin/` for Windows, Linux, and macOS.\n\n### Run in Development\n\n```bash\nnpm run dev\n```\n\n## Requirements\n\n- **DDC/CI Support**: Your monitor must support DDC/CI (most modern monitors do)\n- **DDC/CI Enabled**: Enable DDC/CI in your monitor's OSD settings\n- **Permissions**: On Linux, you may need to add your user to the `i2c` group\n\n### Linux Setup\n\n```bash\nsudo usermod -a -G i2c $USER\nsudo modprobe i2c-dev\n```\n\nLog out and log back in for group changes to take effect.\n\n## Environment Variables\n\nSee `.env.example` for all available configuration options.\n\nKey variables:\n- `DDC_API_KEY` - API key for server authentication (required)\n- `MCP_TRANSPORT` - Transport type: `sse` or `stdio` (default: `sse`)\n- `MCP_PORT` - HTTP port for SSE transport (default: `8000`)\n- `MQTT_ENABLED` - Enable MQTT client (default: `false`)\n- `MQTT_HOST` - MQTT broker IP/hostname (default: `localhost`)\n- `MQTT_PORT` - MQTT broker port (default: `1883`)\n- `MQTT_USERNAME` - Auto-configured as `ddc-mcp`\n- `MQTT_PASSWORD` - Auto-configured from `DDC_API_KEY`\n\n## Architecture\n\n```\n┌─────────────────────────────────────────┐\n│       DDC/CI Control Bridge             │\n│                                         │\n│  ┌─────────────────┐  ┌──────────────┐ │\n│  │  MCP Server     │  │ MQTT Client  │ │\n│  │  - Resources    │  │ - Pub/Sub    │ │\n│  │  - Tools        │  │ - Discovery  │ │\n│  └────────┬────────┘  └──────┬───────┘ │\n│           │                  │         │\n│           └────────┬─────────┘         │\n│                    │                   │\n│           ┌────────▼────────┐          │\n│           │ DDC Controller  │          │\n│           │ - VCP Scanning  │          │\n│           │ - Read/Write    │          │\n│           └────────┬────────┘          │\n└────────────────────┼───────────────────┘\n                     │\n            ┌────────▼────────┐\n            │ Physical Monitor│\n            │   (DDC/CI)      │\n            └─────────────────┘\n\nExternal Clients:\n┌──────────────┐  ┌──────────────┐  ┌──────────────┐\n│ AI Agents    │  │ MQTT Broker  │  │ Automation   │\n│ (via MCP)    │  │ (any broker) │  │ Platforms    │\n└──────────────┘  └──────────────┘  └──────────────┘\n```\n\n## License\n\nMIT\n\n## Documentation\n\n- [Home Assistant Integration Guide](./docs/README-HOMEASSISTANT.md) - Complete HA setup\n- [Development Guide](./docs/DEVELOPMENT.md) - Technical architecture and development details\n\n## Contributing\n\nContributions welcome! Please open an issue or PR.\n\n## Troubleshooting\n\n### No monitors found\n\n- Ensure DDC/CI is enabled in your monitor's OSD settings\n- On Linux, check if i2c devices are available: `ls -l /dev/i2c-*`\n- Try running with elevated permissions (not recommended for production)\n\n### MQTT connection failed\n\n- Verify MQTT broker is running\n- Check credentials match the server output\n- Ensure firewall allows MQTT port (1883)\n\n### Commands not working\n\n- Check server logs for errors\n- Verify monitor supports the VCP code\n- Some codes may be read-only\n- Try restarting both server and Home Assistant\n",
  "bytes": 19509,
  "sha": "c40000de9b0baf7cad8bc50da37ced149ce93b525c060c02d911f670b0784bf6",
  "repo_slug": "defozo/ddc-ci-control-bridge",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_defozo_ddc_ci_control_bridge_36627aa8/readme"
}