How do I connect SaSame to another MCP client?

The client must support remote MCP over Streamable HTTP. A client that accepts only local stdio servers or a legacy transport may require different configuration or may not be compatible. Use the client’s current documentation as the authority for its configuration shape.

A common configuration shape is:

{
  "mcpServers": {
    "sasame-public": { "type": "http", "url": "https://live-vps.sasame.online/public-mcp" },
    "sasame-knowledge": { "type": "http", "url": "https://srl-sasame.com/api/mcp" },
    "sasame-account": { "type": "http", "url": "https://live-sasame.sasame.online/mcp" }
  }
}

The public and knowledge servers are keyless. The account server requires an OAuth 2.1 client with PKCE and opens Google-backed Account Control consent. If the client cannot complete remote OAuth, use only the keyless surfaces; never copy a bearer token into static configuration.

For the public server, call start_here. For the authenticated server, complete OAuth and call session_info followed by account_status. Confirm a real JSON-RPC response and the intended organization before treating installation as complete.

A 401 from the public URL usually means the wrong endpoint was configured. A 401 from the account URL means OAuth has not completed or the token is invalid. No tools often means the client did not refresh, lacks Streamable HTTP/OAuth support, or rejected its own configuration schema. Record the exact client/version and error before changing endpoints.

Do not add a token to the public configuration. The public surface is intentionally bounded and keyless; private account or Owner operations use separate authenticated surfaces.