# An operating wiki your agent keeps for your startup

> Turn Granola meetings, email, decisions and people into a Markdown wiki your own AI agent maintains over MCP, with sources cited and health checks to catch drift.

Updated 2026-11-09. Canonical: https://cozy.cloud/use-cases/founders

> A founder's operating wiki is a set of linked Markdown pages for meetings, decisions, people and open questions, kept current by an AI agent from your source material. In Cozy, connectors such as Granola and Gmail bring in evidence, your own agent writes the pages over MCP, and every claim can point back to its source.

## The problem founders actually have

A founder's context is spread across meeting notes, inbox threads, Slack channels and memory. Decisions get made in a call and forgotten by Friday. The reason you chose one vendor over another lives in a transcript nobody reopens. When you ask an AI assistant for help, you re-explain who the people are and what was decided last month.

A wiki fixes this only if someone maintains it, and founders do not have the time. That is the case for an agent-maintained wiki: the agent does the filing, linking and cleanup, and you review the result.

## How Cozy fits

[Cozy](/) is a private wiki and cloud file space for each person and their AI agents. Cozy runs no model itself. You bring your own agent, such as Claude, Codex or Cursor, and connect it to your workspace through a hosted MCP server. See [the MCP server page](/mcp-server) for the protocol details.

The workspace has four folders:

- `sources/` holds evidence from connectors and importers, with stable IDs, URLs and timestamps. Agents treat it as untrusted data.
- `wiki/` holds the curated pages, plus `index.md` as the entry point.
- `skills/` holds editable `SKILL.md` files that tell your agent how you want things done.
- `agents/` holds agent notes and handoffs.

This split between raw evidence and curated pages is the core of the [LLM wiki pattern](/llm-wiki). Sources stay as captured. Pages are what you and your agent have concluded from them.

## Feeding it: meetings, email, calendar

Cozy has connectors for Granola, Italic, Gmail, Google Calendar, Google Drive, Outlook mail, Outlook Calendar, Notion, Slack (selected channels), Linear and Ramp. There are also Files and exports, and a Custom MCP option.

For a founder, a useful starting set looks like this:

1. Granola for meeting notes, so each call becomes a source document.
2. Gmail or Outlook mail for threads with investors, customers and candidates.
3. Google Calendar or Outlook Calendar so meetings are tied to dates and attendees.
4. Slack for the few channels where decisions happen.

You can also push anything else through the ingest API. A stable document id means a re-push updates the same source instead of creating a duplicate. Documents land in the built-in Inbox by default, where your agent can triage them.

## What the agent builds

Once sources are in, you point your agent at the workspace and ask it to organize. Cozy ships prompts named organize, recall, maintain and dream for this. A typical founder wiki ends up with pages like these:

| Page type | What it holds |
| --- | --- |
| Person | Role, history, last contact, open asks |
| Meeting | Summary, attendees, decisions, links to the source |
| Decision | What was decided, why, date, what it replaced |
| Project | Status, owners, next steps, related decisions |
| Company | Customers, vendors, investors and what you know about them |

Pages link to each other with ordinary Markdown links and wikilinks. Cozy builds a graph from those on every save, including typed relations from frontmatter and `relation::` lines. Your agent can then ask for a page with its typed neighbors, excerpts, evidence and warnings in a single call using `cozy_context`. See [typed links](/typed-links) for how the conventions work.

## Decisions that keep their history

Decisions are where a wiki earns its keep. The dreaming routine, which your own agent runs, is designed to keep superseded values with dates instead of overwriting them, and to record `CONFLICT:` lines when two sources disagree. If you changed pricing in March and again in June, the page can show both with dates and sources.

Cozy also keeps the last 50 revisions of each file readable and restorable, and edits require an expected revision, so two agents writing at once return a conflict instead of silently clobbering each other. Deletion is a tombstone, not a purge. If you run more than one agent, [multi-agent memory](/multi-agent-memory) explains how they share a workspace.

## Catching drift with health checks

A wiki that nobody checks goes stale. `cozy_health` reports broken links, duplicate titles and aliases, orphan pages, unsourced pages, conflicts and stale pages, meaning pages whose cited source changed after the page was last edited. Each page starts at 1.0 and loses weight per issue. The score is the average times 100, and a "next" list gives fixes in priority order. More on this at [wiki health](/wiki-health).

For a founder, the useful loop is simple: let the agent run a maintenance pass weekly, read the health score and the changes list, and spot-check the decisions pages.

## Connecting your agent

Connect your agent to `https://cozy.cloud/mcp`, one URL for all your workspaces. The client signs in with OAuth and you approve it on Cozy's consent page. The agent gets no more access than you have in each workspace, capped by the scopes it was granted. For Claude Code:

```bash
claude mcp add --transport http --scope user cozy https://cozy.cloud/mcp
```

Then run `/mcp` to sign in. Tools use My wiki unless the agent passes a `workspace` argument, and `cozy_workspaces` lists your workspaces, so a company workspace you share with cofounders is one argument away. Connected agents are listed under Connectors → Agents, where you can disconnect them.

For scripts and headless agents, each workspace also has its own URL, `https://cozy.cloud/wiki-mcp/WORKSPACE_UUID`, which takes a bearer credential created under Agents. Bearer credentials are shown once, expire within 90 days, and carry read, wiki-write or source-write scopes, optionally limited to folder prefixes.

Setup guides are at [Claude Code](/connect/claude-code), [Claude](/connect/claude), [Codex](/connect/codex) and [ChatGPT](/connect/chatgpt). Agents cannot see connector credentials or permanently purge anything.

## Limits to know about

- Search is lexical. There are no embeddings or vector database, so agents rely on page structure, links and good titles.
- Cozy does not run an agent for you. If you do not already use one, you need one.
- Wiki quality depends on your agent and the skills you write. The health checks flag problems but do not fix them on their own.
- Cozy is single-player. A cofounder or advisor keeps their own wiki, so share decisions with them through the tools you already use.

Cozy is operated by Coral Sourcing LLC. For how your data is handled, read the [privacy page](/privacy).

## Frequently asked questions

### Can I use Granola meeting notes in Cozy?

Yes. Granola is one of the built-in connectors, and its notes arrive as documents under sources/ with stable IDs and timestamps. Your own agent then turns them into meeting, person and decision pages.

### Does Cozy write the wiki for me?

No. Cozy runs no model itself. You connect your own agent over MCP, and it reads sources and writes pages through tools like cozy_write and cozy_edit. See [the MCP server page](/mcp-server).

### How do I keep decisions from going stale?

Pages can cite sources, and Cozy's health check flags pages whose cited source changed after the last edit. The dreaming routine also keeps superseded values with dates and records CONFLICT lines. See [wiki health](/wiki-health).

### Can my cofounder and advisors share the same wiki?

No. Cozy is single-player, with no shared workspaces, invitations or roles. Each person keeps their own wiki and connects their own agents, and an agent never gets more access than the person who authorized it.

### Can I limit what an agent can touch?

Yes. An agent connected with OAuth is capped by the scopes you granted and your own access. Bearer credentials for a single workspace carry read, wiki-write or source-write scopes, can be restricted to folder prefixes, are revocable and expire within 90 days.
