Build on PlaybookOps

Connect your code and AI agents to your projects, tasks, knowledge, automations, apps, people and KPIs.

PlaybookOps has a REST API for your own code and an MCP server for AI agents. Both use the same API keys and offer the same actions, and a key can only reach what the person who made it can reach in the app.

Two ways in

The REST API is JSON over HTTPS at https://developers.playbookops.ai/v1. Use it for code with fixed steps: syncing items with another system, a webhook handler, a dashboard, a script that files tasks.

The MCP server at https://mcp.playbookops.ai offers the same actions as tools for AI agents. The agent reads each tool's description and decides what to call: "what's overdue on the launch board?" becomes list_projects, then list_items.

What you can reach

AreaReadChange
Projects and itemsProjects, groups, columns, items, updates, searchCreate, update, move and complete items; post updates
TasksYour tasks across projects and personal listsCreate personal tasks; update and complete your own
KnowledgePlaybooks, documents, search, who knows about a topicCreate documents in Markdown and patch them section by section
AutomationsAutomations, runs and their stepsStart automations that are started by hand
AppsApps you can open, their collections and Live recordsCreate and update records
People and KPIsPeople, job roles, KPIs and their values

Good to know

  • A key acts as you. It sees the projects you're on and the apps you can open, and its changes show up in the app as yours, with notifications and automations as usual. See API keys and scopes.
  • Admins stay in control. Org admins see every key in the organization, can revoke any of them, can turn the API off, and can see the organization's API and MCP traffic under Admin → API.
  • Most calls are free. Knowledge search and who knows use AI credits. Each key can make 120 requests a minute. See limits and credits.
  • Docs for models. Every page is available as Markdown, and /llms.txt lists them all for coding agents.