Using Cozy on a team: each person keeps their own wiki

Updated · By the Cozy team

Cozy is single-player. There are no shared workspaces, invitations, members or roles. On a team, each person keeps their own wiki, "My wiki" plus any private workspaces they create, and connects their own AI agents to it. Only that person and the agents they authorize can reach it. If your team needs one wiki everyone edits together, use a team tool alongside Cozy.

What single-player means for a team

Every Cozy account starts with "My wiki". You can create more workspaces to keep projects apart, and each one is private to you. Nobody else can be added to a workspace. Each holds the same four folders: curated pages in wiki/, evidence in sources/, editable skills in skills/, and agent notes in agents/.

So Cozy does not replace a shared team wiki. What it gives each person on a team is a private memory that their own agents read and maintain, separate from what the rest of the team sees. Cozy runs no model itself, so each person brings whichever agent they already use.

How a team can still use Cozy

Agents act for one person

Agents get no more access than the person who authorized them, and they are capped by granted scopes.

  1. OAuth on the account URL. https://cozy.cloud/mcp reaches all of your workspaces. OAuth 2.1 with dynamic client registration, S256 PKCE and refresh tokens. You approve each agent on Cozy's consent page and choose its scopes (wiki:read, wiki:write, sources:write). Connected agents are listed under Connectors → Agents, where they can be disconnected.
  2. Bearer credentials on a workspace URL. For scripts, CI and headless agents, each workspace has its own endpoint at https://cozy.cloud/wiki-mcp/WORKSPACE_UUID. You create credentials in Agents. Each one is random and shown once, stored only as a SHA-256 digest, revocable, and expires within 90 days.

A bearer credential carries scopes: read, wiki-write and source-write. You can also limit it to folder prefixes, for example giving one agent write access under agents/ and nothing else. Giving each agent its own connection or credential means you can tell them apart, disconnect one without touching the others, and keep a research agent from writing to curated pages.

Some actions are never available to an agent: seeing connector credentials and permanently purging. More on the threat model is in MCP security.

Connecting your agents

For Claude Code, add the account URL and then run /mcp to sign in:

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

For Codex, run codex mcp add cozy --url https://cozy.cloud/mcp, which opens a browser to sign in. In Claude.ai, add a custom connector with the same URL. Tools use My wiki unless the agent passes another workspace's ID or exact name as workspace, and cozy_workspaces lists the choices.

For a script that should only reach one workspace, use its workspace URL and a bearer credential. For Codex, add this to the config and export the token:

[mcp_servers.cozy]
url = "https://cozy.cloud/wiki-mcp/WORKSPACE_UUID"
bearer_token_env_var = "COZY_MCP_TOKEN"

For Claude Code, put this in .mcp.json, and give each machine or CI job its own credential:

{"mcpServers":{"cozy":{"type":"http","url":"https://cozy.cloud/wiki-mcp/WORKSPACE_UUID","headers":{"Authorization":"Bearer ${COZY_MCP_TOKEN}"}}}}

Handoffs between your agents

The agents/ folder is where agent notes live. A practical convention is one short note per handoff: what the agent was asked to do, what it finished, what it left open, and which pages it touched. The next agent reads the note instead of rebuilding context from scratch. cozy_changes returns what changed since a timestamp, and cozy_history shows the revision trail of any page. See multi-agent memory for the full pattern.

Edits require expectedRevision (0 for a new page), so two of your agents editing the same page get a conflict instead of a silent overwrite. Deleting a page creates a tombstone, and the last 50 revisions are readable and restorable with cozy_history and cozy_restore.

Where Cozy is a poor fit

If your team needs a wiki that several people edit together, with comments, sharing, permissions or live co-editing, Cozy does not do that. A team documentation tool is the better choice, and Cozy vs Notion covers one option. Search is lexical, with no embeddings. Cozy is operated by Coral Sourcing LLC and is not affiliated with Cozy Cloud (cozy.io) or Cozi.

Getting started

  1. Each person signs in with an email code, Google or Apple on the web app or the Mac app.
  2. Each person connects their own agents to https://cozy.cloud/mcp and approves the narrowest scopes that work.
  3. Create a private workspace per project if My wiki gets crowded.
  4. Agree as a team where shared outputs go, such as the repository or your team docs.

Questions about plans and limits are covered in the FAQ.

Frequently asked questions

Can my team share a Cozy workspace?

No. Cozy is single-player: there are no shared workspaces, invitations, members or roles. Each workspace is private to the person who created it and the agents they authorize.

How can a team use Cozy, then?

Each person keeps their own wiki and connects their own agents. Results that others need, such as decision records, are plain Markdown you can copy into your repository or team docs. For a wiki the whole team edits, use a team tool alongside Cozy.

Can each agent have its own credential?

Yes. Each agent connects with its own OAuth grant, listed under Connectors → Agents. For scripts, you create bearer credentials in Agents. Each is random, shown once, stored as a SHA-256 digest, revocable, and expires within 90 days. You can limit scopes to read, wiki-write or source-write, and optionally to folder prefixes.

Can an agent do more than I can?

No. An agent never gets more access than the person who authorized it, and it is capped by the scopes it was granted. Agents also cannot see connector credentials or permanently purge. See MCP security.

What happens if two of my agents edit the same page?

Edits require expectedRevision, so a concurrent edit returns a conflict instead of overwriting. The agent reads the latest revision and retries.

Give your agents a memory worth keeping

Cozy gives every account a private wiki that Claude, Codex, ChatGPT and other MCP clients can read and maintain.

Start your wiki