Skip to main content

Parity Overview

Copera exposes the same workspace capabilities through four parallel surfaces. They share the underlying API, but they do not all expose every capability — some are intentionally read-only or narrower in scope.

  • Public API — the REST API, callable from any language or platform.
  • CLI — drive boards, docs, drive, and messaging from your terminal or CI.
  • MCP server — connect AI clients (Claude, Cursor, and other MCP hosts) to your workspace.
  • Native AI — a read-only subset exposed directly to Copera's in-product AI (board data + personal schedule).

Use this page to decide which surface fits your use case and to spot where a capability is missing on a given surface.

Capability matrix​

Legend: ✅ full · ◑ read-only · — none

DomainPublic APICLIMCPAI
Workspace✅✅✅—
Boards/Rows (read)✅✅✅◑
Rows (create/update/delete)✅✅✅—
Row rich-text column markdown✅✅——
Row authenticate✅✅——
Row comments + attachments✅✅✅—
File-column upload/remove✅———
Table export (async)✅✅✅—
Docs✅✅✅—
Drive (browse/download/folders)✅✅✅—
Drive multipart upload✅✅——
Channels/Messaging✅✅✅—
Search✅✅✅—
Notifications✅✅✅—
Bookings✅——◑

Native AI surface​

Copera's native AI exposes a read-only subset of the board and bookings domains — enough to look up and read structured data, but nothing that mutates the workspace. The available tools are:

Board tools:

  • copera_list_boards
  • copera_get_board
  • copera_list_tables
  • copera_get_table_schema
  • copera_list_rows
  • copera_get_row
  • copera_get_row_markdown

Schedule tool (personal scope):

  • getMySchedule — reads the authenticated user's own upcoming bookings and calendar. This is a personal view; it does not expose workspace-wide booking data or other users' calendars.

For anything beyond reading boards or your own schedule — writes, docs, drive, channels, search, notifications, or workspace-wide booking data — use the Public API or MCP server.

Known gaps​

Some capabilities are deliberately absent on specific surfaces:

  • No CLI for Bookings — the CLI does not yet ship bookings commands. Use the Public API until CLI support lands. See the Bookings guide for the REST Quick Start.
  • No MCP for Bookings — no MCP booking tools are exposed at this time. Use the Public API.
  • No MCP or AI for row rich-text column markdown — available via Public API and CLI only.
  • No MCP or AI for row authenticate — Public API and CLI only.
  • No MCP or AI for Drive multipart upload — Public API and CLI only.
  • AI bookings access is personal-scope only — getMySchedule reads the authenticated user's own upcoming schedule. Workspace-wide booking data (all hosts, all types) is not accessible from the native AI; use the Public API instead.
  • AI is otherwise read-only and limited to boards + personal schedule — no writes, and no non-board/schedule domains.

When a surface doesn't cover what you need, fall back to the Public API, which is the full surface.

Where to go next​