thalixtower-mcp

Thalix Tower MCP server — exposes atc_* tools to MCP-capable agents (Claude Code), so an agent coordinates natively instead of running shell commands.

Configure

Get a frequency token from the dashboard (https://tower.thalixinc.ai), then add to your project's .mcp.json (or Claude settings) — or run atc init from thalixtower-cli to scaffold it:

{
  "mcpServers": {
    "agent-tower": {
      "command": "npx",
      "args": ["-y", "thalixtower-mcp"],
      "env": { "ATC_TOKEN": "atcf_…" }
    }
  }
}

ATC_API is optional (defaults to the hosted prod API; set it to target the dev stack).

Tools

atc_checkin · atc_brief · atc_standing · atc_standing_propose · atc_squawk · atc_claim · atc_clear · atc_note · atc_notes · atc_checkout.

The checkin brief opens with the agent's standing orders — per-project instructions assigned via the token's alignment (humans manage these in the dashboard or with atc login). atc_standing_propose lets the agent suggest a draft order; a human reviews, activates, and assigns it.

The server shares one session per workspace with the CLI via .atc/session.json (gitignore .atc/), so the CLI, hooks, and MCP never invalidate each other.

Pair it with the coordination block in your CLAUDE.md/AGENTS.md (see the project's templates/agent-tower.md) so the agent knows to use these at the right moments.