Install walkthrough

1 · Install it

One member, no dependency closure.

tctl install trusty-memory

cargo install trusty-memory --locked

The second line is the escape hatch: it pulls the published crates.io release directly, which is also what tctl falls back to off a prebuilt platform.

The Svelte UI ships pre-built inside the crate, so this never runs pnpm.

2 · Find the port it serves on

The daemon picks its port at startup and reports it back. The UI is on the same port, on loopback.

trusty-memory port

3 · Register it as an MCP server

Add the entry to your .mcp.json. The command and args are what the crate’s own CLI parses.

{
  "mcpServers": {
    "trusty-memory": {
      "command": "trusty-memory",
      "args": ["serve","--stdio"]
    }
  }
}

1 · Install it

One member, no dependency closure.

tctl install trusty-search

cargo install trusty-search --locked

The Svelte UI ships pre-built inside the crate, so this never runs pnpm.

2 · Start the daemon and read its port

First start downloads the embedding model, which is what the ~2 GB of disk is for.

trusty-search start

trusty-search port

3 · Register it as an MCP server

Add the entry to your .mcp.json.

{
  "mcpServers": {
    "trusty-search": {
      "command": "trusty-search",
      "args": ["serve"]
    }
  }
}

1 · Install both

There is no dependency edge between them, so the order does not matter and they can be installed in parallel.

tctl install trusty-search trusty-memory

cargo install trusty-search --locked
cargo install trusty-memory --locked

What the two share is a library, not a process: both link the same embedder out of trusty-common. Neither daemon talks to the other over the network.

2 · Register both MCP servers

Two independent entries in the same .mcp.json — each keeps the command and args from its own section.

{
  "mcpServers": {
    "trusty-search": {
      "command": "trusty-search",
      "args": ["serve"]
    },
    "trusty-memory": {
      "command": "trusty-memory",
      "args": ["serve", "--stdio"]
    }
  }
}

1 · Install it

One member, no dependency closure.

tctl install trusty-analyze

cargo install trusty-analyze --locked

The Svelte UI ships pre-built inside the crate, so this never runs pnpm.

2 · Register it as an MCP server

Add the entry to your .mcp.json. Both args are required — the crate generates exactly this pair itself.

{
  "mcpServers": {
    "trusty-analyze": {
      "command": "trusty-analyze",
      "args": ["serve","--mcp"]
    }
  }
}

1 · Install it, and what it needs

One tctl line installs three members. The cargo path installs one, so bring up trusty-search and trusty-analyze first if you take it.

tctl install trusty-review

cargo install trusty-review --locked

trusty-review checks for both before it starts a review and skips the review entirely if either is unreachable, absent an explicit degraded-mode opt-in.

Install order does not matter under tctl: it resolves the closure and orders it topologically.

2 · Point it at a model

Set the provider key from the prerequisites above before the first review — this is the one product that will not run without it.

3 · Register it as an MCP server

Add the entry to your .mcp.json.

{
  "mcpServers": {
    "trusty-review": {
      "command": "trusty-review",
      "args": ["mcp"]
    }
  }
}

["serve", "--stdio"] still parses as an alias, so an older .mcp.json keeps working. ["mcp"] is the current spelling to write.

1 · Install it, and check what landed

One line installs three binaries. tctl status prints what it manages and what is running.

tctl install trusty-mpm
tctl status

cargo install trusty-mpm --locked

The crate ships two binaries, tm and trusty-mpm, from the same source — either name drives it.

2 · Know where its config lives

Configuration is TOML at ~/.config/trusty-mpm/config.toml, honouring $XDG_CONFIG_HOME when you set it.

Two older docs point at a config.yaml and at a trusty-mpmd binary. Neither exists: the file is TOML, and the daemon runs in-process as a mode of tm itself.

3 · Run the daemon

tm owns its own lifecycle rather than handing it to launchd.

tm start

tm stop and tm restart are the other two halves of the same verb set.

1 · Install it from crates.io

The published crate, direct. There is no prebuilt tarball and no tctl membership.

cargo install trusty-code --locked

trusty-code has no Svelte build step, so pnpm is not involved at any point.

Its README points at a GitHub release tag that has never existed — an unreplaced template placeholder. Use the line above.

2 · Run one process per project

The harness is scoped to a project’s .claude/ root, so it is one running process per project rather than one per machine.

tcode serve

1 · Clone and build it

This is the same cargo install --path form the project’s own signed-install script uses.

git clone https://github.com/bobmatnyc/trusty-tools
cd trusty-tools
cargo install --path crates/trusty-agents --locked

tctl install trusty-agents fails — it is not a stable-set member. Older docs naming an open-mpm repository or crate are wrong; neither has ever existed.

2 · Supply one credential, or none

Each credential resolves from the environment, then a project or user .env.local, then the store tagent config keys set writes to. A run against Bedrock or a local Ollama model needs none of the three.

3 · Register it as an MCP server

tagent exposes itself to other MCP clients over stdio.

{
  "mcpServers": {
    "trusty-agents": {
      "command": "tagent",
      "args": ["mcp-serve"]
    }
  }
}

1 · Install it

The package is named tga even though its directory is crates/trusty-git-analytics.

tctl install tga

cargo install tga --locked

Do not copy a built binary onto your PATH by hand. tga’s own user guide still shows a cp and an mv into /usr/local/bin; on macOS that leaves a stale kernel signature cache and the next run is killed in a way that looks like an out-of-memory kill. cargo install renames atomically instead.

2 · Point it at a config file

One global flag, -c or --config, on every subcommand. It defaults to config.yaml resolved against your current directory.

There is no ~/.config/tga/ fallback and no environment-variable override, whatever INSTALL-CONVENTION.md says.

tga has no MCP transport at all — nothing to register, by design.