ChatGPT — custom connector

Validated on web ChatGPT in a browser, 2026-11-04.

Add the server

1. Open the plugin/connector surface on chatgpt.com and add a custom MCP server ("Ajouter un serveur MCP personnalisé") with URL https://mcp.bloomy.earth/mcp.
2. The add form shows a registration-method selector ("Méthode d'enregistrement"); this host auto-detected the server's published client-ID-metadata-document lane and took it.
3. Acknowledge the custom-server risk warning to proceed.

Sign in

Adding the server does not authenticate. OAuth starts on your first tool invoke: ChatGPT prompts the connection sign-in, which opens the Bloomy consent page, where you sign in with your own Dashboard → Integration API credentials. This client requests mcp:read mcp:write (no offline_access) — builder-configured at add time.

If a consent attempt ends with a generic "connection not completed" toast, retry once. Validation saw exactly one such first-attempt failure that succeeded on the second try; its post-approval redirect was never directly observed, so it is recorded as a single non-reproducing edge transient rather than a settled cause.

Tool listing and refresh

Tool changes on the server can be picked up with the connection's "Actualiser les outils" (refresh tools) control — no reconnect was needed (observed). The listing showed all seven tools grouped Write 3 / Read 4, following the server's tool annotations, with the full descriptions visible. Per-parameter schemas are not shown by this host.

Confirmation

Confirmation on this host is conversational two-step: the assistant relays the server's not-executed summary and the one-time code as ordinary text. No native popup and no elicitation form appeared, matching this host's documented posture — and the server's confirmation floor is what actually stops a write, independent of what the host renders.