NotifyMCP
Allows publishing messages to an MQTT broker via the publish_message tool, enabling agents to send notifications or data to MQTT topics.
Click on "Install 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., "@NotifyMCPpublish a message 'Deployment finished successfully'"
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.
NotifyMCP
NotifyMCP is a small FastMCP server that lets an agent publish messages to a configured MQTT topic.
It is intended to pair with the NotifyMQTT Android app: an agent calls the MCP tool, NotifyMCP publishes to MQTT, and NotifyMQTT turns that MQTT message into a phone notification.
NotifyMCP can run either directly with uvx or as a Docker container pulled from Docker Hub.
Tools
publish_message
Publishes a message to the MQTT topic configured by environment variables.
Arguments:
message— message payload to publish.qos— MQTT QoS level, defaults to1.retain— whether to publish as a retained MQTT message, defaults tofalse.
get_mqtt_config
Returns the configured MQTT target without exposing the password.
Related MCP server: MQTT MCP Server
Environment variables
Required:
Variable | Description |
| Broker URL. Supports |
| Topic to publish all agent messages to. |
Optional:
Variable | Description |
| MQTT username. Leave blank for anonymous brokers. |
| MQTT password. Leave blank for anonymous brokers. |
| MQTT keepalive. Defaults to |
| Publish wait timeout. Defaults to |
mqtt:// and tcp:// default to port 1883. mqtts:// and ssl:// default to port 8883 and enable TLS.
Run with uvx from GitHub
You can run the MCP server directly from the GitHub repo with uvx:
export MQTT_URL="mqtt://192.168.1.10:1883"
export MQTT_USERNAME=""
export MQTT_PASSWORD=""
export MQTT_TOPIC="notify/test"
uvx --from git+https://github.com/mbush91/NotifyMCP notifymcpFor a fixed version, use a tag or commit:
uvx --from git+https://github.com/mbush91/NotifyMCP@v0.1.0 notifymcpRun from Docker Hub
After the Docker Hub publish workflow has run, pull and run the image:
docker pull <dockerhub-username>/notifymcp:latest
docker run --rm -i \
-e MQTT_URL="mqtt://192.168.1.10:1883" \
-e MQTT_USERNAME="" \
-e MQTT_PASSWORD="" \
-e MQTT_TOPIC="notify/test" \
<dockerhub-username>/notifymcp:latestThe container runs the MCP server over stdio, so keep -i when using it from an MCP host.
Docker Hub publishing
The Docker Hub Publish GitHub Actions workflow pushes images on:
pushes to
mainaslatestandsha-<commit>tags like
v0.1.0as semver Docker tagsmanual
workflow_dispatchruns
Configure these repository secrets in GitHub before publishing:
Secret | Description |
| Docker Hub username or organization. |
| Docker Hub access token. |
The image name will be:
DOCKERHUB_USERNAME/notifymcpExample MCP client config: uvx
{
"mcpServers": {
"notifymcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mbush91/NotifyMCP",
"notifymcp"
],
"env": {
"MQTT_URL": "mqtt://192.168.1.10:1883",
"MQTT_USERNAME": "",
"MQTT_PASSWORD": "",
"MQTT_TOPIC": "notify/test"
}
}
}
}Example MCP client config: Docker
{
"mcpServers": {
"notifymcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"MQTT_URL=mqtt://192.168.1.10:1883",
"-e",
"MQTT_USERNAME=",
"-e",
"MQTT_PASSWORD=",
"-e",
"MQTT_TOPIC=notify/test",
"<dockerhub-username>/notifymcp:latest"
]
}
}
}Local development
uv sync --extra dev
uv run ruff check .
uv run pytest
uv build
docker build -t notifymcp:local .You can also smoke-test the local checkout through uvx:
uvx --from . notifymcpMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceEnables 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
- FlicenseAqualityDmaintenanceEnables interacting with MQTT brokers to publish, subscribe, and manage connections, with a real-time web UI for visual feedback.61
- Flicense-qualityDmaintenanceProvides 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.
- FlicenseAqualityBmaintenanceEnables AI to send push notifications to your phone via a configurable gateway. It is a thin wrapper that posts to an Apprise push gateway.1
Related MCP Connectors
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Fire-and-forget webhooks for agents with guaranteed, retried delivery and status polling. x402
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mbush91/NotifyMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server