BurrowTime docs

MCP server

Connect BurrowTime to an MCP client for owned agent timers, lease renewal, pause and resume, recovery, and reporting.

Configure the server

BurrowTime includes a local Model Context Protocol server over standard input and output. Configure your MCP client to launch the installed command:

{
  "mcpServers": {
    "burrowtime": {
      "command": "burrowtime",
      "args": ["mcp"]
    }
  }
}

No port, API key, account, or remote service is involved.

Available tools

ToolPurpose
start_timeStart an explicitly requested owned session and return its exact ID.
heartbeat_timeRenew the lease before it expires.
pause_timePause while the agent is waiting and close the current timer segment.
resume_timeResume the same session with a new standard timer.
stop_timeStop one owned session without affecting other timers.
list_time_sessionsList sessions and reconcile expired leases.
report_agent_timeReport durations by client, project, or session status.
recover_time_sessionsClose timers whose agent lease expired.
burrowtime_capabilitiesRead the supported protocol and feature flags.

Expected client behavior

  1. Call burrowtime_capabilities and require agent protocol 1.
  2. Start only after the user explicitly asks and provides a project plus task.
  3. Retain the returned session ID and use it for every later write.
  4. Renew the lease during long work and pause before waiting for required input.
  5. Stop the exact session before returning the final answer.

Do not fall back to a bare stop. An integration must never run burrowtime stop or burrowtime stop --all on an agent's behalf. Those commands can affect timers the integration does not own.

Capability check

burrowtime capabilities --json

The result reports the agent protocol, MCP protocol, installed feature flags, supported skill targets, and session states. This lets a client fail clearly when the binary is older than its integration.