Other MCP clients

These steps follow each tool’s own documentation, as Connect MCP shows them. WeHarness has not yet tested these tools end to end; see Compatibility.

OpenCode

Add WeHarness to opencode.json:

{
  "mcp": {
    "weharness": {
      "type": "remote",
      "url": "https://mcp.weharness.io/mcp",
      "enabled": true
    }
  }
}

Sign in:

opencode mcp auth weharness

opencode mcp list shows the server’s status, and opencode mcp logout weharness removes OpenCode’s stored sign-in.

Hermes

Add WeHarness to ~/.hermes/config.yaml:

mcp_servers:
  weharness:
    url: "https://mcp.weharness.io/mcp"
    auth: oauth

Sign in:

hermes mcp login weharness

OpenClaw

openclaw mcp set weharness '{"url":"https://mcp.weharness.io/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login weharness

Any other MCP client

Use these settings:

Server URL	https://mcp.weharness.io/mcp
Transport	Streamable HTTP
Authentication	OAuth 2.1 with PKCE (S256)

Your client must support:

• Discovery. A call without a token gets 401 Unauthorized with a WWW-Authenticate header that points to https://mcp.weharness.io/.well-known/oauth-protected-resource/mcp. That metadata names the sign-in service, https://auth.weharness.io/realms/weharness, and the scope mcp.
• Dynamic client registration (RFC 7591) at the sign-in service, with a redirect back to your own machine: http://localhost or http://127.0.0.1, on any port. Redirects to other hosts are refused, except the known callbacks of a few tools that sign in from the web.
• PKCE with S256, and the mcp scope in the authorization request.
• Refresh tokens, so it stays signed in while you use it.

See Sign-in and disconnect for what happens at each step.

After you sign in, ask your client to list your WeHarness workspaces. It appears in Connect MCP as soon as it connects.