Guide
Integrations
Connect durable sources and live MCP tools without breaking team isolation.
Connected sources
First-party integrations and ingest paths can create durable evidence. MCP servers give the agent live reach into approved tools; successful tool results are captured privately, but MCP is not passive provider sync.
- Google Drive syncs selected folders and files into the document drive.
- GitHub and Linear bring engineering and project activity into the operational record.
- Monday.com syncs selected boards, generic records, subitems, updates, columns, and WorkDocs.
- Slack workspace ingestion syncs selected channels, threads, files, reactions, and edits.
- Sentry syncs issue updates, resolved issues, and releases into cited events, evidence clusters, and customer/project associations.
- Slack, Telegram, email, and meeting bots are capture surfaces for conversations and calls.
- Custom MCP servers expose approved live tools and context to the agent; successful tool results are captured as private evidence for later reconciliation while passive provider activity still needs native sync or custom ingestion.
Security model
OAuth tokens and bearer secrets are encrypted at rest. Imported snippets are treated as external content before the agent sees them.
- Admins control team-level source activation.
- Connection owners control what provider resources are shared.
- For Monday.com, selecting a parent board also captures its classic subitems; hidden “Subitems of …” helper boards are not selected separately.
- Personal MCP connections are visible only to their owner.
- Outbound Timeline MCP keys see only team-visible events.