Bond MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bond MCP Server turn on the living room fan and set it to medium speed"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bond MCP Server
A Model Context Protocol (MCP) server that provides tools for controlling Bond Bridge smart home devices. This server enables AI assistants like Claude to interact with ceiling fans, fireplaces, shades, lights, and other RF-controlled devices through Bond Bridge hubs.
Features
Device Management: List and get information about all connected Bond devices
Fan Control: Control ceiling fan speed, direction, and power state
Shade Control: Open, close, and set positions for motorized shades
Light Control: Control dimmable lights and brightness levels
Custom Actions: Send any Bond API action to devices
Bridge Information: Get Bond Bridge status and configuration
Related MCP server: Alexa Home Automation MCP Server
Quick Start
Prerequisites
Bond Bridge on your local network
Bond API token (obtained from Bond Home app)
Getting Your Bond Token
Open the Bond Home app on your mobile device
Go to Settings → Bond Bridge → Advanced → API
Copy the Local Token (not the Cloud Token)
Add to your MCP settings:
{
"mcpServers": {
"bond": {
"command": "podman",
"args": [
"run", "-i", "--rm",
"-e", "BOND_TOKEN=your_token_here",
"-e", "BOND_HOST=192.168.1.100",
"quay.io/madorn/bond-mcp-server:latest"
]
}
}
}Installation
Create and activate virtual environment:
python3 -m venv bond-mcp-env source bond-mcp-env/bin/activate # On Windows: bond-mcp-env\Scripts\activateInstall dependencies:
pip install -r requirements.txtConfigure environment:
cp .env.example .env # Edit .env with your Bond Bridge settingsRun the server:
python -m bond_mcp.server
Configuration
Create a .env file with your Bond Bridge configuration:
# Required: Bond Bridge settings
BOND_TOKEN=your_bond_api_token_here
BOND_HOST=192.168.1.100
# Optional: Connection settings
BOND_TIMEOUT=10.0
BOND_MAX_RETRIES=3
BOND_RETRY_DELAY=1.0
# Optional: Logging
LOG_LEVEL=INFOAvailable Tools
Device Management
list_devices()- List all Bond devicesget_device_info(device_id)- Get detailed device informationget_device_state(device_id)- Get current device stateget_bridge_info()- Get Bond Bridge information
Device Control
toggle_device_power(device_id)- Toggle device on/offsend_custom_action(device_id, action, argument?)- Send custom Bond action
Fan Control
set_fan_speed(device_id, speed)- Set fan speed (0-8)set_fan_direction(device_id, direction)- Set direction ("forward"/"reverse")
Shade Control
control_shades(device_id, action, position?)- Control shadesActions: "open", "close", "set_position"
Position: 0-100 (for set_position action)
Light Control
set_light_brightness(device_id, brightness)- Set brightness (0-100)
Bond API Reference
This server uses the Bond Local API v2:
Base URL:
http://{bridge_ip}/v2/Authentication: Bearer token in Authorization header
Troubleshooting
Common Issues
Connection refused: Ensure Bond Bridge IP is correct and accessible
Authentication failed: Verify Bond token is correct (use Local Token, not Cloud Token)
Device not found: Check device ID exists using
list_devices()Action not supported: Verify device supports the action using
get_device_info()
Debug Logging
Enable debug logging by setting LOG_LEVEL=DEBUG in your environment.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
10 toolscontrol_shadesB
Control motorized shades.
Args: device_id: The Bond shade device identifier action: Action to perform ("open", "close", or "set_position") position: Position percentage (0-100) when action is "set_position"
Returns: Result of the shade control operation.
Inputs: device_id (required), action (required), position. Returns: object
get_bridge_infoA
Get Bond Bridge information and status.
Returns: Bridge information including version, uptime, and configuration.
Inputs: no named parameters. Returns: object
get_device_infoB
Get detailed information about a specific device.
Args: device_id: The Bond device identifier
Returns: Detailed device information including capabilities and properties.
Inputs: device_id (required). Returns: object
get_device_stateB
Get current state of a Bond device.
Args: device_id: The Bond device identifier
Returns: Current device state including power, speed, direction, etc.
Inputs: device_id (required). Returns: object
list_devicesA
List all Bond devices connected to the bridge.
Returns: Dictionary containing all devices with their basic information.
Inputs: no named parameters. Returns: object
send_custom_actionB
Send a custom action to a Bond device.
Args: device_id: The Bond device identifier action: Bond action name (e.g., "TurnOn", "TurnOff", "SetSpeed") argument: Optional argument for the action
Returns: Result of the custom action.
Inputs: device_id (required), action (required), argument. Returns: object
set_fan_directionA
Set fan direction for a ceiling fan device.
Args: device_id: The Bond fan device identifier direction: Fan direction ("forward" or "reverse")
Returns: Result of the direction change operation.
Inputs: device_id (required), direction (required). Returns: object
set_fan_speedA
Set fan speed for a ceiling fan device.
Args: device_id: The Bond fan device identifier speed: Fan speed level (0-8, where 0 is off)
Returns: Result of the speed change operation.
Inputs: device_id (required), speed (required). Returns: object
set_light_brightnessA
Set brightness for a dimmable light device.
Args: device_id: The Bond light device identifier brightness: Brightness percentage (0-100, where 0 is off)
Returns: Result of the brightness change operation.
Inputs: device_id (required), brightness (required). Returns: object
toggle_device_powerC
Toggle power state of a Bond device (on/off).
Args: device_id: The Bond device identifier
Returns: Result of the toggle operation.
Inputs: device_id (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have distinct purposes targeting specific device types or actions, but some overlap exists: 'control_shades' and 'send_custom_action' could be confused for shade operations, and 'toggle_device_power' might overlap with custom actions for power control. Descriptions help clarify, but agents might misselect between these in edge cases.
Tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly. Examples include 'get_bridge_info', 'list_devices', 'set_fan_speed', and 'toggle_device_power', making them predictable and easy to understand.
With 10 tools, this server is well-scoped for controlling Bond devices like shades, fans, and lights. Each tool serves a clear function, such as retrieving information, listing devices, or performing specific actions, without being overly sparse or bloated.
The toolset provides good coverage for device control, including CRUD-like operations (list, get, control) and specific actions for common devices. A minor gap is the lack of a dedicated tool for creating or deleting devices, but agents can likely work around this using existing tools like 'send_custom_action' or bridge configurations.
Related MCP Connectors
Control your Tesla from your AI assistant - climate, charging, access, and security.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each device’s supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
Versioned skills and Binders for AI assistants. Requires a Bindry account and workspace API key.
Related MCP Servers
- AlicenseCqualityFmaintenanceEnables AI assistants to control SwitchBot devices, providing functionalities like device management, scene execution, and sensor information monitoring through the SwitchBot API.37ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to control Alexa-connected smart home devices, including voice announcements, music control, smart lighting, sensor monitoring, and volume management through the Alexa API.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.91MIT