Trinity

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

1. 1

   Download / install

   Publisher instructions

   Self-host Trinity first; then connect to its MCP HTTP endpoint using an API key created in Trinity Settings. Do not confuse the trinity-cli package with the server stack.

   Advanced configuration · self hosted install or run

   self hosted install or run · Review before use

   git clone https://github.com/abilityai/trinity.git
   cd trinity
   cp .env.example .env

   Advanced configuration · self hosted start

   self hosted start · Review before use

   ./scripts/deploy/build-base-image.sh
   ./scripts/deploy/start.sh

2. 2

   Configure application / integrations

   Publisher instructions

   Set ADMIN_PASSWORD (publisher requires 12+ characters) in .env and satisfy Docker/runtime prerequisites. First-run web UI at http://localhost. In Settings → MCP Keys create an MCP API key. Configure HTTP MCP endpoint http://localhost:8080/mcp for local installations, or https://your-domain.com/mcp behind the production proxy. Publisher Claude Code JSON uses mcpServers.trinity.type=http and an Authorization Bearer header. Never put a real API key in committed repository config.

   Advanced configuration · claude code json

   {
     "mcpServers": {
       "trinity": {
         "headers": {
           "Authorization": "Bearer REPLACE_WITH_TRINITY_MCP_KEY"
         },
         "type": "http",
         "url": "http://localhost:8080/mcp"
       }
     }
   }

   Copy
3. 3

   Check connection

   Suggested check

   Check the deployed Trinity control UI Settings > MCP Keys, the appropriate /mcp URL, authentication scope and client-discovered tools. A configured JSON alone does not demonstrate remote key validity. Do not run create/stop/delete agent operations for smoke testing. Client registration check: `claude mcp get trinity` (checks registration; inspect tools/read-only calls separately to verify authenticated service access).

4. 4

   Disconnect / uninstall / revoke

   MCP100 setup guide

   For a local Trinity installation run `./scripts/deploy/stop.sh` from the checkout to stop services without removing agent-network containers. The publisher explicitly warns against routine `docker compose down`. Separately disconnect client config and revoke Trinity MCP key via Settings → MCP Keys if access should end; do not assume stopping stack revokes keys or removes persistent data. Client disconnect (claude-code, only if registered using the name `trinity`): `claude mcp remove trinity`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.

   To revoke the Trinity MCP key, use Trinity Settings → MCP Keys to deactivate/revoke the key used for this connection. Revocation is separate from stopping the stack or deleting a client entry.

   claude mcp remove trinity

   Copy