iotforge
Allows discovery and control of Bluetooth Low Energy (BLE) devices, such as BLE lights, through adapter plugins.
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., "@iotforge discover all IoT devices on my network"
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.
iotforge
An MCP server for discovering and controlling IoT devices on your local network and via Bluetooth LE.
What it does
iotforge exposes your LAN and BLE devices as MCP tools so any MCP-compatible AI assistant can:
Discover devices on your local network (mDNS, ARP) and Bluetooth LE
Register discovered devices into a persistent inventory
Control devices through adapter plugins (smart plugs, BLE lights, etc.)
Query device status and inventory via MCP resources
Related MCP server: matter-mcp-server
Architecture
MCP Client (Claude, etc.)
│
▼
┌─────────────────────────────┐
│ iotforge MCP Server │
│ (stdio or SSE transport) │
├─────────────────────────────┤
│ Tools: discover, register, │
│ control, status │
│ Resources: inventory, │
│ pending │
├─────────────────────────────┤
│ Core: Scanner, Registry, │
│ Discovery Service │
├─────────────────────────────┤
│ Adapters: Meross, BLE │
│ Database: SQLite (async) │
└─────────────────────────────┘
│ │
▼ ▼
LAN/mDNS BLE/GATTMCP Tools
Tool | Description |
| Scan WiFi/LAN and BLE for devices |
| List devices awaiting registration |
| Promote a pending device to the registry |
| Dismiss a pending device |
| List registered devices with filters |
| Send a command to a device |
| Get current device status |
MCP Resources
Resource | Description |
| Full device inventory (markdown) |
| Pending devices (markdown) |
Installation
pip install -e ".[all]"Optional extras: meross (Meross smart plugs), ble (Bluetooth LE via bleak).
Configuration
Copy config.example.yaml and edit:
cp config.example.yaml config.yamlKey settings: network range, scan intervals, transport mode (stdio/SSE), database path.
Usage
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"iotforge": {
"command": "iotforge",
"args": ["config.yaml"]
}
}
}Standalone (SSE mode)
iotforge config.yamlSet server.transport: sse in your config to expose an HTTP endpoint.
BLE Scripts
The scripts/ directory contains standalone BLE utilities:
elk_ble_ctl.py— GATT controller for ELK-BLEDDM LED strips (service 0xFFF0)lampsmart_pro.py— BLE ADV broadcast controller for LampSmart Pro ceiling lights (multiple protocol versions)ble_adv_sniffer.py— Raw HCI BLE advertisement sniffer for protocol discovery
Adapters
iotforge uses a plugin adapter system. Built-in adapters:
meross — Meross smart plugs/switches (requires
meross-iot)ble_light — BLE GATT light control (requires
bleak)
Custom adapters implement the BaseAdapter interface in src/iotforge/adapters/base.py.
Development
pip install -e ".[dev]"
ruff check .
python -m pytest --cov=iotforgeLicense
MIT — see LICENSE.
Available Tools
7 toolslan_device_controlC
Send a command to a device.
Inputs: command (required), device_id (required), args. Returns: object
lan_device_listC
List registered devices with current status.
Inputs: filter_room, filter_type, online_only, filter_transport. Returns: object
lan_device_registerC
Promote a pending device to the registry.
Inputs: name (required), pending_id (required), room, adapter_type. Returns: object
lan_device_statusC
Get detailed current status of a device.
Inputs: device_id (required). Returns: object
lan_discoverA
Discover devices on local network and Bluetooth.
Scans WiFi/LAN and Bluetooth LE simultaneously. Returns a discovery report with new, updated, lost devices.
Inputs: scan_type, network_range, timeout_seconds. Returns: object
lan_discover_pendingB
List devices awaiting manual registration.
Inputs: filter_transport. Returns: object
lan_pending_dismissC
Dismiss a pending device (hide from pending list).
Inputs: pending_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 7 tools
Each tool targets a distinct operation: discovery trigger, pending list, pending registration, pending dismissal, registered device list, device control, and device status. No two tools overlap in purpose, so an agent can easily select the correct tool for a given task.
All tools share the 'lan_' prefix, providing a unified namespace. However, naming mixes verb-first (lan_discover) and noun-first (lan_device_register) patterns, and lan_device_status uses a noun instead of an action verb. These are minor deviations that don't severely impair readability.
Seven tools is ideal for a local network device management server. The set covers discovery, the pending device workflow, and registered device operations without unnecessary redundancy, fitting comfortably within the 3-15 tool range.
The tool set covers the core lifecycle from discovery through pending approval and registration, plus device listing, control, and status retrieval. Notable gaps include no unregister/delete operation for registered devices and no update device details, but these are minor for a LAN management use case.
Maintenance
Related MCP Connectors
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Connect AI agents to discover services and coordinate real-world tasks.
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/
Turns a phone into a camera+Bluetooth remote so AI assistants can see and control any PC.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables natural language control of WeMo smart home devices for power, brightness, and device management through AI assistants. It features a high-reliability multi-phase discovery process to scan, monitor, and configure devices across a local network.1166 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to directly interact with Matter devices and protocol operations, including device commissioning, attribute read/write, commands, and event monitoring, through natural language.7MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to control Roku TVs on the local network via natural language commands.6-
- FlicenseBqualityDmaintenanceEnables discovery and control of smart appliances (TVs, media devices) on the local network through natural language, supporting providers like Roku, Google TV, and Home Assistant.18-