Does it require an API key?

Yes — the executable requires the DDC_API_KEY environment variable to be set, or it exits immediately.

Can it integrate with home automation?

Yes — it includes an MQTT client with Home Assistant auto-discovery support, configurable via MQTT_ENABLED and MQTT_HOST.

What monitor properties can it control?

Brightness, contrast, power, and input source, plus any VCP code directly via the get/set VCP code tools.

CI Control Bridge

hardwaremonitor-controlmqtthome-automationddc-ci

A cross-platform MCP (and MQTT) server for controlling monitor brightness, contrast, power, and input source over DDC/CI.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

We couldn’t automatically confirm this listing starts correctly

We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y ddc-ci-control-bridge

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Configure Environment Variables (API Keys, Tokens, Options):

Add required secrets below — values are included directly in the generated snippet so you can copy and paste with confidence.

Quick Add:

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "ddc-ci-control-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "ddc-ci-control-bridge"
      ],
      "env": {
        "DDC_API_KEY": "YOUR_VALUE_HERE",
        "MQTT_ENABLED": "YOUR_VALUE_HERE",
        "MQTT_HOST": "YOUR_VALUE_HERE"
      }
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

This server reads and writes VCP codes over DDC/CI to control monitor brightness, contrast, input source, and other display settings, exposing that control as MCP tools for AI/agent integration. It also includes an optional MQTT client with Home Assistant auto-discovery for IoT/automation setups, and ships as an npm package, npx-runnable command, or standalone executable for Windows, Linux, and macOS.

Use cases

Get or set a monitor's brightness or contrast from an AI agent

Read or write an arbitrary VCP code for advanced monitor control

Re-scan connected monitors and their DDC/CI capabilities

Bridge monitor control into a Home Assistant setup via MQTT

Key features

Read/write arbitrary VCP codes over DDC/CI

Dedicated brightness get/set tools

Optional MQTT client with Home Assistant auto-discovery

Cross-platform: Windows, Linux, macOS

Available as npm package, npx command, or standalone executable

Capabilities & Tool Schemas (5)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by CI Control Bridge.

get_vcp_code

Read a specific VCP code value

set_vcp_code

Write a value to a VCP code

get_brightness

Get monitor brightness (0-100)

set_brightness

Set monitor brightness (0-100)

refresh_monitors

Re-scan monitors and VCP capabilities

Documentation Overview

DDC/CI Control Bridge

Multi-protocol server for DDC/CI monitor control with MCP and MQTT support.

Features

DDC/CI Monitor Control: Read and write VCP codes to control monitor brightness, contrast, input source, and more
Model Context Protocol (MCP): Server with resources and tools for AI/agent integration
MQTT Client: Connect to any MQTT broker for IoT/automation platforms
- Home Assistant auto-discovery support
- Generic MQTT pub/sub for custom integrations
Cross-Platform: Works on Windows, Linux, and macOS
Dual Distribution: Available as standalone executable or npm package

Quick Start

Installation

Option 1: NPM Package (Global)

Terminal

npm install -g ddc-ci-control-bridge
ddc-ci-bridge

Option 2: NPX (No Install)

Terminal

npx ddc-ci-control-bridge

Option 3: Standalone Executable

Download the binary for your platform from GitHub Releases:

Windows: ddc-ci-bridge-win.exe
Linux: ddc-ci-bridge-linux
macOS: ddc-ci-bridge-macos

⚠️ Note: The executable requires DDC_API_KEY environment variable to be set, or it will exit immediately.

Windows:

cmd

# Set API key (required)
set DDC_API_KEY=your-secret-key

# Run the executable
ddc-ci-bridge-win.exe

# Or set multiple environment variables
set DDC_API_KEY=your-secret-key
set MQTT_ENABLED=true
set MQTT_HOST=192.168.1.100
ddc-ci-bridge-win.exe

Linux/macOS:

bash

# Make executable (first time only)
chmod +x ddc-ci-bridge-linux  # or ddc-ci-bridge-macos

# Run with API key (required)
DDC_API_KEY=your-secret-key ./ddc-ci-bridge-linux

# Or with multiple environment variables
DDC_API_KEY=your-secret-key MQTT_ENABLED=true MQTT_HOST=192.168.1.100 ./ddc-ci-bridge-linux

Using with MCP Clients:

Configure your MCP client to use the executable path:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "C:\\path\\to\\ddc-ci-bridge-win.exe",
      "args": [],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

MCP Client Setup

Choose between Local (stdio) or Remote (HTTP) setup depending on your needs:

Local Setup: Run MCP server on the same machine as your monitors (recommended for most users)
Remote Setup: Run MCP server on a monitor-connected machine, access from other devices

🖥️ Local Setup (stdio - Same Machine)

Use this if your MCP client is on the same machine as your monitors.

Install in Cursor (Local)

Go to: Settings → Cursor Settings → MCP → Add new global MCP server

Or paste the following configuration into your ~/.cursor/mcp.json file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false",
        "MQTT_HOST": "localhost",
        "MQTT_PORT": "1883"
      }
    }
  }
}

Optional MQTT: Set MQTT_ENABLED=true and configure MQTT_HOST to your MQTT broker IP for automation platform integration.

Install in VS Code (Local)

Add this to your VS Code MCP config file:

json

"mcp": {
  "servers": {
    "ddc-ci-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Claude Desktop (Local)

Open Claude Desktop developer settings and edit your claude_desktop_config.json file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Claude Code (Local)

Run this command:

Terminal

claude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge

Install in Windsurf (Local)

Add this to your Windsurf MCP config file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Cline (Local)

Add this to your Cline MCP configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Zed (Local)

Add this to your Zed settings.json:

config.json

{
  "context_servers": {
    "DDC/CI Bridge": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Roo Code (Local)

Add this to your Roo Code MCP configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Augment Code (Local)

Option A: Using the UI

Click the hamburger menu
Select Settings
Navigate to Tools section
Click + Add MCP button
Enter command: npx -y ddc-ci-control-bridge
Name: DDC/CI Bridge
Click Add

Option B: Manual Configuration

Add to settings.json:

json

"augment.advanced": {
  "mcpServers": [
    {
      "name": "ddc-ci-bridge",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  ]
}

Install in JetBrains AI Assistant (Local)

Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP)
Click + Add
Select As JSON from the dropdown
Add this configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Click Apply to save changes

Install in Warp (Local)

Navigate Settings → AI → Manage MCP servers
Click + Add button
Paste this configuration:

config.json

{
  "DDC/CI Bridge": {
    "command": "npx",
    "args": ["-y", "ddc-ci-control-bridge"],
    "env": {
      "FASTMCP_API_KEY": "your-api-key-here",
      "MQTT_ENABLED": "false"
    },
    "working_directory": null,
    "start_on_launch": true
  }
}

Click Save

Install in OpenAI Codex (Local)

Add to your Codex MCP configuration:

toml

[mcp_servers.ddc-ci-bridge]
command = "npx"
args = ["-y", "ddc-ci-control-bridge"]

[mcp_servers.ddc-ci-bridge.env]
MQTT_ENABLED = "false"

Windows Users: Use full paths if you encounter timeout errors:

toml

[mcp_servers.ddc-ci-bridge]
command = "cmd"
args = ["/c", "npx", "-y", "ddc-ci-control-bridge"]
startup_timeout_ms = 20_000

[mcp_servers.ddc-ci-bridge.env]
SystemRoot = "C:\\Windows"
FASTMCP_API_KEY = "your-api-key-here"
MQTT_ENABLED = "false"

Install in LM Studio (Local)

Navigate to Program (right side) → Install → Edit mcp.json
Add this configuration:

config.json

{
  "mcpServers": {
    "DDC/CI Bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Click Save
Toggle the MCP server on/off from the right side panel

Install in Qodo Gen (Local)

Open Qodo Gen chat panel in VSCode or IntelliJ
Click Connect more tools
Click + Add new MCP
Add this configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Perplexity Desktop (Local)

Read the full README →View source on GitHub →

Related MCP Servers

View all in Home Automation View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

7mo ago

Most recent push to the default branch.

Install check

Inconclusive

Didn't respond in our test window — often a slow first install.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

2 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about CI Control Bridge

npx ddc-ci-control-bridge runs it directly without a global install.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

CI Control Bridge AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/ddc-ci-control-bridge?style=directory)](https://allmcps.com/mcp/ddc-ci-control-bridge)

HTML Embed

<a href="https://allmcps.com/mcp/ddc-ci-control-bridge"><img src="https://allmcps.com/api/badge/ddc-ci-control-bridge?style=directory" alt="CI Control Bridge on AllMCPs" /></a>

Technical Specs & Signals

CategoryHome Automation

PricingFree

16/16 checks healthy over the last 46d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools26/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · ddc-ci-control-bridge (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🏠 Home Automation →Alternatives to CI Control Bridge →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

CI Control Bridge

hardwaremonitor-controlmqtthome-automationddc-ci

A cross-platform MCP (and MQTT) server for controlling monitor brightness, contrast, power, and input source over DDC/CI.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

We couldn’t automatically confirm this listing starts correctly

We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y ddc-ci-control-bridge

No response to initialize.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Configure Environment Variables (API Keys, Tokens, Options):

Add required secrets below — values are included directly in the generated snippet so you can copy and paste with confidence.

Quick Add:

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "ddc-ci-control-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "ddc-ci-control-bridge"
      ],
      "env": {
        "DDC_API_KEY": "YOUR_VALUE_HERE",
        "MQTT_ENABLED": "YOUR_VALUE_HERE",
        "MQTT_HOST": "YOUR_VALUE_HERE"
      }
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Get or set a monitor's brightness or contrast from an AI agent

Read or write an arbitrary VCP code for advanced monitor control

Re-scan connected monitors and their DDC/CI capabilities

Bridge monitor control into a Home Assistant setup via MQTT

Key features

Read/write arbitrary VCP codes over DDC/CI

Dedicated brightness get/set tools

Optional MQTT client with Home Assistant auto-discovery

Cross-platform: Windows, Linux, macOS

Available as npm package, npx command, or standalone executable

Capabilities & Tool Schemas (5)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by CI Control Bridge.

get_vcp_code

Read a specific VCP code value

set_vcp_code

Write a value to a VCP code

get_brightness

Get monitor brightness (0-100)

set_brightness

Set monitor brightness (0-100)

refresh_monitors

Re-scan monitors and VCP capabilities

Documentation Overview

DDC/CI Control Bridge

Multi-protocol server for DDC/CI monitor control with MCP and MQTT support.

Features

DDC/CI Monitor Control: Read and write VCP codes to control monitor brightness, contrast, input source, and more
Model Context Protocol (MCP): Server with resources and tools for AI/agent integration
MQTT Client: Connect to any MQTT broker for IoT/automation platforms
- Home Assistant auto-discovery support
- Generic MQTT pub/sub for custom integrations
Cross-Platform: Works on Windows, Linux, and macOS
Dual Distribution: Available as standalone executable or npm package

Quick Start

Installation

Option 1: NPM Package (Global)

Terminal

npm install -g ddc-ci-control-bridge
ddc-ci-bridge

Option 2: NPX (No Install)

Terminal

npx ddc-ci-control-bridge

Option 3: Standalone Executable

Download the binary for your platform from GitHub Releases:

Windows: ddc-ci-bridge-win.exe
Linux: ddc-ci-bridge-linux
macOS: ddc-ci-bridge-macos

⚠️ Note: The executable requires DDC_API_KEY environment variable to be set, or it will exit immediately.

Windows:

cmd

# Set API key (required)
set DDC_API_KEY=your-secret-key

# Run the executable
ddc-ci-bridge-win.exe

# Or set multiple environment variables
set DDC_API_KEY=your-secret-key
set MQTT_ENABLED=true
set MQTT_HOST=192.168.1.100
ddc-ci-bridge-win.exe

Linux/macOS:

bash

# Make executable (first time only)
chmod +x ddc-ci-bridge-linux  # or ddc-ci-bridge-macos

# Run with API key (required)
DDC_API_KEY=your-secret-key ./ddc-ci-bridge-linux

# Or with multiple environment variables
DDC_API_KEY=your-secret-key MQTT_ENABLED=true MQTT_HOST=192.168.1.100 ./ddc-ci-bridge-linux

Using with MCP Clients:

Configure your MCP client to use the executable path:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "C:\\path\\to\\ddc-ci-bridge-win.exe",
      "args": [],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

MCP Client Setup

Choose between Local (stdio) or Remote (HTTP) setup depending on your needs:

Local Setup: Run MCP server on the same machine as your monitors (recommended for most users)
Remote Setup: Run MCP server on a monitor-connected machine, access from other devices

🖥️ Local Setup (stdio - Same Machine)

Use this if your MCP client is on the same machine as your monitors.

Install in Cursor (Local)

Go to: Settings → Cursor Settings → MCP → Add new global MCP server

Or paste the following configuration into your ~/.cursor/mcp.json file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false",
        "MQTT_HOST": "localhost",
        "MQTT_PORT": "1883"
      }
    }
  }
}

Optional MQTT: Set MQTT_ENABLED=true and configure MQTT_HOST to your MQTT broker IP for automation platform integration.

Install in VS Code (Local)

Add this to your VS Code MCP config file:

json

"mcp": {
  "servers": {
    "ddc-ci-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Claude Desktop (Local)

Open Claude Desktop developer settings and edit your claude_desktop_config.json file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Claude Code (Local)

Run this command:

Terminal

claude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge

Install in Windsurf (Local)

Add this to your Windsurf MCP config file:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Cline (Local)

Add this to your Cline MCP configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Zed (Local)

Add this to your Zed settings.json:

config.json

{
  "context_servers": {
    "DDC/CI Bridge": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Roo Code (Local)

Add this to your Roo Code MCP configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Augment Code (Local)

Option A: Using the UI

Click the hamburger menu
Select Settings
Navigate to Tools section
Click + Add MCP button
Enter command: npx -y ddc-ci-control-bridge
Name: DDC/CI Bridge
Click Add

Option B: Manual Configuration

Add to settings.json:

json

"augment.advanced": {
  "mcpServers": [
    {
      "name": "ddc-ci-bridge",
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  ]
}

Install in JetBrains AI Assistant (Local)

Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP)
Click + Add
Select As JSON from the dropdown
Add this configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Click Apply to save changes

Install in Warp (Local)

Navigate Settings → AI → Manage MCP servers
Click + Add button
Paste this configuration:

config.json

{
  "DDC/CI Bridge": {
    "command": "npx",
    "args": ["-y", "ddc-ci-control-bridge"],
    "env": {
      "FASTMCP_API_KEY": "your-api-key-here",
      "MQTT_ENABLED": "false"
    },
    "working_directory": null,
    "start_on_launch": true
  }
}

Click Save

Install in OpenAI Codex (Local)

Add to your Codex MCP configuration:

toml

[mcp_servers.ddc-ci-bridge]
command = "npx"
args = ["-y", "ddc-ci-control-bridge"]

[mcp_servers.ddc-ci-bridge.env]
MQTT_ENABLED = "false"

Windows Users: Use full paths if you encounter timeout errors:

toml

[mcp_servers.ddc-ci-bridge]
command = "cmd"
args = ["/c", "npx", "-y", "ddc-ci-control-bridge"]
startup_timeout_ms = 20_000

[mcp_servers.ddc-ci-bridge.env]
SystemRoot = "C:\\Windows"
FASTMCP_API_KEY = "your-api-key-here"
MQTT_ENABLED = "false"

Install in LM Studio (Local)

Navigate to Program (right side) → Install → Edit mcp.json
Add this configuration:

config.json

{
  "mcpServers": {
    "DDC/CI Bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Click Save
Toggle the MCP server on/off from the right side panel

Install in Qodo Gen (Local)

Open Qodo Gen chat panel in VSCode or IntelliJ
Click Connect more tools
Click + Add new MCP
Add this configuration:

config.json

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Install in Perplexity Desktop (Local)

Read the full README →View source on GitHub →

Related MCP Servers

View all in Home Automation View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

7mo ago

Most recent push to the default branch.

Install check

Inconclusive

Didn't respond in our test window — often a slow first install.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

2 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about CI Control Bridge

npx ddc-ci-control-bridge runs it directly without a global install.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/ddc-ci-control-bridge?style=directory)](https://allmcps.com/mcp/ddc-ci-control-bridge)

HTML Embed

<a href="https://allmcps.com/mcp/ddc-ci-control-bridge"><img src="https://allmcps.com/api/badge/ddc-ci-control-bridge?style=directory" alt="CI Control Bridge on AllMCPs" /></a>

Technical Specs & Signals

CategoryHome Automation

PricingFree

16/16 checks healthy over the last 46d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools26/30

Adoption & activity2/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · ddc-ci-control-bridge (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🏠 Home Automation →Alternatives to CI Control Bridge →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients