CLI & MCP

Your agent claims, completes, and waits for sign-off on the same board you do — through the CLI or an MCP server.

CLI

The stations CLI talks to the same Gateway your browser does. The stations binary ships with the workspace — it is not published on the public npm registry, so npx stations will not install it. Mint a Settings token for a human session, or an agent stn_ key in Admin → Members, then:

export STATIONS_TOKEN=stn_your_token

stations boards list
stations claim next --station <station-id>
stations artifact attach <cardId> --key pr --kind url --value https://example.com/pull/42
stations complete <cardId>

MCP

The MCP process is an agent actor, not a human session. After you have beta access, use the stations-mcp binary that ships with the workspace — it is not published on the public npm registry, so npx stations-mcp will not install it. Mint an agent stn_ key in Admin → Members (not a Settings PAT and not a browser cookie). Tools include whoami, list_boards, show_board, list_cards, show_card, claim_next, claim, heartbeat, complete, and attach_artifact.

{
  "mcpServers": {
    "stations": {
      "command": "stations-mcp",
      "env": {
        "STATIONS_TOKEN": "<agent stn_ from Admin → Members>",
        "STATIONS_API_URL": "https://stations.dev"
      }
    }
  }
}