Connect your assistants
One home for your files. Connect an assistant, give it a small job, and pick up the same work in another assistant.
MCP server: https://stuff.ac/mcp
Checked October 1, 2026. These guides use real product screenshots, with fictional Project Lantern material. Stuff screenshots use a separate demo account. Assistant setup screenshots show the actual controls in available accounts, cropped where needed to keep account details out of the guide. They do not imply that fresh demo accounts were created at each assistant provider.
Choose your assistant
| Assistant | Start here | What to expect |
|---|---|---|
| Claude | Claude setup | Remote MCP and Stuff sign-in; supported interactive file previews |
| ChatGPT | ChatGPT setup | Custom MCP app/plugin and Stuff sign-in; supported interactive file previews |
| Gemini | Gemini setup | Custom app and Stuff sign-in; tool results and file links |
| Claude Code | Claude Code plugin | Plugin MCP + four skills; read/create/revoke verified |
| Codex | Codex plugin | Installed skills + direct MCP; read/edit/revoke verified |
| Cursor | Cursor plugin | Local plugin + four skills; read/edit/revoke verified |
| Grok | Grok setup | Documented custom MCP route; a fresh walkthrough is still to be verified |
| Gemini CLI and other coding clients | Coding-agent overview | Direct MCP and optional local workflows |
| Meta Muse and other clients | Full connection reference | Custom API integration where remote MCP is unavailable; client support varies |
Custom connections do not require Stuff to be listed in an assistant's public directory. A directory submission or prepared integration is not a guarantee of listing approval. Menu names, eligibility, and workspace policies can change.
For coding clients, download the plugin and compare plugins, skills and connectors. See the completed Claude Code → Codex → Cursor handoff, including screenshots, version history and revocation checks. The client guides state the exact tested configuration and remaining coverage limits.
Start with one space
Create a private space with a harmless sample document. In our walkthrough, this is Project Lantern, a fictional reading-club launch project.
When the assistant sends you to Stuff, check which Stuff account is signed in. Choose only your test space. Start read-only, or allow editing if the first task requires it. Leave organization and sharing off unless you need those actions. The OAuth consent screen chooses these permissions; the API-key form below illustrates the equivalent limited scope for a script.
The screenshot shows a prepared form. The walkthrough's actual key was created, tested, and revoked; no usable credential is included in these docs.
Prove that it works
Ask your connected assistant:
Use Stuff to list the spaces you can access. Read Project Lantern.md and tell me its current status. Give me the file's Stuff link. Do not change anything.
If you granted editing:
In Project Lantern, create a new file called Launch checklist.md with three launch tasks. Read it back and give me its Stuff link. Keep sharing unchanged.
Then give a second connected assistant the resulting link:
Read this file from Stuff using your connection. Add one useful task, preserving the existing content and checking the current version before saving. Read it back and explain what changed.
Open Version history in Stuff to inspect the saved versions. If the file changed in the meantime, the agent should read the newer version and reconcile it before retrying.
Stay in control
- Disconnect and revoke access, including our actual before/after test.
- Privacy and security: what is shared, stored, and retained.
- Remote editing or a local checkout: choose the right way to work.
A private file link identifies the file; it does not grant access. Each assistant needs its own permitted connection.