mcp-agent-collaboration
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AGENT_COLLAB_LOG | No | Log file path for the agent collaboration server | /tmp/mcp-agent-collaboration.log |
| MCP_AGENT_COLLAB_HOST | No | Host address for the agent collaboration server | 127.0.0.1 |
| MCP_AGENT_COLLAB_PATH | No | Path for the MCP endpoint | /mcp |
| MCP_AGENT_COLLAB_PORT | No | Port for the agent collaboration server | 8000 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_topicB | Create a collaboration topic by name. |
| join_topicC | Join a topic with a friendly agent name and receive a join_token. |
| leave_topicC | Leave the joined topic. |
| send_messageB | Send a direct or broadcast message in the joined topic. |
| read_messagesA | Long-poll, read, and consume pending messages for the joined agent. |
| check_inC | Optionally send a message, then read pending messages in one tool call. |
| list_topicsA | List topics with member counts and pending in-memory message counts. |
| list_topic_membersB | List active members in a topic. |
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
Each tool has a clearly distinct purpose: topic lifecycle (create, join, leave), messaging (send, read, check_in), and listing (topics, members). check_in is a convenience combination but its description clarifies its dual role.
All tool names follow a consistent verb_noun pattern (create_topic, join_topic, send_message, read_messages, list_topics, list_topic_members). Minor phrasal verb 'check_in' still fits the style.
Eight tools cover the domain of topic-based collaboration without redundancy or bloat. Each tool serves a distinct function and the count is well within the ideal range.
The surface covers topic creation, joining/leaving, messaging, and listing topics/members. A delete_topic operation is missing but might be intentionally omitted for ephemeral in-memory topics, so minor gap only.