For developers
Build on Mica
Mica ships with an extensible connector architecture — Linear is the first, showing live issue status and owner right inside a doc. More connectors, and a path for outside developers to build their own, are on the roadmap.
Live example
Linear, built in
Paste a Linear issue link into any doc and it renders as a live status chip — current state and assignee, right inline — instead of a plain link. Nothing is written back into the document: it's pure decoration over the same markdown link every other link uses, so copying the raw text elsewhere just yields a plain link again.
- An account admin connects a Linear workspace once, for the whole team
- Any doc collaborator sees live status/owner — no per-person setup
- The same architecture is built to support more connectors over time
How it's built
Reviewed, and privacy-first by construction
Every connector is reviewed before it ships, and none of them can see document content — Mica's core privacy invariant is that a doc's content lives only in your Google Drive and, transiently, in your browser's memory during a live session. A connector only ever sees the small, external identifier you linked to (like a Linear issue id), never the surrounding document.
- Connector code is reviewed before release, the same as any other Mica feature
- Encrypted-at-rest credentials, scoped per connected account
- No connector — Mica-built or otherwise — has a path to see document content
What's next
A path for outside developers
Today's connectors are built and operated by Mica. The next step is opening a real path for outside developers to build their own — modeled on how Mica already connects AI assistants via the Model Context Protocol: your code runs on your own infrastructure, and Mica grants it scoped, audited access to its API, rather than running someone else's code on Mica's own servers. We'll share more here once that path is ready.