connect

name	connect
description	Connect to a Trinity instance and configure MCP server. Authenticates via email OTP, provisions an MCP API key, and writes `.mcp.json` — no CLI installation required.
disable-model-invocation	false
user-invocable	true
allowed-tools	Read, Write, Edit, Bash, AskUserQuestion
metadata	{"version":"1.3","created":"2026-05-27T00:00:00.000Z","author":"Ability.ai","changelog":["1.3: Next steps carry the deploy sequence — add the instance GitHub token (Settings → GitHub token) before /trinity:onboard, which deploys an agent from its GitHub repo","1.2: Explain the silent no-code failure mode — email OTP only reaches whitelisted addresses and the API 200s identically for unknown ones (anti-enumeration #186); self-signup is default-OFF (#1274) — so guide users to admin whitelisting instead of resend loops","1.1: Idempotent reconnect (PHASE 0) — when a valid profile already exists, (re)write `.mcp.json` in the current directory from the stored profile without an email round-trip, instead of just reporting 'already connected'. connect is now the single writer of `.mcp.json` that /trinity:onboard, /trinity:sync, and /trinity:loop delegate to","1.0: Initial version — connect to a Trinity instance via email OTP, provision an MCP API key, and write .mcp.json, with no CLI installation required"]}

/trinity:connect

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. connect vX.Y — recent: <summary>. Then proceed.

Connect to a Trinity instance and configure MCP server. No CLI installation required.

Trigger

User wants to:

• Connect to Trinity for the first time
• Set up Trinity MCP integration
• Authenticate with a Trinity instance
• "connect to trinity", "trinity login", "set up trinity"

Flow

PHASE 0: Check Existing Connection

Check if already connected:

cat ~/.trinity/config.json 2>/dev/null | jq -r '.current_profile // empty'

If a profile exists, check if it's still valid:

• Read the current profile's instance_url and token
• Test connection: curl -s -o /dev/null -w "%{http_code}" -H "Authorization: Bearer {token}" {instance_url}/api/users/me
• If 200 (profile valid): ensure .mcp.json in the current directory is present and correct before reporting done. /trinity:connect is the single writer of .mcp.json — /trinity:onboard, /trinity:sync, and /trinity:loop delegate here rather than writing it themselves, so a valid profile must still (re)materialize the file for the current agent directory:
  • Derive the MCP URL and write the trinity server block from the stored profile's instance_url + mcp_api_key, exactly as in PHASE 6 — no email round-trip needed. If the file was already present and identical, leave it.
  • Report: "Already connected to {instance_url}. .mcp.json [written / refreshed / already current]. Reconnect with /mcp if it just changed. Run /trinity:connect --force to re-authenticate or switch instances." Then skip to PHASE 7 (verify) — do not re-run the email flow.
• If not 200: Continue with flow (token expired)

PHASE 1: Get Instance URL

Ask: "What's your Trinity instance URL?"

Examples: