Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
A Model Context Protocol (MCP) server for ZigBee2MQTT that provides intelligent device discovery and control for AI assistants.
🌐 Remote-Capable! This MCP server can run on a remote server (e.g., where your MQTT broker runs) and you can access it from your Mac via HTTP. See for details!
A Model Context Protocol (MCP) server for ZigBee2MQTT that provides intelligent device discovery and control for AI assistants
This MCP server connects to your MQTT broker and automatically analyzes all ZigBee devices connected via ZigBee2MQTT. It learns the structure and capabilities of each device and makes this information available to AI assistants through MCP tools.
✅ Device Metadata (Name, model, manufacturer) ✅ Field Schemas (Which fields does a device have? What data types?) ✅ Capabilities (Can dim, change color, measure temperature, etc.) ✅ Current State (Only last value, no history)
❌ Not Stored: Complete message history, time-based sensor data
Estimated Database Size: ~1-2 MB for 100 devices (instead of GB with full history!)
Clone repository
git clone <repository-url>
cd zigbeeMCP
Create environment file
cp .env.example .env
Configure .env
MQTT_BROKER_URL=mqtt://192.168.1.100:1883
MQTT_USERNAME=your_user
MQTT_PASSWORD=your_password
MQTT_BASE_TOPIC=zigbee2mqtt
DB_PATH=/data/zigbee2mqtt.db
# Log Level: debug, info, warn, error, silent
# Recommended: error (minimal output)
LOG_LEVEL=error
Start container
docker compose up -d
View logs
docker compose logs -f
Install dependencies
npm install
Compile TypeScript
npm run build
Start
npm start
Add the following to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"zigbee2mqtt": {
"command": "docker",
"args": [
"exec",
"-i",
"zigbee2mqtt-mcp",
"node",
"dist/index.js"
]
}
}
}
Or for local installation:
{
"mcpServers": {
"zigbee2mqtt": {
"command": "node",
"args": ["/path/to/zigbeeMCP/dist/index.js"],
"env": {
"MQTT_BROKER_URL": "mqtt://localhost:1883",
"MQTT_BASE_TOPIC": "zigbee2mqtt",
"DB_PATH": "/path/to/zigbee2mqtt.db"
}
}
}
}
The MCP server provides the following tools:
list_devicesLists all ZigBee devices.
Example:
Show me all my ZigBee devices
get_device_infoShows detailed information about a specific device.
Parameters:
device: Device friendly name or IEEE addressExample:
Show me details for the living room lamp
find_devicesSearches for devices by name, model, or description.
Parameters:
query: Search termExample:
Find all lamps in the living room
get_device_stateShows the current state of a device.
Parameters:
device: Device friendly name or IEEE addressExample:
Is the living room lamp on?
send_commandSends a command to a device.
Parameters:
device: Device friendly name or IEEE addresscommand: Command as JSON objectExample:
Turn on the living room lamp
Set brightness to 50%
find_by_capabilityFinds all devices with a specific capability.
Parameters:
capability: Capability type (e.g., on_off, brightness, temperature_sensor)Example:
Show all dimmable devices
Which devices can measure temperature?
Common Capabilities:
on_off - Can be turned on/offbrightness - Dimmablecolor_temperature - Color temperature adjustablecolor - Color changeabletemperature_sensor - Temperature sensorhumidity_sensor - Humidity sensorcontact_sensor - Contact sensoroccupancy_sensor - Motion sensorget_integration_infoProvides integration information for n8n or other tools.
Parameters:
device: Device friendly name or IEEE addressExample:
How can I integrate the living room lamp into n8n?
get_statsShows statistics about the ZigBee network.
Example:
How many devices are connected?
get_device_documentationProvides links to official Zigbee2MQTT documentation for a specific device.
Parameters:
device: Device friendly name or IEEE addressExample:
Show me the documentation for my Philips Hue lamp
How can I best control the "living_room_lamp" device?
What can my IKEA TRADFRI switch do?
Returns:
get_recent_devicesLists devices that were added to the ZigBee network within the last N days.
Parameters:
days: Number of days to look back (default: 7)Example:
Which devices were added in the last week?
Show me all new devices since yesterday
Which devices have I paired in the last 30 days?
Returns:
created_at: Timestamp when device was addedlast_seen: Timestamp of last messageupdated_at: Last updateNote: All timestamps are Unix timestamps (milliseconds since 1970-01-01).
User: "Is there a lamp in the living room?"
Claude: [Uses find_devices with query="living room"]
→ "Yes, I found 'living_room_ceiling_lamp' (Philips Hue White)"
User: "Turn it on"
Claude: [Uses send_command with {"state": "ON"}]
→ "The lamp has been turned on"
User: "How can I use this lamp in n8n?"
Claude: [Uses get_integration_info]
→ "You can use these MQTT topics:
- Read: zigbee2mqtt/living_room_ceiling_lamp
- Write: zigbee2mqtt/living_room_ceiling_lamp/set
Example payload: {"state": "ON", "brightness": 200}"
User: "What can my IKEA TRADFRI switch do?"
Claude: [Uses get_device_documentation]
→ "Your IKEA TRADFRI switch (Model: E1743) supports:
- Capabilities: button, battery
- Documentation: https://www.zigbee2mqtt.io/supported-devices/#s=E1743
- There you'll find all button events and MQTT payloads!"
User: "Which devices did I add in the last week?"
Claude: [Uses get_recent_devices with days=7]
→ "3 devices were added in the last 7 days:
1. living_room_outlet (OSRAM Smart+ Plug) - 2 days ago
2. bathroom_sensor (Aqara Temperature Sensor) - 5 days ago
3. hallway_lamp (Philips Hue) - 6 days ago"
┌─────────────────────┐
│ AI Assistant │
│ (Claude Desktop) │
└──────────┬──────────┘
│ MCP Protocol (stdio)
┌──────────▼──────────┐
│ MCP Server │
│ - Tools Handler │
│ - Response Gen. │
└──────────┬──────────┘
│
┌──────────▼──────────┐ ┌──────────────────┐
│ SQLite Database │ │ MQTT Listener │
│ - Devices │ │ - Subscribe All │
│ - Fields │◄─────┤ - Process Msgs │
│ - Capabilities │ │ - Discovery │
│ - Current State │ └────────┬─────────┘
└─────────────────────┘ │
│
┌───────▼────────┐
│ MQTT Broker │
│ (Mosquitto) │
└───────┬────────┘
│
┌───────▼────────┐
│ ZigBee2MQTT │
│ - ZigBee Net │
│ - Devices │
└────────────────┘
# Check logs
docker compose logs
# Rebuild container
docker compose down
docker compose build --no-cache
docker compose up -d
.envmqtt://host.docker.internal:1883zigbee2mqtt/bridge/state should be "online".env - must match ZigBee2MQTT config# Reset database
docker compose down
rm -rf data/
docker compose up -d
The MCP server uses a configurable logging system:
Adjust in .env:
# Minimal output (recommended)
LOG_LEVEL=error
# For debugging
LOG_LEVEL=debug
Log Levels:
silent - No outputerror - Only errors (recommended for Claude Desktop)warn - Warnings + errorsinfo - Normal outputdebug - All detailsAfter changes:
docker compose restart
# Install dependencies
npm install
# TypeScript in watch mode
npm run watch
# In another terminal: start server
npm run dev
src/
├── index.ts # Main entry point
├── types.ts # TypeScript definitions
├── database.ts # SQLite database logic
├── mqtt-listener.ts # MQTT client & message handler
├── schema-discovery.ts # Schema discovery engine
└── mcp-server.ts # MCP server & tools
MIT
For questions or issues, please create an issue on GitHub.
A Model Context Protocol (MCP) server for ZigBee2MQTT that provides intelligent device discovery and control for AI assistants
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
MCP2ZigBee2MQTT s'exécute en local via stdio.
Dernière vérification : 2026-10-28. A Model Context Protocol (MCP) server for ZigBee2MQTT that provides intelligent device discovery and control for AI assistants
