Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ddc-ci-control-bridge": {
"command": "npx",
"args": [
"-y",
"ddc-ci-control-bridge"
]
}
}
}Run this in your terminal
claude mcp add ddc-ci-control-bridge -- npx -y ddc-ci-control-bridgePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ddc-ci-control-bridge": {
"command": "npx",
"args": [
"-y",
"ddc-ci-control-bridge"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ddc-ci-control-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ddc-ci-control-bridge"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Defozo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.5) reached the registry 13 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Multi-protocol server for DDC/CI monitor control with MCP and MQTT support.
Option 1: NPM Package (Global)
npm install -g ddc-ci-control-bridge
ddc-ci-bridge
Option 2: NPX (No Install)
npx ddc-ci-control-bridge
Option 3: Standalone Executable
Download the binary for your platform from GitHub Releases:
ddc-ci-bridge-win.exeddc-ci-bridge-linuxddc-ci-bridge-macos⚠️ Note: The executable requires DDC_API_KEY environment variable to be set, or it will exit immediately.
Windows:
# Set API key (required)
set DDC_API_KEY=your-secret-key
ddc-ci-bridge-win.exe
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:
# Make executable (first time only)
chmod +x ddc-ci-bridge-linux # or ddc-ci-bridge-macos
DDC_API_KEY=your-secret-key ./ddc-ci-bridge-linux
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:
{
"mcpServers": { "ddc-ci-bridge": { "command": "C:\\path\\to\\ddc-ci-bridge-win.exe", "args": [], "env": { "MQTT_ENABLED": "false" } } } }
Choose between Local (stdio) or Remote (HTTP) setup depending on your needs:
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:
{
"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:
"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:
{
"mcpServers": { "ddc-ci-bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Install in Claude Code (Local)
Run this command:
claude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge
Install in Windsurf (Local)
Add this to your Windsurf MCP config file:
{
"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:
{
"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:
{
"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:
{
"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
npx -y ddc-ci-control-bridgeOption B: Manual Configuration
Add to settings.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)
Settings → Tools → AI Assistant → Model Context Protocol (MCP)+ Add{
"mcpServers": { "ddc-ci-bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Apply to save changesInstall in Warp (Local)
Settings → AI → Manage MCP servers+ Add button{
"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 } }
SaveInstall in OpenAI Codex (Local)
Add to your Codex MCP configuration:
[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:
[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)
Program (right side) → Install → Edit mcp.json{
"mcpServers": { "DDC/CI Bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
SaveInstall in Qodo Gen (Local)
{
"mcpServers": { "ddc-ci-bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Install in Perplexity Desktop (Local)
Perplexity → SettingsConnectorsAdd ConnectorAdvanced{
"command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "FASTMCP_API_KEY": "your-api-key-here", "MQTT_ENABLED": "false" } }
SaveInstall in Kiro (Local)
Kiro → MCP Servers+ Add button{
"mcpServers": { "DDC/CI Bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" }, "disabled": false, "autoApprove": [] } } }
SaveInstall in BoltAI (Local)
{
"mcpServers": { "ddc-ci-bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Install in Zencoder (Local)
{
"command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "FASTMCP_API_KEY": "your-api-key-here", "MQTT_ENABLED": "false" } }
Install in Amazon Q Developer CLI (Local)
Add to your Amazon Q configuration:
{
"mcpServers": { "ddc-ci-bridge": { "command": "npx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Using Bun or Deno
Bun:
{
"mcpServers": { "ddc-ci-bridge": { "command": "bunx", "args": ["-y", "ddc-ci-control-bridge"], "env": { "MQTT_ENABLED": "false" } } } }
Only the beginning is shown; read the rest in the repo