Other MCP client

This path describes a protocol contract, not verified compatibility.

Your client must support MCP Streamable HTTP, HTTPS, OAuth authorization-server discovery, browser authorization, and tool-list refresh. Add the workspace MCP URL from Settings → Connect, authenticate, refresh tools, then verify contract.get and a read-only grounded query.

If the client cannot complete OAuth, do not paste a bearer token unless Sift explicitly documents a safe scoped-token path for that client. Use local MCP instead.