How do I connect the SaSame MCP to ChatGPT?
Current setup and verification steps for using the SaSame remote MCP from ChatGPT.
- Collection
- documentation
- Updated
- 2026-08-24
- min read
- 4
Create a custom MCP app using either the keyless public endpoint or the Google-authenticated account endpoint, scan tools, enable the app and verify a real call.
Before you begin
Custom MCP apps depend on the current ChatGPT plan, workspace role and administrator policy. Use ChatGPT on the web for the setup flow described here. If developer mode or app creation is unavailable, the account or workspace is not currently eligible.
Choose the SaSame surface
For public discovery and audits, use https://live-vps.sasame.online/public-mcp and select no authentication. For site knowledge, use https://srl-sasame.com/api/mcp and select no authentication. For account and organization tools, use https://live-sasame.sasame.online/mcp and choose OAuth when ChatGPT detects the server metadata. During Scan Tools, complete Continue with Google in Account Control, select the intended organization and approve consent. Do not reuse an app configured for one surface as if it represented the other.
Create the app
Open ChatGPT settings, enable developer mode, go to Apps and create a custom MCP app. Enter a clear name such as SaSame, use https://live-vps.sasame.online/public-mcp as the MCP endpoint, select the no-authentication option for this public surface, then scan or refresh tools before creating the app.
Enable and verify
Enable the app in a new chat. On the public surface, call start_here. On the authenticated surface, call session_info, then account_status; verify that the selected organization is the one returned before using Factory or billing tools.
Common failures
If Scan Tools fails, verify the exact HTTPS URL and retry without adding an API key. If the app exists but no tools appear in chat, confirm that it is enabled for that conversation. If controls are missing, ask the workspace administrator whether custom apps or developer mode are disabled.
Data and authority boundary
The endpoint is keyless and public. Connecting it does not create a Factory account, claim an MCP, start a subscription or grant access to the private Owner MCP. Tool arguments sent by the client are processed according to the public tool contract.
Examples
1- 01
After setup, ask: “Use SaSame to call start_here and show the shortest path for auditing a live MCP.”