Connect, authorize and make your first call with Giggle in your AI assistant.
Add a remote MCP through ChatGPT Plugins and authorize with your existing Giggle account.
https://giggle.pro/mcpWith the preregistered director-chatgpt client, use https://chatgpt.com/connector_platform_oauth_redirect as the callback. Prefer dynamic registration for other callbacks.
The configuration below is a preregistered fallback for /mcp using director-local without a client secret. Prefer dynamic registration when your client supports it.
[mcp_servers.giggle-director]
url = "https://giggle.pro/mcp"
scopes = ["director:mcp"]
[mcp_servers.giggle-director.oauth]
client_id = "director-local"
callback_url = "http://127.0.0.1:8765/callback"
callback_port = 8765codex mcp login giggle-directorClients that support MCP OAuth dynamic client registration (DCR) can get a client ID automatically. Connect from MCP settings in Claude Code or Cursor and authorize in your browser. Use platform-specific preregistration for clients that require a fixed client ID.
Call Giggle AI Director list_models and list_canvases and show the available models and canvases. Do not create canvases or run paid generation.Choose one connection method per assistant to avoid duplicate plugin and direct MCP tools.
Both call the same MCP service. Manage plugins in ChatGPT Plugins and direct local connections in MCP settings or /mcp. This page does not offer a separate generation CLI.
Authorization and connection checks are free. Generation uses current team credits and your member quota. Switching teams affects subsequent calls. Estimate the cost before submitting.
Keep the task_id and continue polling. A client timeout does not mean generation failed. Avoid resubmitting; successful results sync to the canvas.
Complete OAuth, refresh the MCP connection or start a new chat, and select the correct plugin. Keep temporary tunnels running and update both server and client settings when the public address changes.