ChatGPT Dots: connection and validation

Estimated reading time: 4 minutes

Validation pending · Reviewed 2026-11-17

Hosted always-on assistant whose dots use the plugins enabled for the account; a custom MCP server is added as a plugin that signs in through OAuth against a pre-registered Praesidia browser client. The path follows vendor documentation dated 2026-11-17 and is not live-verified by Praesidia.

Connect ChatGPT Dots through its hosted connector

Create a workspace for ChatGPT Dots Open ChatGPT Dots setup · Start with the free sample

  1. Create your free workspace and verify your email. On the dashboard, run the local allow/block sample and inspect the saved audit and actual signing status. This requires no model or external target; it does not connect a client or create independently verified proof.
  2. Return to your saved ChatGPT Dots setup and create its managed-mcp installation. The setup page shows the Praesidia MCP server URL and a nonsecret environment file; nothing is installed on a host. Configuration starts read-only.
  3. Register a browser OAuth client under Manage > Identity in your Praesidia workspace with the redirect URI the Plugin Creator shows. Ask a workspace administrator to allow creating plugins with custom MCP servers, open Plugins > Personal > Created by you > Plugin Creator, add the MCP server URL with OAuth and that client ID, complete the sign-in, then enable the plugin for the dot. Plugins accept OAuth or no authentication, never an API key.
  4. Load the creator’s scoped API credential only in the vendor’s secret or header field, never in a prompt or shared workflow. Run the one-use connection challenge from any shell with the same credential. Recorded credential proof does not attest a target effect.
  5. Make one harmless managed call from the assistant and inspect the server-returned action bound to this installation. A connector that shows the tools is not execution evidence.

The connector path follows the vendor’s public documentation as of 2026-11-17; Praesidia has not run a live acceptance against it. Tool calls transit the vendor’s hosted backend under the vendor’s terms and region. Free setup remains available; registered protected HTTP execution requires Enterprise approval workflows, enabled proof.actions, and the appropriate role and scopes. Advanced proof reads are a separate entitlement. Payments are currently unavailable. Provider usage may have separate charges.

Connection acceptance comes before a coverage claim

This distribution profile is separate from native runtime enforcement. Check the exact client version, transport, authentication, and tool surface with the operator. No marketplace listing or automatic interception is implied.

No tested installation recipe is recorded for this profile yet. Use the checklist below to prepare an evaluation; do not infer compatibility from an MCP label alone.

  1. Configure a dedicated test connection with minimum scopes. Never paste a runtime secret into a public workflow or repository.
  2. Discover the tools and allow only the intended tool set. Confirm the exact transport supported by your installed client.
  3. Make one harmless managed call. Check denial and revoked credentials; a client that continues after a failed policy hook does not enforce that hook.
  4. Inspect the action ID in Praesidia. Report whether the test covered a managed call, native interception, or observation only.
  • Only the explicit Praesidia MCP tools exposed by the plugin are governed; other plugins and native tools stay outside this boundary.
  • Plugin authentication is OAuth or none. API keys are not accepted, so register a browser OAuth client under Manage > Identity first; Praesidia does not offer dynamic client registration.
  • Workspace administrators must allow creating plugins with custom MCP servers; the permission is off by default. Enterprise enables plugins by default from 2026-11-18.
  • Pro tiers are not sold in the EEA, UK or Switzerland as of 2026-11-17; check plan availability for the region.
  • Connector path per vendor documentation as of 2026-11-17; no Praesidia acceptance run exists yet, so no evidence grade is claimed.

SDK setup · Inspect evidence · Runtime catalog