MCP Talk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TALK_QUEUE | No | Message queue directory | ~/.mcp_talk/q/ |
| MCP_TALK_AUTO_CLEAN_HOURS | No | Auto-delete messages older than N hours (0 to disable) | 24 |
| MCP_TALK_MAX_MESSAGE_CHARS | No | Maximum message length | 2000 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sendC | Send a message to another agent. Usage: send(to='claude', message='Hello!', namespace='myproject') |
| chkC | Check messages for an agent (shortcut). Usage: chk(agent='claude', namespace='myproject') |
| checkC | Check messages for an agent. Usage: check(agent='claude', namespace='myproject') |
| ackB | Acknowledge/delete a message after processing. Usage: ack(id='msg_id', namespace='myproject') |
| broadcastC | Send a message to all agents. Usage: broadcast(message='Team update', namespace='myproject') |
| listC | List all pending messages in the queue (PM visibility). Usage: list(namespace='myproject') |
| cleanC | Clean up old messages. Usage: clean(hours=24, namespace='myproject') |
| replyB | Reply to a message (acks original and sends response to sender). Usage: reply(id='msg_id', message='Got it!', namespace='myproject') |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Multiple tools have unclear boundaries and overlapping purposes. 'check' and 'chk' are explicitly redundant shortcuts for the same function, while 'ack', 'reply', and 'send' all involve message handling with potential confusion about when to use each. The descriptions help somewhat, but the overlap is significant.
Naming is inconsistent with mixed conventions. Most tools use short, imperative verbs (ack, broadcast, check, clean, list, reply, send), but 'chk' is an abbreviation that breaks this pattern. There's no consistent verb_noun structure, and the naming feels chaotic rather than following a predictable scheme.
With 8 tools, the count is reasonable for a messaging/queue management server. It's well-scoped for core operations like sending, receiving, acknowledging, and cleaning messages. The redundancy of 'check' and 'chk' slightly bloats it, but overall, the number of tools is appropriate for the domain.
The tool surface covers the essential messaging lifecycle well: sending (send, broadcast), receiving (check, chk, list), responding (reply), and cleanup (ack, clean). Minor gaps might include operations like message prioritization or filtering, but agents can likely work around these with the provided tools for basic workflows.