Skip to content

Sign-in and disconnect

Your coding tool signs in to WeHarness in your browser, with your own WeHarness account. It never sees your password, and you never paste a token into it.

  1. Your tool calls https://mcp.weharness.io/mcp without a token and gets 401 Unauthorized. The answer points to the server’s resource metadata, https://mcp.weharness.io/.well-known/oauth-protected-resource/mcp, which names the sign-in service (https://auth.weharness.io/realms/weharness) and the mcp scope.
  2. Your tool registers itself with the sign-in service (dynamic client registration). Registration accepts only redirects back to your own machine (localhost or 127.0.0.1, on any port) or to the known callbacks of a few tools that sign in from the web.
  3. Your browser opens WeHarness sign-in. You sign in (with two-step sign-in if it is on) and allow the access your tool asks for. Your tool must use PKCE.
  4. Your tool gets a token that works only for the WeHarness MCP server. A token issued for anything else is refused here, and this token does not work anywhere else. Your email address must be verified.

Your tool keeps its sign-in while you use it: up to 30 days without use, and 90 days at most. Then it asks you to sign in again. Your tool refreshes its token by itself in the meantime.

Connect MCP in the sidebar lists each tool you connected, by the name and version it gives, as soon as it connects after you sign in (most tools connect when they start). Each shows when it was last used and the last tool it called, or that it connected and has not used a tool yet.

Allowed at sign-in, never connected lists tools you allowed at sign-in that have not connected. They are not connections: nothing has used WeHarness through them. If one is not yours, use Sign out everywhere.

Select Disconnect beside it in Connect MCP. It stops at once: its next call is refused. If you use it again, it asks you to sign in.

Removing WeHarness from the tool’s own settings only removes it there; its sign-in with WeHarness stays until you disconnect it or it expires.

Settings → Account → Sign out everywhere signs you out of WeHarness on every device and ends the sign-in of every coding tool, including tools allowed but never connected. Each tool asks you to sign in again. See Account security.

  • You leave a workspace, or an owner or admin removes you: your tool’s next call to that workspace fails.
  • WeHarness staff end your MCP access, for example after a security report: your tool is refused until you sign in again.

Exactly what your role allows in each workspace, and never an approval. See The rules your tool works under.