Connect Claude Code to Stuff
Install the Stuff plugin for MCP access plus four workflow skills. This is a separate installation from Claude's web connector. Plugins versus connectors.
1. Install
Download and extract the coding-agent bundle into a permanent folder. Replace the example path with the extracted stuff-ac directory:
claude plugin marketplace add /absolute/path/to/stuff-ac
claude plugin install stuff-ac@stuff-ac --scope user
Start a new Claude Code session. User scope installs it for you rather than a shared project. Sign in to Claude Code normally if needed. Official installation guide.
2. Connect
Run /mcp, select the stuff-ac plugin's server, and choose Authenticate. In our test it was named plugin:stuff-ac:stuff.
In the browser, check the Stuff account, choose Only spaces I choose, select a test space, and choose read-only or read/write as needed. Leave sharing/management disabled for a simple editing task. Review, choose Allow connection, and return to Claude Code.
This shows the form before approval. We approved the selected-space grant, and Claude Code's callback confirmed authentication:
The localhost callback port varies per session; do not copy it as your server URL.
Claude Code may also expose Claude.ai connectors. We observed an existing Claude.ai Stuff connection alongside this plugin's server. Avoid duplicate active Stuff servers and confirm which grant is used. Authorizing one does not automatically authorize the other. Claude Code MCP documentation.
3. Use the skills
Invoke /stuff-ac:project-context, /stuff-ac:safe-edit, /stuff-ac:local-folder or /stuff-ac:handoff, or describe the task naturally. Skills guide the workflow; your tool approvals and Stuff permissions still apply.
Use the Stuff project-context skill to read Project Lantern.md, summarize its status and give me the file link. Do not edit anything.
Then run the small edit and assistant handoff test.
Before a headless or automated run, confirm that the intended MCP server is available and authenticated. On October 5, Claude Code 2.1.287 loaded all four Stuff skills in a noninteractive session. With inherited Claude.ai connectors enabled, that session exposed the inherited Stuff connection instead of the plugin-owned server. A second diagnostic, with ENABLE_CLAUDEAI_MCP_SERVERS=false for that process only, exposed plugin:stuff-ac:stuff with status needs-auth. This verifies plugin discovery, not successful file access. Authenticate the plugin's own server and check its account/scope before a real task; do not silently use an inherited grant as evidence that the plugin is authorized. The October 1 successful read/create/revoke test below used an interactive session. Official plugin loading guidance.
MCP-only alternative
For tools without the bundled skills:
claude mcp add --transport http --scope user stuff https://stuff.ac/mcp
Authenticate through /mcp. Choose the plugin or this direct server; avoid configuring both unnecessarily. Neither needs a Stuff key pasted into chat.
Disconnect
Disable or uninstall stuff-ac in Claude Code, then revoke its specific connection in Stuff → Agents. Removing the plugin alone does not revoke authorization. Revocation walkthrough.
Verification, October 1, 2026: Claude Code 2.1.91 used plugin:stuff-ac:stuff to read the fictional brief, create Assistant handoff test.md at version 1, and read the saved original back. After we revoked that specific grant in Stuff, a fresh read required reauthorization and returned no file content. The browser screenshots and saved version history are genuine; we have not simulated a terminal screenshot.