Changelog

What's new in the PlaybookOps API and MCP server.

We add to /v1 without breaking it: new endpoints, new optional parameters and new fields in answers. Your code should ignore fields it doesn't know. Anything that would break existing code would come as /v2, announced here well ahead.

December 2026: playbooks as agent context

  • Create playbooks and folders: POST /v1/playbooks, and GET or POST /v1/playbooks/{id}/folders, so an import can rebuild a docs repo's structure.
  • What changed: GET /v1/document-changes returns documents created, changed, deleted or moved since a time, for keeping mirrors and indexes in step.
  • MCP resources: playbooks and documents can be attached as context at playbookops://playbooks/{id} and playbookops://documents/{id}.
  • Safe retries over MCP: tools that change things take an optional idempotency_key argument.
  • Custom keys: pick each area's access, like only reading and changing playbooks.
  • Cookbooks for using PlaybookOps as your agents' context, and Codex setup.
  • KPI values: record one with PUT /v1/kpis/{id}/values/{period} and clear it with DELETE, with the same rules as the scorecard.
  • Archive, restore and delete items: POST /v1/items/{id}/archive and /restore, DELETE /v1/items/{id}, and ?archived=true on an item list. Delete personal tasks with DELETE /v1/tasks/{id}. Over MCP, the deletes are marked destructive.
  • The MCP page moved to /agents/mcp.

December 2026: launch

The PlaybookOps API and MCP server are here.

  • Read projects, groups, columns, items and updates; your tasks; playbooks, documents, knowledge search and who knows; automations and runs; apps and Live records; people, job roles and KPIs.
  • Change items (create, update, move, complete) and post updates; create and complete personal tasks; create playbook documents in Markdown and patch them by section; start automations that are started by hand; create and update app records.
  • MCP at https://mcp.playbookops.ai, with the same actions as tools.
  • API keys under Account → API keys, with Read-only and Full access and an optional expiry.
  • For admins, Admin → API shows the organization's API and MCP usage, lists every key, and has a switch to turn the API off.