trinity-onboard: Plugin MCP fails silently when TRINITY_URL/TRINITY_API_KEY env vars are not set

[pandore]

Problem

The trinity-onboard plugin's .mcp.json references ${TRINITY_URL} and ${TRINITY_API_KEY} environment variables:

{
  "mcpServers": {
    "trinity": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "${TRINITY_URL}/mcp"],
      "env": {
        "API_KEY": "${TRINITY_API_KEY}"
      }
    }
  }
}

When the plugin is enabled, Claude Code immediately tries to start this MCP server. If the env vars aren't set (which is the default state after installing the plugin), the server fails to connect silently — claude mcp list shows plugin:trinity-onboard:trinity: ✗ Failed to connect with no helpful error message.

Expected Behavior

Either:

1. The README should document that TRINITY_URL and TRINITY_API_KEY must be added to ~/.claude/.env before enabling the plugin, or
2. The plugin should gracefully handle missing env vars (e.g., skip MCP registration until onboarding is complete), or
3. The /trinity-onboard skill should write these values to ~/.claude/.env as part of setup

Current Workaround

Manually add to ~/.claude/.env:

TRINITY_URL=http://your-trinity-instance:8080
TRINITY_API_KEY=your_api_key_here

Environment

• Claude Code 2.1.87
• macOS