Skip to main content
On ChatGPT web, you can create a personal plugin from Capsulate’s remote MCP server. Workspace permissions may restrict custom plugins. A public directory listing is not required for a personal test connection.
  1. Open Plugins → + → Add custom MCP server.
  2. Name it Capsulate. Set Server URL to https://capsulate.app/mcp.
  3. Choose OAuth. For CIMD, choose the public-client (none) option; Capsulate does not support private-key client assertions. DCR is also supported when configured by your host.
  4. Create the plugin, then install it from your personal plugins.
  5. Sign in to Capsulate, check the account shown on consent, and approve the requested scopes.
  6. In a new conversation, select the Capsulate plugin with @ and first ask it to list your Canvases.
For staging acceptance, use https://staging.capsulate.app/mcp and a staging account. The updated backend and migrations must be deployed first. Refresh the plugin’s tools after deployment. Staging browser sign-in may also require the tester’s Cloudflare Access login; protocol discovery must remain reachable from the actual assistant host. A Dot can use supported plugins installed and enabled for your account. Install this connection through ChatGPT; a Codex CLI configuration alone does not install a Dot plugin. Actual Dot read/write approval compatibility must be tested before claiming support. If Capsulate is available in your Plugins directory, you can also install that listing and complete the same account consent flow. Capsulate uses OAuth with PKCE. Do not paste a password or bearer token into ChatGPT. OAuth permission does not approve an individual write: the host must also handle Capsulate’s exact-argument write confirmation. Manage or revoke the connection from Capsulate → Settings → Connect AI. Disconnect revokes current access/refresh tokens and outstanding authorization codes. Signing out of the app alone does not disconnect existing OAuth clients. See OpenAI’s custom MCP setup and Dot app connections.