How to connect ChatGPT to your Cozy wiki over MCP

Updated · By the Cozy team

To connect ChatGPT to Cozy, go to chatgpt.com/plugins, choose + and then Add custom MCP server, name it Cozy, and paste https://cozy.cloud/mcp. ChatGPT runs the OAuth sign-in, you approve access on Cozy's consent page, and ChatGPT can reach all your workspaces. Whether ChatGPT can write or only read depends on your plan, as set by OpenAI.

What you need first

Your Cozy account has one hosted MCP endpoint for every workspace. It is stateless Streamable HTTP and supports MCP protocol versions 2025-03-26, 2025-06-18 and 2025-11-25:

https://cozy.cloud/mcp

For background on what the server exposes, see the Cozy MCP server page.

Connect ChatGPT with OAuth

ChatGPT's menu names for connectors and developer features change from time to time. When we checked, the flow was:

  1. Open chatgpt.com/plugins.
  2. Choose + and then Add custom MCP server. Depending on your plan, you may need to turn on a developer or advanced option first.
  3. Name it Cozy and paste https://cozy.cloud/mcp as the server URL. Do not add an Authorization header.
  4. ChatGPT sends you to Cozy to sign in and approve the connection on the consent page.
  5. Back in ChatGPT, enable Cozy for the conversation where you want to use it.

Cozy uses OAuth 2.1 with dynamic client registration, S256 PKCE and refresh tokens, so ChatGPT registers itself and renews its access without asking you to sign in every time. Connected agents are listed under Connectors → Agents in Cozy, where you can disconnect ChatGPT at any time.

What ChatGPT can do through the connector

The connector exposes Cozy's tools, file resources, resource templates and prompts. ChatGPT can use the read tools to look things up in your wiki:

The write tools are cozy_write, cozy_edit, cozy_append, cozy_move, cozy_delete and cozy_ingest. Edits require an expectedRevision, with 0 for a new page, and concurrent edits return a conflict instead of overwriting. Deleting a page leaves a tombstone, and the last 50 revisions can be read and restored.

Cozy runs no model of its own. ChatGPT does the reasoning, and Cozy provides the wiki and the guarded access to it. Search is lexical, with no embeddings.

Read access versus write access

The OAuth scopes are wiki:read, wiki:write and sources:write. A read scope is enough for ChatGPT to search, read and navigate the wiki. Writing needs a write scope approved on Cozy's consent page and a ChatGPT plan that lets custom connectors call write-capable tools.

The second part is controlled by OpenAI, not by Cozy. Secondary sources we found report that write-capable custom connectors are limited to some business-tier plans while other plans are read-only. OpenAI's own documentation was inconsistent when we looked, so we are not stating a plan list here. Before you rely on ChatGPT to save notes, check OpenAI's current help pages for your plan. If your plan is read-only, you can still use ChatGPT to recall and cite your wiki, and let Claude or Codex do the writing.

Cozy also limits what any connected agent can do. ChatGPT's access is capped by the scopes you approved and by your own access, checked on every request. Agents cannot see connector credentials or permanently purge content.

OAuth or a bearer token

OAuth on the account URL is the right choice for ChatGPT because you sign in and approve access through the browser. Bearer credentials are for scripts, CI and headless agents. They are created in "Agents" for one workspace and used with that workspace's URL, https://cozy.cloud/wiki-mcp/WORKSPACE_UUID. They are shown once, stored as SHA-256 digests, revocable, and expire within 90 days. They carry the scopes read, wiki-write and source-write, and can be limited to folder prefixes.

ChatGPT's custom MCP server flow uses OAuth, so use the account URL above. OAuth on a workspace URL also still works, but it grants only that workspace.

Where ChatGPT writes

Cozy workspaces have four top-level folders:

If you let ChatGPT write, approve only the scopes it needs. Folder-prefix limits are available on workspace bearer credentials, not on the OAuth connector. Every save also updates the graph from your Markdown conventions, and cozy_health will flag broken links, stale pages and conflicts afterward.

Troubleshooting

For other clients, see Connect Codex. For common questions about accounts and access, see the FAQ.

Frequently asked questions

Does ChatGPT need a token to connect to Cozy?

No. Add https://cozy.cloud/mcp as a custom MCP server with no Authorization header and let ChatGPT run the OAuth sign-in. Bearer tokens from Agents are meant for scripts and headless agents that use a workspace URL.

Can ChatGPT write to my Cozy wiki?

Only if both sides allow it. Cozy needs a write scope you approved, and OpenAI decides which ChatGPT plans can use write-capable custom connectors. Check OpenAI's current documentation for your plan.

How long does the ChatGPT connection last?

Cozy issues refresh tokens, so ChatGPT renews its access without asking you to sign in every time. You can disconnect it at any time under Connectors → Agents in Cozy.

Which URL do I use for ChatGPT?

Use https://cozy.cloud/mcp. It is one URL for your account and reaches My wiki and any other workspaces you created. See the MCP server page for more on what it exposes.

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