Connect with hosted MCP

Hosted MCP is the preferred remote-agent path when your client supports MCP Streamable HTTP and browser OAuth. It is Beta: the connection contract is implemented, but named clients remain Provisional until Sift completes the deployed real-client suite.

Connect

1. In Sift, open Settings → Connect and copy the workspace MCP URL. Treat it as workspace metadata; do not publish it.
2. Add that URL to your client using its documented remote HTTP configuration.
3. Complete authorization in the browser. Review the workspace and requested capabilities before consenting.
4. Restart or reload the client’s MCP tool discovery.
5. Call contract.get, then call context.assemble with a harmless question. Confirm the result contains citations or an explicit coverage gap.

Caution

Never paste an access token into this site or a project file. OAuth happens between the client and Sift’s authorization server.

Optional write verification

Only after explicit user intent, create a clearly disposable record through brain.propose_write or the currently documented write tool. Confirm the acting user’s capability, then delete or supersede the test object in Sift. A successful read does not prove write permission.

Revoke and recover

Revoke the connection from the client’s MCP settings or Sift’s connection controls. If tools disappear, reload discovery, confirm the selected workspace, and reconnect. If OAuth is unsupported, use local MCP.