How do I connect the SaSame MCP to Claude Code?

Public, keyless:

claude mcp add --transport http sasame-public https://live-vps.sasame.online/public-mcp

Knowledge, keyless:

claude mcp add --transport http sasame-knowledge https://srl-sasame.com/api/mcp

Authenticated account:

claude mcp add --transport http sasame-account https://live-sasame.sasame.online/mcp

The authenticated server uses the client OAuth flow. Complete Continue with Google in Account Control, select the intended organization and approve consent when Claude Code opens the authorization flow.

Run claude mcp list and confirm that sasame appears with the expected URL. Start or restart the Claude Code session if the active session does not refresh its MCP list automatically.

For sasame-public, call start_here. For sasame-account, call session_info and account_status; verify the returned organization. Tool listing alone proves discovery, not a completed OAuth exchange or successful tool call.

If the server is absent, rerun the command and inspect the CLI error without adding credentials. If a stale entry uses another URL, remove or replace that entry through the current Claude Code MCP management commands, then verify again. Never point this configuration at the private Owner MCP host.

The command adds a client configuration only. It does not modify the current repository, create an SaSame account or authorize mutating Owner tools.