Skip to main content
Console’s authorization-code method requires a compatible public Client ID Metadata Document, S256 PKCE and exact MCP resource binding. It provides MCP-only tokens lasting at most one hour and no refresh token. A client’s support for remote MCP alone does not establish end-to-end compatibility; if its authorization flow cannot meet the contract, use a supported key-capable client. Never downgrade to anonymous paid access.

Prerequisites

  • A ChatGPT account and workspace role that can add custom MCP servers; availability and administrator controls are determined by OpenAI.
  • Compatible Console MCP authorization; no published Altss App Directory acceptance is implied.
Complete Console onboarding before protected paid use.

Connection steps

  1. In the current ChatGPT Plugins experience, choose Add custom MCP server; older workspaces may show Apps settings.
  2. Supply the Console MCP URL below and use the supported authorization method. Do not paste a Console key into an ordinary chat.
  3. Scan the actual tools, complete human authorization if supported, and test catalog discovery before any paid execution.
  4. If the client’s OAuth identity cannot satisfy Console’s contract, use the documented REST or key-capable MCP setup. Reauthenticate after token expiry.

Copy configuration

Agent instructions

Verify the connection

Inspect the live tool inventory and schema before quoting work. Keep the organization, permitted inputs, maximum charge and actual run/settlement separate. A successful connection is not a payment or an accepted execution.

References

Protocol guide · Specialized prompts