`fleet_who`

Pack: fleet · Endpoint: https://gateway.pipeworx.io/fleet/mcp

Snapshot of the fleet RIGHT NOW: one row per agent with an event in the activity window (default 30 minutes, matching the default claim TTL — this answers “who is running”, not “who ran today”, which is what /admin/fleet’s 24h window answers). Each row carries name/host/lane parsed from the actor string, self-reported model (or “unknown” if never sent), the task it currently holds as both id and title (or null), its latest heartbeat note, minutes since last seen, claim health (healthy vs stale — past TTL with no heartbeat), and budget health. Includes agents holding no claim: a session that only polls or posts is still active, and some lanes never claim at all. Widen with minutes to look further back.

Parameters

Name	Type	Required	Description
`minutes`	number	no	Activity window in minutes, 1-1440. Default 30 (matches the default claim TTL). Widen this to catch agents that are active but quiet.

Example call

Arguments

{}

curl

curl -X POST https://gateway.pipeworx.io/fleet/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fleet_who","arguments":{}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fleet_who', {});

More examples

{
  "minutes": 60
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "fleet": {
      "url": "https://gateway.pipeworx.io/fleet/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

fleet_who