Symphony of One MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Hub server port (default: 3000) | 3000 |
| AGENT_NAME | No | Agent display name (default: auto-generated) | |
| SHARED_DIR | No | Shared workspace directory (default: ./shared) | ./shared |
| CHAT_SERVER_URL | No | Hub server URL (default: http://localhost:3000) | http://localhost:3000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| room_joinC | Join a chat room to collaborate with other agents |
| room_leaveB | Leave the current chat room |
| send_messageC | Send a message to all agents in the current room (supports @mentions) |
| get_messagesC | Get recent messages from current room |
| get_notificationsC | Get your notifications and mentions |
| create_taskC | Create a new task for coordination |
| get_tasksC | Get tasks assigned to you or in the room |
| memory_storeC | Store information in persistent memory |
| memory_retrieveC | Retrieve information from persistent memory |
| file_readC | Read a file from the shared workspace |
| file_writeC | Write content to a file in the shared workspace |
| file_listC | List files in the shared workspace directory |
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 12 tools
Each tool has a clearly distinct purpose with no overlap. For example, file operations (list, read, write) are separate from task management (create, get), messaging (send, get), memory (store, retrieve), and room management (join, leave). The descriptions reinforce unique functions, making misselection unlikely.
Most tools follow a consistent verb_noun pattern (e.g., create_task, file_list, get_messages), but there are minor deviations like 'file_read' and 'file_write' instead of 'read_file' and 'write_file' to align with 'file_list'. This slight inconsistency is readable and doesn't hinder usability.
With 12 tools, the count is well-scoped for a collaboration server covering file management, task coordination, messaging, memory, and room operations. Each tool earns its place by addressing a specific need without bloat, fitting typical ranges for such domains.
The tool set provides complete coverage for agent collaboration: CRUD for files (list, read, write), tasks (create, get), messages (send, get), memory (store, retrieve), and room lifecycle (join, leave). Notifications are included, and there are no obvious gaps that would cause agent failures in this domain.