Claude web and ChatGPT

Not enabled yet

Claude on the web and ChatGPT cannot connect to WeHarness yet. Their sign-in is turned on only after a clean connect, use and disconnect test with each.

Both connect to remote MCP servers from their own servers, not from your machine. Their sign-in sends you back to a web address of theirs, which WeHarness’s sign-in service does not accept yet.

	What it needs	Where it stands
Claude on the web (a custom connector on claude.ai; the same connector serves Claude Desktop, mobile and Cowork)	The exact redirect https://claude.ai/api/mcp/auth_callback, dynamic client registration or a client ID metadata document, PKCE with S256, and requests from Anthropic’s addresses reaching WeHarness	The redirect is not accepted yet: WeHarness’s registration rules match hosts, not exact addresses, so they need exact-address matching first
ChatGPT (a developer-mode connector or app)	A stable redirect https://chatgpt.com/connector_platform_oauth_redirect when the sign-in service supports issuer identification (RFC 9207), otherwise a per-connection redirect copied from ChatGPT; dynamic client registration or a client ID metadata document; PKCE with S256	WeHarness’s sign-in service supports issuer identification, so ChatGPT should use the stable redirect. It is added only after a clean connect shows the address ChatGPT actually sends

Until then, use a coding tool that runs on your machine: Claude Code, Codex, Cursor, VS Code, Devin or another MCP client.

Want one of these first? Write to info@weharness.io.