mqtt-mcp-server
Related Servers
Alternatives to mqtt-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to interact with MQTT brokers through publish, subscribe, and query operations. Provides fine-grained topic permissions with wildcard support for secure IoT device communication and sensor data access.1BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceProvides comprehensive SQLite database interaction for AI agents, including data manipulation, schema inspection, and automated query logging. It features a unique context preservation pattern that uses a dedicated meta-table to help autonomous agents maintain self-documenting database architectures.25 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.2612 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to MQTT brokers for smart home automation and IoT device control, enabling topic discovery, sensor reading, command sending, and event monitoring.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to query a SQLite database using natural language through the Model Context Protocol (MCP). Includes security guardrails that block destructive SQL operations.-
- FlicenseNot gradedqualityDmaintenanceProvides MQTT communication capabilities for Large Language Models and other clients, enabling connections to MQTT brokers, publishing and subscribing to topics, and managing real-time messaging workflows.-
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: broker_konflikte, find_silent, get_gaps, get_history, get_last, get_tree, list_topics, publish, and status each target a different query. There is mild overlap between list_topics and get_tree (inventory vs. tree view) and between find_silent and get_gaps (device silent vs. collector disconnected), but the descriptions explicitly distinguish these cases.
Four tools follow a clean get_* pattern (get_gaps, get_history, get_last, get_tree) plus list_topics, but broker_konflikte is a German noun-first name and find_silent uses a different verb style, while publish and status are bare verbs/nouns. All snake_case, but the verb conventions are mixed and languages are inconsistent.
Nine tools is well-scoped for an MQTT broker client, covering query, diagnostics, write, and status without redundancy. Each tool earns its place in the workflow.
The surface covers topic history, latest value, tree/list inventory, silence and gap diagnostics, conflict detection, publish, and status — a solid read/diagnostic/write lifecycle. Minor gaps like retained-message management or subscription/streaming operations exist but are not essential.