
Mcp Zmq
io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Oct 27, 2026
MCP server for ZMQ messaging
Overview
A local MCP server that gives an assistant tools to publish, subscribe, request/reply and pair over ZeroMQ sockets.
- What you can do
- Publish messages to a ZMQ PUB socket and subscribe to messages on a SUB socket
- Send requests over a REQ socket and listen for and answer requests on a REP socket
- Connect to or bind a ZMQ PAIR socket
- Report ZMQ server status
- When to use it
- Useful when an assistant needs to exchange messages with a ZeroMQ-based system, such as publishing events, consuming a message stream, or acting as a request/reply endpoint during local development or testing.
- Requirements
- Runs as a local process over stdio, installed from the PyPI package mcp-zmq (pip install mcp-zmq) and started with the mcp-zmq command. A Python environment is needed, plus reachable ZMQ endpoints to connect to or bind. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Mcp Zmq in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-zmq — MCP server for ZMQ messaging
[PyPI] [Python] [Coverage] [Ruff]
mcp-name: io.github.daedalus/mcp-zmq
Install
Usage
MCP Server
Python API
Available Tools
zmq_publish: Publish a message to a ZMQ PUB socketzmq_subscribe: Subscribe to messages from a ZMQ SUB socketzmq_send_request: Send a request via ZMQ REQ socketzmq_listen_reply: Listen for requests and reply via ZMQ REP socketzmq_pair_connect: Connect to a ZMQ PAIR socketzmq_pair_bind: Bind a ZMQ PAIR socketzmq_status: Get ZMQ server status
Development
Source: README.md at commit 5eacf52
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts