Claude Symphony Of One MCP Server

Symphony of One MCP - enables multi-agent collaboration through centralized chat rooms with persistent memory and tagging

Local serverstdio

What is the Claude Symphony Of One MCP MCP server?

Symphony of One MCP - enables multi-agent collaboration through centralized chat rooms with persistent memory and tagging. The claude symphony of one mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

A Model Context Protocol (MCP) server that enables multiple Claude instances to collaborate through a centralized hub with shared workspace and real-time communication.

Its toolset

Everything the assistant can do here goes through one of these:

  • Orchestration — The Orchestration tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 3 environment variables: CHAT_SERVER_URL, SHARED_DIR, AGENT_NAME. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Claude Symphony Of One MCP's toolset — Orchestration — is a fair guide to whether it matches your workflow. It is maintained by ai-wes; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the claude symphony of one mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
OrchestrationThe Orchestration tool exposed by this server.

How to install the Claude Symphony Of One MCP MCP server

**For Claude Code (WSL):**

```json
{
  "mcpServers": {
    "claude-symphony-of-one": {
      "command": "node",
      "args": ["/mnt/c/path/to/your/project/mcp-server-wrapper.js"],
      "env": {
        "CHAT_SERVER_URL": "http://localhost:3000",
        "SHARED_DIR": "/mnt/c/path/to/your/project/shared",
        "AGENT_NAME": "Claude-Agent-WSL"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CHAT_SERVER_URLEndpoint or connection string the server talks to.Yes
SHARED_DIRFilesystem location the server is allowed to use.Optional
AGENT_NAMEConfiguration value read at startup.Optional

Example prompts to try

  • Use Claude Symphony Of One MCP to Orchestration.

Frequently asked questions

It connects Claude Symphony Of One MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Orchestration) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Claude Symphony Of One MCP directly.