Set up RenX in DeepSeek Harness

Bring RenX hiring into DeepSeek Harness using its built-in MCP client and the mcp-remote OAuth adapter. Your assistant works through your RenX agents; you do not need RenX Desktop or a local RenX bridge.

Profile loading and skill discovery have been tested with Harness 0.1.2-rc.1, alongside the actual MCP client and adapter against a mock server. Live RenX sign-in and a full hiring conversation are not yet verified. DeepSeek Harness is still in developer preview.

Prepare your assistant

Use Node.js 22.x from 22.19.0, or Node.js 24 or later. The terminal commands below are for macOS or Linux and use the Harness release checked for this integration:

npx --yes @deepseek-ai/dsh@0.1.2-rc.1 plugin --profile web add @deepseek-ai/dsh-mcp-client@0.1.2-rc.1

If you already use a different Harness version, install its matching MCP client version instead. Do not mix release candidates.

Sign in to RenX

Run this first-time connection check before starting the Harness session:

npx --yes --package=mcp-remote@0.8.4 mcp-remote-client https://mcp.openmercury.com/mcp --transport http-only --auth-timeout 300

Your browser opens for RenX sign-in. Check the account and requested access, approve the connection, and return to the terminal. Once tools are listed, the connection is ready. If the check remains running, press Ctrl+C.

Signing in separately gives you time to finish without the Harness connection timing out. The adapter retains the sign-in locally and refreshes it when needed. Never paste access tokens into chat or configuration files.

Add the connection and hiring skill

Clone the RenX plugin repository if you have not already:

git clone https://github.com/Jackyhaorockman/renx-plugin.git

Merge the entry in renx-plugin/plugins/renx/deepseek-harness.cordis.yml into ~/.dsh/profiles/web/cordis.patch.yml. Keep your other entries and add the RenX entry only once. This configuration is included in RenX plugin 0.2.0 and later.

Install the same hiring skill used by the other RenX integrations:

mkdir -p ~/.dsh/skills
cp -R renx-plugin/plugins/renx/skills/renx-hiring ~/.dsh/skills/
npx --yes @deepseek-ai/dsh@0.1.2-rc.1 web

If the skill is already installed, review it before replacing it. Start a new Harness session and ask:

Use the renx-hiring skill and show my RenX agents and sessions.

Then describe the outcome you want:

Help me hire someone to deliver a tested landing page by Friday. My budget is $500. Find suitable providers first; do not fund a contract yet.

The tools appear with the mcp__renx__ prefix. Your assistant uses the same RenX messaging and hiring workflow as the other hosted MCP integrations. See Hiring and deals for the full process.

Stay in control

The OAuth adapter runs as a child of the Harness MCP connection, not an always-on RenX service. It is third-party software and stores credentials under ~/.mcp-auth by default. Keep that directory private.

Personal approvals and payment, payout, or tax setup still follow RenX’s existing rules. Complete setup in the signed-in browser page, then return to your assistant and ask it to continue. Hosted MCP does not wake the assistant automatically. Embedded RenX upload and approval widgets are not verified in Harness; use the RenX app when an embedded interface is unavailable.

To disconnect, remove the RenX entry from the profile patch and restart Harness. Revoke its access under RenX Settings > Devices. Removing configuration alone does not revoke the server-side authorisation.