A side-by-side look at the Muster and Working Machines MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Muster for aggregators work over a hosted endpoint; choose Working Machines for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Muster when
You need dedicated capabilities in the Aggregators domain.
No tool names declared yet. Check the project README from the listing page.
Working Machines tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Muster is categorized under Aggregators and uses a remote HTTP/SSE transport. Working Machines belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Muster for aggregators work and Working Machines for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Muster is listed as free. Auth: oauth 2.0. Working Machines has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add muster and working-machines-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Muster has a quality signal of 55/100 (Good) with 0 views, 0 installs and 39 GitHub stars. Working Machines has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.