# Capira

> Capira is a notes-first workspace where notes, tasks, collections, canvas, calendar, and habits are one interoperable system rather than five separate apps. Context is the atomic unit: you write notes to think, and tasks are extracted from them. Capira is designed to be read and driven by AI agents over the Model Context Protocol (MCP) and a REST API.

## What Capira is

- **Notes-first, not task-first.** Most tools treat a task as the atomic unit and bolt context on afterwards. Capira inverts this — context is the atomic unit and tasks (called *intents*) are derived from the notes where the thinking happened. The task view is a lens on your notes, not a standalone list.
- **A block-based editor.** Each element in a note is its own block, so structured content (text, images, embeds, records) composes cleanly.
- **One database, many surfaces.** Notes, tasks, collections, canvas, calendar, and habits all read and write the same underlying data and cross-reference each other.

## Primitives

- **Notes** — block-based rich documents; the primary thinking surface.
- **Tasks (intents)** — actionable items extracted from notes, with explicit lifecycle states (not just done/not-done) and links back to their source note.
- **Collections** — structured, spreadsheet-like databases with typed fields, formulas, and multiple views (table, list, calendar, gallery). A collection is also a tag: its records can be referenced inline anywhere in Capira.
- **Canvas** — a spatial surface for connecting notes, records, and ideas.
- **Calendar & events** — time-based placement of work and occasions.
- **Habits** — recurring practices with streaks.
- **Books** — the single "home" a note lives in.
- **Forms & inbound webhooks** — capture external data directly into collections.

## Design principle: the Walled Garden of Apps

Apps in Capira are built *inside* Capira from its own primitives (collections, notes, canvas, forms, tasks), and every app interoperates because they share one database. A trading journal, a reading list, a CRM, or a project tracker is composed from these primitives rather than imported as outside code. You extend Capira by composing within the garden.

## For AI agents

Capira is directly reachable by AI:

- **MCP server** — an agent can create, query, and update notes, tasks, collections, and records through Model Context Protocol tools, with the same guards as the app.
- **REST API** — programmatic access for automation and integrations.
- **Agent writes are surfaced, not silent** — when an agent creates content, Capira raises an arrival notification for the user.
- Point your own assistant (e.g. Claude) at your workspace to read and drive it.

## Privacy

- Capira does not sell user data and does not train AI models on user content.
- Data is stored in the EU.

## Links

- Home: https://capira.app/
- About (human page): https://capira.app/about
- Privacy Policy: https://capira.app/privacy
- Terms of Service: https://capira.app/terms