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": {
      "type": "http",
      "url": "https://live-vps.sasame.online/public-mcp"
    }
  }
}

Some clients use different field names. Preserve the endpoint and remote HTTP transport semantics rather than copying unsupported fields blindly.

Restart or refresh the client if required, inspect the discovered tools, then call start_here. Confirm a real JSON-RPC response from SaSame before treating the installation as complete.

A 401 usually indicates that the private Owner endpoint was used instead of the public endpoint. No tools often means the client did not refresh, does not support Streamable HTTP, or rejected its own configuration schema. Record the exact client/version and error before changing the endpoint.

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.