Stuff plugins for coding agents
Connect Stuff to Claude Code, Codex or Cursor, then work on the same files across assistants. The plugin adds four workflows, called skills, alongside the Stuff MCP connection.
Connector, plugin, skill: what changes?
| Part | What it does | What it does not do |
|---|---|---|
| MCP connection | Gives an assistant authorized tools to find, read, create and edit Stuff files | Does not automatically teach your preferred workflow |
| OAuth | Lets you choose the Stuff account, spaces and permissions for a connection | Does not authorize every other assistant |
| Plugin | Packages MCP configuration, skills and product identity for a client | Does not grant extra permissions or bypass confirmation |
| Skill | Gives the agent instructions for a recurring task | Is not a permission boundary or guarantee of agent behavior |
| Optional Stuff CLI | Pulls files into a local folder and pushes deliberate changes | Is not installed by this plugin; it needs a separate scoped API key |
Claude Code plugins are separate installations from Claude's web connector. Codex is a different client from ChatGPT, even though OpenAI supports plugins in both. ChatGPT plugins can also bundle skills; skills are not exclusive to coding agents. Cursor has its own installation and authentication. All three use the same Stuff MCP server and files, with separate grants. Some Claude Code versions also expose existing Claude.ai connectors; check the actual connection before assuming a new plugin shares one. Claude Code plugins · OpenAI plugins · Cursor plugins.
Interactive previews in Claude or ChatGPT are a separate client capability. This coding-agent package does not add an embedded file viewer; agents use their own tools and link back to Stuff's viewers.
Four included workflows
| Skill | Use it for |
|---|---|
project-context |
Find the right space, read relevant files in bounded chunks, and cite their links and versions |
safe-edit |
Make targeted edits, check the current version and reconcile conflicts before retrying |
local-folder |
Choose local pull/edit/push when a task needs local editors, renderers or coordinated changes |
handoff |
Leave an explicitly requested handoff so another assistant can continue from saved originals |
The package contains no credentials, install scripts, hooks, background sync or automatic uploads. Stuff enforces permissions on every request. Skills guide behavior; they do not replace permission checks.
Download and install
Download Stuff.ac coding-agent plugins 0.2.0.
The ZIP is 23,676 bytes. SHA-256:
5559016287a7f19f100348faf3a9fd08b084821dc882567f9ee69d64114f7b81
Extract it into a permanent folder. The stuff-ac marketplace directory contains plugins/stuff-ac. You do not need access to Stuff's source repository. Installation and authorization are separate steps.
This is a direct-install release. Public marketplace listings and vendor reviews are separate. Managed workspaces may restrict local plugins.
First useful task
Start with a harmless private test space. Our screenshots use Project Lantern, a fictional reading-club project in a separate Stuff demo account.
Use Stuff to list the spaces you can access. Read Project Lantern.md, tell me its current status and give me its file link. Do not change anything.
Then, if editing is enabled:
Create Launch checklist.md in Project Lantern with three tasks. Read the saved original back and give me its link. Keep sharing unchanged.
Give that link to another connected assistant:
Read this file from Stuff. Add one useful task, preserving existing content and checking the current version. Read the saved result back and explain what changed.
Check the original and Version history in Stuff. A private link identifies a file; each assistant still needs permission. Remote editing or local pull/push.
What we have checked
Checked October 1, 2026. These are genuine installation and consent screenshots, not mockups.
| Client | Verified in this walkthrough | Coverage limit |
|---|---|---|
| Claude Code 2.1.91 | Installed plugin; its own MCP grant read the brief, created version 1 and read it back; fresh read denied after revocation | Interactive session; one separate headless session did not expose the plugin MCP tools |
| Codex CLI 0.158.0-alpha.2.1 | Installed skills loaded; direct MCP read version 1, saved version 2 with approval and read it back; fresh read denied after revocation | Direct MCP plus plugin skills; plugin-specific desktop OAuth remains unverified |
| Cursor 3.22 | Local plugin authenticated; safe-edit skill loaded; read version 2, saved version 3 and read it back; fresh read denied after revocation | Local IDE plugin; Cloud Agents and public marketplace listing are separate |
Each tested grant allowed only Project Lantern, read/write, without sharing management. All demo grants were revoked afterward. The consent screenshots were captured before approval; the completed three-assistant handoff shows the saved original, version history and fresh access-denied results. This test covers remote Markdown work, not local folder pull/push or every file format.
Other coding clients
Gemini CLI can connect directly: gemini mcp add --transport http stuff https://stuff.ac/mcp, then /mcp auth stuff inside the client. This vendor-documented route is separate from this three-client package test. Gemini CLI documentation.