Skip to main content
Glama
Bond MCP Server
by madorn

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

  1. Open the Bond Home app on your mobile device

  2. Go to Settings → Bond Bridge → Advanced → API

  3. 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

  1. Create and activate virtual environment:

    python3 -m venv bond-mcp-env
    source bond-mcp-env/bin/activate  # On Windows: bond-mcp-env\Scripts\activate
  2. Install dependencies:

    pip install -r requirements.txt
  3. Configure environment:

    cp .env.example .env
    # Edit .env with your Bond Bridge settings
  4. Run 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=INFO

Available Tools

Device Management

  • list_devices() - List all Bond devices

  • get_device_info(device_id) - Get detailed device information

  • get_device_state(device_id) - Get current device state

  • get_bridge_info() - Get Bond Bridge information

Device Control

  • toggle_device_power(device_id) - Toggle device on/off

  • send_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 shades

    • Actions: "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:

Troubleshooting

Common Issues

  1. Connection refused: Ensure Bond Bridge IP is correct and accessible

  2. Authentication failed: Verify Bond token is correct (use Local Token, not Cloud Token)

  3. Device not found: Check device ID exists using list_devices()

  4. 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 tools
control_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

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      9
      1
      MIT