Give your agent the plan you see

Connect an agent to a database-backed Zeitlines deployment. It can inspect and change the plan through the same API the browser uses, with version checks on every write.

Planning context becomes structured input

Items, groups, dates, dependencies, status and metadata are records an agent can query. The agent receives the current plan records directly, so its work begins with the same state a person sees in the browser.

Reads and writes go to the live deployment

The MCP server requires the deployment URL. Database-backed timelines can be read and changed through that API. Writes carry the record version they started from, and stale writes are rejected by optimistic locking.

Core tools cover the plan

Agents can list timelines, read a complete timeline, and add, update or remove items and groups. Whole-plan replacement and the Product plugin model also have dedicated tools. The repository reference is the authoritative list as the interface develops.

Open the complete MCP tool reference.

Plugins can contribute focused verbs

Sprints can plan a sprint, roll unfinished work forward and report status. Lifecycle can date cutovers and check end-of-support risk. Construction can check trade conflicts and shift a dependent chain. These tools run where the supported plugin runtime exposes them; the MCP reference records the current transport limits.

Connect the server

claude mcp add -s user timelines -- \
  <repo>/node_modules/.bin/tsx <repo>/scripts/mcp/server.ts

Start with the documentation map or prepare a Postgres-backed deployment.