Skip to content

ChatGPT — agent plugin

Validated on the create-as-plugin path in ChatGPT ("Créer en tant que plugin" — delete and re-create to re-add, no ZIP upload), 2026-11-04.

What this surface is

The plugin packages the remote MCP server together with a climate-awareness skill. It is created as a plugin in the host; nothing is uploaded from a laptop or a repository.

What it does and does not read

  • The plugin mirrors the live server. With no upload of any kind, the tool listing carried the server's current descriptions — including the two-call confirmation copy on all three write tools — and server-side tool changes propagated without a re-ingestion step (confirmed 2026-11-04).
  • The plugin manifests in the repository are not read by this path. The displayed version and the auth configuration are host-managed: bumping the manifest version and flipping its declared auth mode changed nothing observable on the surface. The ZIP-upload + version-bump + review-submission path was not exercised in this validation, so its semantics stay vendor-documented only and are not described here as working.

Sign-in, approval and confirmation

Sign-in and confirmation behave as on the custom connector: conversational two-step confirmation, with one clean consent attempt observed. ChatGPT's own approval gating on this surface is plugin-wide — one setting covering all tools, in contrast to claude.ai's per-tool policy. That host-level setting sits above the server's confirmation floor and does not replace it.