Bond MCP Server

Bond MCP Server

Enables AI assistants to control Bond Bridge smart home devices including ceiling fans, motorized shades, dimmable lights, and other RF-controlled devices. Provides comprehensive device management and control capabilities through the Bond Local API.

Category
Visit Server

README

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

Quick Start

Prerequisites

  • Python 3.11 or higher
  • Bond Bridge on your local network
  • Bond API token (obtained from Bond Home app)

Installation

  1. Create and activate virtual environment:

    python3.11 -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
    

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)

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

Podman Usage

Build and Run

# Build the container
podman build -t bond-mcp-server .

# Run with environment variables
podman run -i --rm \
  -e BOND_TOKEN=your_token_here \
  -e BOND_HOST=192.168.1.100 \
  bond-mcp-server

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)

MCP Client Integration

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",
        "bond-mcp-server"
      ]
    }
  }
}

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.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured