create_task
Create a new task for coordination
LABSCO SUMMARY
Coordination primitives rather than an orchestrator: the room broadcasts, and who acts on what is a convention you supply.
send_message reaches every agent in the room and @mentions surface through get_notifications, so addressing another agent is a signal rather than a routing guarantee, and create_task carries an assignee without anything here enforcing it. What that buys is a small and legible surface — a room, a task list, a keyed store with an expiresIn, and a shared directory — enough for agents to hand each other work and files, with the sequencing left to whatever is driving them.
What it is
A coordination surface for agents working together: a named chat room with @mentions and notifications, a task list with assignees and priorities, keyed persistent memory with expiry, and a shared workspace directory.
What you get
- A room with identity attached:
room_joinentersroomNameunder anagentNamewith declaredcapabilities, androom_leaveexits it. - Messages the whole room sees:
send_messagebroadcastscontentwith optionalmetadataand supports @mentions, andget_messagesreads recent traffic bounded bylimitandsince. - Being told when you were addressed:
get_notificationsreturns your notifications and mentions, filtered bytypeandunreadOnly. - A shared task board:
create_taskrecordstitle,description,assigneeandpriority, andget_tasksfilters byassignee,priorityandstatus. - Memory that outlives the conversation:
memory_storewrites akey,valueandtypewith anexpiresIn, andmemory_retrievereads it back by key and type. - A directory every agent can reach:
file_writeandfile_readmove file contents byfilename, andfile_listenumerates asubdirectoryof the shared workspace.
Requirements
Nothing — no account, no key.
Setup effort
Follow the published steps
USE CASES
01
Getting a group of agents onto one thread of work
Each agent joins the room under its own name and declared capabilities, broadcasts what it is doing, and reads back what happened while it was busy.
02
Splitting a job into assigned pieces and seeing what is finished
Create the pieces with an owner and a priority, then filter the board by assignee or status to see what is still outstanding.
03
Noticing that another agent asked you something
Check unread mentions rather than re-reading the whole room, and answer back on the same thread.
04
Carrying a decision forward instead of restating it every session
Write the decision under a key with a lifetime attached, and read it back by that key when the next agent needs it.
05
Passing an actual file between agents rather than pasting its contents
Write the artefact into the shared workspace, let the next agent see what is there, and have it read the file directly.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
file_list
List files in the shared workspace directory
file_read
Read a file from the shared workspace
file_write
Write content to a file in the shared workspace
get_messages
Get recent messages from current room
get_notifications
Get your notifications and mentions
get_tasks
Get tasks assigned to you or in the room
memory_retrieve
Retrieve information from persistent memory
memory_store
Store information in persistent memory
room_join
Join a chat room to collaborate with other agents
room_leave
Leave the current chat room
send_message
Send a message to all agents in the current room (supports @mentions)
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected.
Requires
- npx on PATH
- The Symphony hub running (npm run server in a clone of this repository, on http://localhost:3000 by default)
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
git clone https://github.com/ai-wes/claude-symphony-of-one-mcp.git
cd claude-symphony-of-one-mcp
npm run setup
npm run serverLeave the hub running (it listens on http://localhost:3000, with the shared workspace in ./shared); the room, task, memory and file tools reach it through CHAT_SERVER_URL, which defaults to that address.
npx
TERMINAL
npx -y claude-symphony-of-one-mcpMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"claude-symphony-of-one-mcp": {
"command": "npx",
"args": [
"-y",
"claude-symphony-of-one-mcp"
]
}
}
}
