Tolpo vs CI Control Bridge
A side-by-side look at the Tolpo and CI Control Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TolpoHome Automation · Local subprocess (stdio)Local-first control of TP-Link Tapo smart-home devices for AI agents44FairAuth: not declaredVerdict: choose Tolpo for home automation work as a local process; choose CI Control Bridge for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose Tolpo when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
Choose CI Control Bridge when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DDC_API_KEY, MQTT_ENABLED, MQTT_HOST. - You want tools like
get_vcp_code, set_vcp_code, get_brightness.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tolpo | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | DDC_API_KEYMQTT_ENABLEDMQTT_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Tolpo | View CI Control Bridge |
Tools & capabilities
Tolpo tools
No tool names declared yet. Check the project README from the listing page.
CI Control Bridge tools 5
get_vcp_codeRead a specific VCP code valueset_vcp_codeWrite a value to a VCP codeget_brightnessGet monitor brightness (0-100)set_brightnessSet monitor brightness (0-100)refresh_monitorsRe-scan monitors and VCP capabilities
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Tolpo
{
"mcpServers": {
"tolpo": {
"command": "npx",
"args": [
"-y",
"tolpo"
]
}
}
}
CI Control Bridge
{
"mcpServers": {
"ddc-ci-control-bridge": {
"command": "npx",
"args": [
"-y",
"ddc-ci-control-bridge"
],
"env": {
"DDC_API_KEY": "YOUR_DDC_API_KEY_HERE",
"MQTT_ENABLED": "YOUR_MQTT_ENABLED_HERE",
"MQTT_HOST": "YOUR_MQTT_HOST_HERE"
}
}
}
}
Frequently asked questions
Tolpo is categorized under Home Automation and uses a local stdio subprocess. CI Control Bridge belongs to Home Automation and uses a local stdio subprocess. Pick Tolpo for home automation work and CI Control Bridge for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Tolpo has no declared pricing — check the project's own site. CI Control Bridge is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tolpo and ddc-ci-control-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tolpo has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 8 GitHub stars. CI Control Bridge has 53/100 (Good) with 3 views, 0 installs and 5 GitHub stars.