Integrations
CardBoard is the planning surface; your tracker owns execution. Do the thinking on a board, then sync the committed work to Azure DevOps, Jira, Linear, Shortcut, or Trello — without re-typing a thing.
Trackers
Section titled “Trackers”A linked card is coupled to its tracker item on the fields that describe the work, and decoupled on position. Change a title or status in either place and the other side follows. Move a card anywhere on the map and the tracker hears nothing, because position is the plan. Sync is per card: you choose what links, and everything else stays on the map.
| Azure DevOps | Jira | Linear | Shortcut | Trello | |
|---|---|---|---|---|---|
| A board connects to | One project | One project (optionally a saved filter) | One team | One team | One Trello board |
| Workspace connection | Organization and service hooks | Workspace app in development | One grant, set up by an admin | One outgoing webhook per Shortcut workspace | None, a webhook per board |
| Identity on writes | Each member signs in | Each member signs in | Through the grant | Each member’s API token | Each member’s API key and token |
| Title, description, status | Both ways | Both ways | Both ways | Both ways | Both ways |
| Acceptance criteria | Both ways | Not synced | Not synced | Not synced | Not synced |
| Assignee | Both ways | Both ways | Not synced | Not synced | Not synced |
| Story points | Both ways | Both ways | Both ways | Both ways | Not synced |
| Parent | To Azure DevOps, and on import | On import | Both ways | Not synced | Not synced |
| Marketplace listing | Not listed yet | Not listed yet | Not listed yet | Not listed yet | Not listed yet |
Position, slices, connections, color, reactions, and comments never sync on any tracker. The Trackers concept page explains how workspaces, boards, and cards map to tracker accounts, projects, and items.
Connecting a tracker takes a paid plan: Pro, Team, or Enterprise. Editing a linked card takes a workspace member, because every write to your tracker is attributed to a person. See 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, boundaries, and outcomes in and out as spreadsheets.