Integrations
CardBoard is the planning surface; your tracker owns execution. Do the thinking on a board, then sync the committed work to Azure DevOps or Jira — without re-typing a thing.
Trackers
Section titled “Trackers”Link a card to a tracker item and its work-item fields — title, status, description, acceptance criteria, parent, and assignee — mirror both ways. Position, color, outcomes, and reactions stay in CardBoard — the tracker has no equivalent. Tracker sync is included on every plan, including Free.
- Azure DevOps — two-way sync between boards and work items. Plan the slice in CardBoard; execute it in ADO.
- Jira — link cards to issues and keep title and status in step. Story-map upstream, deliver in Jira.
Editing a tracker-linked card requires a workspace member — every sync write carries the member’s identity into both audit logs. See Trackers and Working with your tracker.
Build on CardBoard
Section titled “Build on CardBoard”- REST API — read and write maps and cards programmatically with HTTP Basic auth.
- MCP server — let AI agents read maps and propose changes through the Model Context Protocol.
- CSV import / export — move cards, dividers, and outcomes in and out as spreadsheets.
Why so few trackers?
Section titled “Why so few trackers?”The set of supported trackers is intentionally small. We support the trackers our customers actually use, and support them well — better one solid integration than ten flaky ones. CardBoard is the planning surface; your tracker owns execution, and each stays the source of truth for what it does best.