Trinity Lite vs Wiff

In-depth architectural comparison of the Trinity Lite and Wiff MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Trinity Lite when:

• You need dedicated capabilities in the Coding Agents domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Capability-based and direct task dispatch, SQLite persistence for tasks and results, MCP access through 14 tools and 3 resources.

Explore Trinity Lite Details

Choose Wiff when:

• You need dedicated capabilities in the Coding Agents domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: WIFF_BACKEND.
• Primary tools included: workflow_start, workflow_status, workflow_wait.

Feature & Specification Comparison

Specification	Trinity Lite Yomiracle Coding Agents	Wiff Coding Agents
Summary	Local-first task bus for CLI-based AI agents. Route work, persist state in SQLite, and let Codex, Claude Code, and other agents collaborate through a shared MCP server.	Deterministic, resumable multi-agent Codex workflows, drivable from any MCP client.
Category & Scope	Coding Agents

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "yomiracle-trinity-lite": {
      "command": "uvx",
      "args": [
        "trinity-lite"
      ]
    }
  }
}

{
  "mcpServers": {
    "wiff": {
      "command": "npx",
      "args": [
        "-y",
        "@xxxoooxoxo/wiff"
      ],
      "env": {
        "WIFF_BACKEND": "YOUR_WIFF_BACKEND_HERE"
      }
    }
  }
}

Related MCP Server Comparisons