Claude Code
These steps follow Claude Code’s own documentation. WeHarness has not yet tested Claude Code end to end; see Compatibility.
Add WeHarness
Section titled “Add WeHarness”Run this in a terminal:
claude mcp add --transport http --scope user weharness https://mcp.weharness.io/mcp--scope user makes WeHarness available in all your projects. Leave it out to add it to the current project only.
Sign in
Section titled “Sign in”- Start Claude Code and run
/mcp. - Choose
weharnessand select the option to authenticate. - Your browser opens WeHarness sign-in. Sign in and allow the access Claude Code asks for.
- Back in Claude Code,
weharnessshows as connected.
Claude Code stays signed in while you use it, for up to 90 days. See Sign-in and disconnect.
Check the connection
Section titled “Check the connection”Ask Claude Code:
List my WeHarness workspaces.
It calls project_inspect. In the WeHarness app, Connect MCP now lists Claude Code with when it was last used.
Then try, in your project’s folder:
Review this project’s agent layer with WeHarness.
Claude Code connects the folder with project_connect_local, sends its text files and reviews them. See Your local project.
Prompts
Section titled “Prompts”Type / in Claude Code: WeHarness’s prompts are listed as /weharness:review (MCP) and so on. Typing /mcp__weharness__review runs the same prompt. Arguments go after the command, separated by spaces. See Prompts.
Add the skill (optional)
Section titled “Add the skill (optional)”The skill for coding tools tells Claude Code when and how to use WeHarness. Copy its folder to ~/.claude/skills/weharness/, or to .claude/skills/weharness/ in one project.
Remove WeHarness
Section titled “Remove WeHarness”claude mcp remove --scope user weharnessRemoving it from Claude Code does not end its sign-in with WeHarness. To stop it at once, select Disconnect beside it in Connect MCP.