mcp-zmq
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zmq_publishB | Publish a message to a ZMQ PUB socket. |
| zmq_subscribeB | Subscribe to messages from a ZMQ SUB socket. |
| zmq_send_requestC | Send a request via ZMQ REQ socket. |
| zmq_listen_replyA | Listen for requests and reply via ZMQ REP socket. |
| zmq_pair_connectB | Connect to a ZMQ PAIR socket for bi-directional communication. |
| zmq_pair_bindB | Bind a ZMQ PAIR socket for bi-directional communication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| zmq_status | Return ZMQ server status and capabilities. Returns: Dictionary with version, available socket types, and status. Example: >>> zmq_status() {"version": "0.1.0", "sockets": ["PUB", "SUB", "REQ", "REP", "PAIR"], "active": true} |
TDQS
Scored across 6 tools
Each tool targets a distinct ZMQ socket type or role (REP, PAIR bind/connect, PUB, REQ, SUB), with no overlap in purpose. Agents can clearly distinguish them.
All tools follow a consistent zmq_verb_noun pattern using snake_case, making the naming predictable and uniform across the set.
With 6 tools covering essential ZMQ socket types (REQ/REP, PUB/SUB, PAIR), the count is well-scoped and each tool serves a clear purpose.
The set covers fundamental ZMQ patterns but lacks support for PUSH/PULL, DEALER/ROUTER, and cleanup actions like disconnect. Minor gaps exist but core workflows are addressed.