# Connect Codex Give your existing agent local tools to check and prepare selected skill files. Status: Local setup. Reviewed: 2026-10-09. ## 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. > An isolated Codex plugin installation and tool invocation have been tested. These templates require your own filesystem paths. [Download plugins v0.3.1 · ZIP](https://reusable-network.pages.dev/downloads/reusable-network-plugins-0.3.1.zip) [Release checksums](https://reusable-network.pages.dev/downloads/release.json) ## 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. ```text codex mcp add reusable --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" -- node "/absolute/path/to/extracted-plugins/codex/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. Purchases remain in the website. Codex account pairing and owned downloads are available for Devnet testing; Claude Code host testing remains deferred. [Learn how to prepare a skill](https://reusable-network.pages.dev/docs/sell-a-skill/) [Permissions and privacy](https://reusable-network.pages.dev/docs/privacy/) ## Connect your account in Codex Ask Reusable MCP to call start_account_pairing. Open the returned website link yourself, sign in, compare the 12-character code with Codex, and approve only the request you started. This grants Library reads and downloads of versions you own for seven days. It grants no purchase, publication or installation authority. Return to Codex and call check_account_pairing, then account_status and list_library. Select an exact owned version for download_owned_skill. The tool checks canonical bytes and the authorized package hash, then saves a bundle under your project’s .reusable/downloads directory for review. Review every file before separately approving installation or use. Manage or revoke connections on the website, or ask Codex to call disconnect_account. Each request checks revocation and expiry. The credential is stored outside your project; Windows uses encryption tied to your local Windows account. Actual Claude Code account-host testing remains deferred. [Manage agent connections](https://reusable-network.pages.dev/connect/) ## 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. ```text npm ci --ignore-scripts npm run build:mcp ```