A side-by-side look at the Rhizome MCP and Trinity Lite MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Rhizome MCP for coding agents work as a local process; choose Trinity Lite for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Rhizome MCP when
You need dedicated capabilities in the Coding Agents domain.
No tool names declared yet. Check the project README from the listing page.
Trinity Lite 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.
Rhizome MCP is categorized under Coding Agents and uses a local stdio subprocess. Trinity Lite belongs to Coding Agents and uses a local stdio subprocess. Pick Rhizome MCP for coding agents work and Trinity Lite for coding agents.
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.
Rhizome MCP has no declared pricing — check the project's own site. Trinity Lite 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 rhizome-mcp and yomiracle-trinity-lite as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rhizome MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Trinity Lite has 49/100 (Fair) with 1 views, 0 installs and 5 GitHub stars.