Connect Claude Code
Use the same selected-file workflow from a Claude Code project.
Before you start
You need Node.js 22 or later, your coding agent’s CLI, and an existing project directory you explicitly approve for selected-file access. Download and extract the plugin archive below, then compare its SHA-256 checksum with the release manifest. The archive includes the compiled local runtime and its dependencies.
The integration runs locally. Connecting the MCP does not sign in to your marketplace account, upload files, publish a listing or authorize a payment.
The Claude plugin manifest and runtime protocol checks pass. Loading and invocation in a signed-in Claude Code host still need verification.
Connect your project
Replace both absolute paths: one selects your approved project; the other points to the extracted plugin runtime. On Windows, paths such as C:/Projects/my-project are valid absolute paths.
Run the setup command from the selected project directory. The public Devnet API supports marketplace discovery without an API key. The MCP requires explicit filenames and does not automatically scan your home directory, project history or conversations.
claude mcp add --env "REUSE_WORKSPACE_ROOT=/absolute/path/to/approved-project" --env "REUSE_API_URL=https://xoqssppzisyxzmgiugmt.supabase.co/functions/v1/reuse-api/v1" --env "REUSE_FRONTEND_URL=https://reusable-network.pages.dev" --transport stdio --scope local reusable -- node "/absolute/path/to/extracted-plugins/claude-code/plugins/reusable-network/runtime/mcp/index.js"Try the first tool
Start a new agent session and ask it to call Reusable’s status tool. Then ask it to search the marketplace and check a specifically selected skill package with check_skill. A successful status call confirms the local tool is running; a successful search confirms public API access.
The local tools can check a package, prepare a draft and return that draft on request. Purchase and protected download use the website. Account pairing and authenticated agent retrieval remain work in progress.
Build from source (optional)
Developers can build the same local tools from a trusted Reusable source checkout. Run these commands there, then use dist-mcp/mcp/index.js as the runtime path in the setup template.
npm ci --ignore-scripts
npm run build:mcp