Download all docs

The Triform MCP server

triform-mcp exposes the Triform platform to MCP-capable agents (Claude Code, and any MCP client) as a compact set of tools. It speaks JSON-RPC 2.0 over stdin/stdout and delegates dispatch to the same consolidated tool surface as the triton CLI — so the tools an agent sees over MCP are exactly the tools you can script from the command line.

Install

The MCP server ships alongside the CLI. One command installs both into ~/.triform/bin:

curl -fsSL https://triform.cloud/downloads/install.sh | sh

See the CLI guide for OS/arch coverage and options.

Register it with Claude Code

claude mcp add triform \
  --env TRIFORM_API_URL=https://triform.cloud \
  --env TRIFORM_API_KEY=trif_your_token \
  -- "$HOME/.triform/bin/triform-mcp"

This registers a stdio MCP server. Tools then surface in Claude Code as <element_type>.<op> (e.g. python.invoke, sql.query). Use a trif_ token minted from an api-token element in your circle (see Authentication & access).

If you have already run triton auth login, you can omit the --env flags — the server reuses the CLI’s resolved credentials from ~/.triform/credentials:

claude mcp add triform -- "$HOME/.triform/bin/triform-mcp"

Tool modes

By default the server exposes the consolidated tool catalog (a small set of high-level tools, each taking an action argument). Set TRIFORM_MCP_TOOL_MODE=generated to switch to the full per-element granular tool set instead.

Credentials

The MCP server reuses the CLI’s credential resolution — authenticate once with triton auth login (or triton auth set-api-key), or pass TRIFORM_API_URL + TRIFORM_API_KEY directly as in the registration command above.

Related