How do I connect the SaSame MCP to Claude?

On supported individual plans, open Customize or Settings, then Connectors and Add custom connector. In Team or Enterprise organizations, an owner may first need to add the custom Web connector from organization settings. The exact controls depend on the plan and workspace role.

Use https://live-vps.sasame.online/public-mcp without authentication for public discovery and audits. Use https://srl-sasame.com/api/mcp without authentication for site knowledge. Use https://live-sasame.sasame.online/mcp for an organization-bound account connection. Claude supports OAuth-based remote connectors: click Connect, continue with Google in Account Control, select the intended organization and approve the scopes. Keep the connectors separately named so their authority is obvious.

Name the connector SaSame and use https://live-vps.sasame.online/public-mcp as the remote MCP URL. This is a cloud-brokered remote connector, not a local claude_desktop_config.json stdio server. No SaSame credential is required for the public surface.

Enable SaSame from Search and tools. For the public connector, call start_here. For the authenticated connector, call session_info and account_status, and verify the returned organization before using Factory or billing tools.

If Add custom connector is unavailable, check plan eligibility or organization policy. If the connector was added but is not used, enable it for the current conversation. If tool discovery fails, verify the URL and that the connector type is remote Web MCP rather than a local server configuration.

The public connector is keyless. It does not expose private Owner tools, create paid entitlement or transfer repository credentials. Claude decides when to propose or invoke tools, and the user remains responsible for reviewing sensitive arguments.