メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Abilityai/abilities --skill connectコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Generate an agent-specific `/update-dashboard` skill that keeps `dashboard.yaml` current for Trinity. Analyzes the agent's purpose and data sources, proposes metrics, gets user approval, then scaffolds a schedulable skill.
Modify an existing playbook based on conversation context or explicit instructions. Use when user wants to update, fix, extend, or refine a playbook they already have.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
| 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"]} |
ℹ️ 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.changelogabove — e.g.connect vX.Y — recent: <summary>. Then proceed.
Connect to a Trinity instance and configure MCP server. No CLI installation required.
User wants to:
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:
curl -s -o /dev/null -w "%{http_code}" -H "Authorization: Bearer {token}" {instance_url}/api/users/me.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:
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..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.Ask: "What's your Trinity instance URL?"
Examples:
https://demo.abilityai.devhttps://yourcompany.abilityai.devhttps://trinity.yourcompany.com (self-hosted)If user doesn't have one:
Validate URL:
https:// if no scheme providedcurl -s -o /dev/null -w "%{http_code}" {url}/api/auth/modeStore: INSTANCE_URL
Ask: "What email should we use to authenticate?"
Send verification code:
curl -s -X POST "{INSTANCE_URL}/api/auth/email/request" \
-H "Content-Type: application/json" \
-d '{"email": "{EMAIL}"}'
Expected: 200 OK (empty response or {"status": "sent"})
If error:
Tell user: "Verification code sent to {EMAIL}. Check your inbox (and spam folder)."
If no code arrives within ~2 minutes: the most likely cause is that {EMAIL} is not on the instance's whitelist — the API deliberately returns the same 200 for unknown emails (anti-enumeration, trinity#186), so a missing email is the only signal. The fix is admin-side: an instance admin adds the email to the whitelist, or the operator enables self-signup (PUBLIC_ACCESS_REQUESTS_ENABLED, default OFF since trinity#1274 — POST /api/access/request returns 403 until it's opted in). Tell the user exactly that instead of looping on resend.
Ask: "Enter the 6-digit code from your email:"
Verify code and get token:
curl -s -X POST "{INSTANCE_URL}/api/auth/email/verify" \
-H "Content-Type: application/json" \
-d '{"email": "{EMAIL}", "code": "{CODE}"}'
Expected response:
{
"access_token": "eyJ...",
"user": {
"email": "user@example.com",
"username": "user@example.com",
"role": "user"
}
}
If error:
Store: ACCESS_TOKEN, USER
Get MCP API key (separate from JWT, longer-lived):
curl -s -X POST "{INSTANCE_URL}/api/mcp/keys/ensure-default" \
-H "Authorization: Bearer {ACCESS_TOKEN}" \
-H "Content-Type: application/json"
Expected response:
{
"api_key": "trinity_mcp_..."
}
Store: MCP_API_KEY
Derive profile name from hostname (e.g., demo.abilityai.dev).
Read existing config or create new:
mkdir -p ~/.trinity
chmod 700 ~/.trinity
Update config structure:
{
"current_profile": "{PROFILE_NAME}",
"profiles": {
"{PROFILE_NAME}": {
"instance_url": "{INSTANCE_URL}",
"token": "{ACCESS_TOKEN}",
"user": {
"email": "{USER.email}",
"username": "{USER.username}",
"role": "{USER.role}"
},
"mcp_api_key": "{MCP_API_KEY}"
}
}
}
If config exists, merge the new profile (don't overwrite other profiles).
Set permissions:
chmod 600 ~/.trinity/config.json
Derive MCP endpoint URL:
:8000, replace with :8080:8080 to hostname/mcp pathExample: https://demo.abilityai.dev → https://demo.abilityai.dev:8080/mcp
Read existing .mcp.json in current directory or create new.
Add/update trinity server config:
{
"mcpServers": {
"trinity": {
"type": "streamable-http",
"url": "{MCP_URL}",
"headers": {
"Authorization": "Bearer {MCP_API_KEY}"
}
}
}
}
Add .mcp.json to .gitignore if in a git repo (contains API key).
Test the connection:
curl -s -H "Authorization: Bearer {MCP_API_KEY}" "{MCP_URL}" -X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "method": "tools/list", "id": 1}'
Report success:
Connected to Trinity at {INSTANCE_URL}
Profile: {PROFILE_NAME}
User: {USER.email} ({USER.role})
MCP: Configured in .mcp.json
Next steps:
1. Restart Claude Code to load the MCP server
2. Add your GitHub token on the instance (Settings → GitHub token — fine-grained
PAT, Contents: Read). Agents deploy by cloning their GitHub repo; private
repos need this, public repos don't.
3. Run /trinity:onboard from an agent directory to deploy it from its repo
4. Use mcp__trinity__list_agents to see your agents
| Error | Response |
|---|---|
| Instance unreachable | "Cannot reach {URL}. Check the URL and your network connection." |
| Email not sent | "Failed to send verification email. Is this email registered on this Trinity instance?" |
| Invalid code | "Code invalid or expired. Would you like a new code?" |
| MCP key failed | "Logged in but couldn't provision MCP key. You can still use the Trinity CLI." |
| Config write failed | "Couldn't write to ~/.trinity/config.json. Check permissions." |
~/.trinity/config.jsonexp claim) but MCP API key is long-lived