A side-by-side look at the Universal MCP Toolkit and Muster MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Universal MCP Toolkit for aggregators work as a local process; choose Muster 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 Universal MCP Toolkit when
You need dedicated capabilities in the Aggregators domain.
No tool names declared yet. Check the project README from the listing page.
Muster 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.
Universal MCP Toolkit is categorized under Aggregators and uses a local stdio subprocess. Muster belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Universal MCP Toolkit for aggregators work and Muster 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.
Universal MCP Toolkit is listed as free. Auth: api key required. Muster is listed as free. Auth: oauth 2.0. 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 markgatcha-universal-mcp-toolkit and muster as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Universal MCP Toolkit has a quality signal of 60/100 (Good) with 6 views, 0 installs and 15 GitHub stars. Muster has 55/100 (Good) with 0 views, 0 installs and 39 GitHub stars.