Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for MQTT 5.0 brokers (publish, subscribe, topic discovery).
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
MQTT_HOST, MQTT_PORT, MQTT_USERNAME, MQTT_PASSWORD, MQTT_USE_TLSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mqtt": {
"command": "uvx",
"args": [
"mqtt5-mcp-server"
],
"env": {
"MQTT_HOST": "your-value",
"MQTT_PORT": "your-value",
"MQTT_USERNAME": "your-value",
"MQTT_PASSWORD": "your-value",
"MQTT_USE_TLS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add mqtt --env MQTT_HOST=your-value --env MQTT_PORT=your-value --env MQTT_USERNAME=your-value --env MQTT_PASSWORD=your-value --env MQTT_USE_TLS=your-value -- uvx mqtt5-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mqtt": {
"command": "uvx",
"args": [
"mqtt5-mcp-server"
],
"env": {
"MQTT_HOST": "your-value",
"MQTT_PORT": "your-value",
"MQTT_USERNAME": "your-value",
"MQTT_PASSWORD": "your-value",
"MQTT_USE_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mqtt": {
"type": "stdio",
"command": "uvx",
"args": [
"mqtt5-mcp-server"
],
"env": {
"MQTT_HOST": "your-value",
"MQTT_PORT": "your-value",
"MQTT_USERNAME": "your-value",
"MQTT_PASSWORD": "your-value",
"MQTT_USE_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MQTT_PORT envMQTT_USERNAME envMQTT_USE_TLS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account nagarjunr, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: MQTT_HOST, MQTT_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Fomu MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol (MCP) server for MQTT — the standard IoT publish/subscribe messaging protocol. Works against any MQTT broker (Eclipse Mosquitto, EMQX, HiveMQ, AWS IoT Core, Azure IoT Hub's MQTT endpoint, etc): only the standard MQTT 5.0 wire protocol is used, no broker-specific admin APIs.
Built with FastMCP and paho-mqtt.
| Tool | Description |
|---|---|
get_connection_status() | Report this connector's broker connection state. |
publish_message(topic, payload, qos, retain, ...) | Publish a message. Supports MQTT5 properties (content type, message expiry, response topic, correlation data, user properties) and optionally blocks until the broker acknowledges delivery (QoS 1/2). |
start_subscription(topic_filter, qos, ...) | Start receiving messages matching a topic filter (supports +/# wildcards). Returns a session_id. |
get_messages(session_id, max_messages, timeout_seconds) | Drain buffered messages from a subscription session; can wait briefly for one to arrive. |
stop_subscription(session_id) | Stop a session and unsubscribe (if no other session needs the same filter). |
list_subscriptions() | List all active subscription sessions. |
discover_topics(topic_filter, duration_seconds, max_topics) | Approximate a "list topics" operation via retained messages — MQTT has no native topic-listing operation. |
MQTT is a continuous publish/subscribe stream, not a request/response API. A single MCP tool call can't "wait forever" for messages, so subscribing works in two steps: start_subscription registers interest and buffers messages in the background (one shared broker connection, dispatched in-process by topic filter), then get_messages drains that buffer on however many tool calls you want, optionally waiting a bounded amount of time for new data. Call stop_subscription when done.
| Env var | Required | Description |
|---|---|---|
MQTT_HOST | Yes | Broker hostname or IP. |
MQTT_PORT | No | Default 1883 (or 8883 for TLS — set explicitly). |
MQTT_USERNAME / MQTT_PASSWORD | No | Broker credentials. |
MQTT_CLIENT_ID | No | Defaults to a broker-assigned ID. |
MQTT_KEEPALIVE | No | Seconds, default 60. |
MQTT_CONNECT_TIMEOUT | No | Seconds to wait for the initial connect, default 10. |
MQTT_TRANSPORT | No | tcp (default) or websockets. |
MQTT_WS_PATH | No | Path for the websocket transport, default /mqtt. |
MQTT_USE_TLS | No | true/false, default false. |
MQTT_TLS_CA_CERTS | No | Path to a CA bundle. Omit to use the system trust store. |
MQTT_TLS_CLIENT_CERT / MQTT_TLS_CLIENT_KEY | No | For mutual TLS. |
MQTT_TLS_INSECURE | No | Skip hostname verification — for self-signed test certs only. |
MQTT_WILL_TOPIC / MQTT_WILL_PAYLOAD / MQTT_WILL_QOS / MQTT_WILL_RETAIN | No | Last Will and Testament, set once at connect time. |
uv sync
export MQTT_HOST=localhost export MQTT_PORT=1883 export MQTT_USERNAME=mqtt export MQTT_PASSWORD=mqtt uv run mqttmcpserver.py
See mcp.json for ready-to-use client configs (stdio and Docker).
This repo's design principles call for testing against a real instance rather than mocks. docker-compose.yml spins up Eclipse Mosquitto (2.x, MQTT5-capable) with password auth, plus a TLS listener with self-signed certs for testing the TLS/mTLS code paths.
./docker/gen-test-certs.sh # one-time: generate throwaway TLS test certs (needs openssl)
docker compose up -d # start Mosquitto on localhost:1883 (plain, user: mqtt / pass: mqtt) and :8883 (TLS) uv run pytest -v # tests/conftest.py also starts/stops the stack automatically docker compose down # stop it manually if you started it yourself
docker-compose.yml and the files under docker/ configure the open-source Eclipse Mosquitto broker (EPL-2.0) for local testing only — they are not part of the MCP server itself.