Use case · ChatGPT
Shared docs for ChatGPT
ChatGPT can reason about your documents, but it can't keep them. Every session starts empty, and you end up pasting the same context again and again. Writespace fixes that: it gives ChatGPT a persistent workspace it can read and write to over the Model Context Protocol.
Free up to 10 documents — no card required.
One connection, then it just works
Generate a personal access token in Writespace, connect it to your MCP-capable ChatGPT client, and your workspace is available. From then on ChatGPT can reach your docs directly — no uploading files, no re-pasting yesterday's notes.
From chat to live documents
With the connection in place, ChatGPT works on real docs instead of throwaway text:
- Search the whole workspace and pull back ranked, relevant snippets.
- Create new docs and append to existing ones.
- Replace a specific section by its heading, leaving the rest untouched.
- Organise the workspace — folders, moves, metadata — on your behalf.
Responses are deliberately lean, so ChatGPT spends its context on your work rather than repeating what it just wrote.
Your knowledge base, not a transcript
The value of shared docs is permanence. Instead of decisions and drafts disappearing into chat history, they live in structured documents you can find later — by search, by folder, or by metadata. ChatGPT becomes a way to work that knowledge base, not just talk about it.
Works with the rest of your stack
The same workspace is open to any MCP client at once — Claude, Gemini, Cursor — and to your teammates, with real-time editing and live cursors. Switch tools freely; the docs stay put.
Free tier: up to 10 documents and full editor access. Pro is $5 per user / month for unlimited documents and collaboration.