CollabMCP
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sessionA | Snapshot of the team's shared context: your scope, who else is active, recent decisions, active locks, and any inbox messages. Call this at the start of every session. |
| who_ownsA | Check whether a file or directory belongs to another dev's scope before editing it. Returns the owner and whether you can proceed. |
| rememberA | Record an architectural decision, a non-obvious bug fix, or anything teammates should know. Append-only and shared with the team. |
| recallB | Search prior team decisions before making an important choice, to check if something was already resolved. |
| broadcastA | Send a message to every active teammate — breaking changes, interface changes, or coordination requests. |
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 5 tools
Each tool has a clearly distinct purpose: broadcast for messaging, get_session for context snapshot, recall for reading past decisions, remember for writing decisions, who_owns for ownership queries. No overlap.
Naming is mixed: 'broadcast', 'recall', 'remember' are single verbs; 'get_session' is verb_noun; 'who_owns' is a question. No consistent pattern, though all are readable.
With 5 tools covering communication, session management, knowledge base, and ownership, the count is well-scoped for a team collaboration server.
Covers key collaboration features (messaging, context, decisions, ownership). Minor gap: no explicit lock acquisition/release tool, but get_session and who_owns may suffice.