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
| Tool | Purpose |
|---|---|
start_time | Start an explicitly requested owned session and return its exact ID. |
heartbeat_time | Renew the lease before it expires. |
pause_time | Pause while the agent is waiting and close the current timer segment. |
resume_time | Resume the same session with a new standard timer. |
stop_time | Stop one owned session without affecting other timers. |
list_time_sessions | List sessions and reconcile expired leases. |
report_agent_time | Report durations by client, project, or session status. |
recover_time_sessions | Close timers whose agent lease expired. |
burrowtime_capabilities | Read the supported protocol and feature flags. |
Expected client behavior
- Call
burrowtime_capabilitiesand require agent protocol 1. - Start only after the user explicitly asks and provides a project plus task.
- Retain the returned session ID and use it for every later write.
- Renew the lease during long work and pause before waiting for required input.
- 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 --jsonThe 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.