sources·MCP today · source connectors on the roadmap

one memory layer across the AI clients you already use.

Today, capture happens only when you or your AI explicitly invokes a 3ngram MCP tool. 3ngram does not passively read chats, repositories, documents, calendars, or project tools.

available now·explicit capture over MCP

claude

via MCP. ask claude to debrief at the end of a session, only what you flag gets stored.

via mcp

chatgpt

via MCP. ask the client to debrief, review the proposed records, and save only what matters.

via mcp

cursor

via MCP. agent sessions, composer chats, captured by debrief.

via mcp

codex

via MCP. agent runs, rationale lines, human checkpoints.

via mcp

source connectors·roadmap · not available today

Source sync has not shipped yet. These are the systems 3ngram plans to read from — each will be invoked, scoped to what you name, and revocable, same as everything else.

basecamp

planned project-scoped connector for to-dos and message boards.

roadmap

github

planned repository-scoped connector for pull requests, reviews, and issues.

roadmap

linear

planned project-scoped connector for issue state and comments.

roadmap

google docs

planned file-scoped connector for documents you explicitly select.

roadmap

google calendar

planned calendar-scoped connector for events you explicitly grant.

roadmap

jira

planned project-scoped connector for issue rationale and comments.

roadmap

confluence

planned site-scoped connector for spaces and pages you select.

roadmap

product boundary·no passive ingestion

Digests, messaging bots, and automatic source synchronization are not part of the v1 product. When a connector ships, this page will name its exact scope and status.