ChatGPT plugin and Codex

The Kreel plugin for ChatGPT, kreel-chatgpt, connects ChatGPT to the same remote MCP server documented in Connect over MCP (https://api.kreel.ai/mcp), and bundles Kreel’s prompt library as agent-invoked skills - the ChatGPT equivalent of the Claude Code plugin’s slash commands. Codex doesn’t get the packaged plugin yet: it connects directly over MCP, with the tools but not the skills (see step 3 below).

Plugin vs. MCP connection

As with the Claude Code plugin, these are two separate things. The MCP connection is what lets ChatGPT reach your Kreel data at all. The plugin is a packaged layer on top of that connection: OpenAI-directory discoverability plus ready-made skills, instead of you adding the connector URL and typing prompts by hand.

Before you start

You need one of:

• ChatGPT, on a plan and workspace where plugins are available. Developer mode is only needed for the fallback below.
• Codex (CLI or desktop app).

Install

1. ChatGPT, via the Plugins Directory (recommended): open the Plugins Directory, search for Kreel, open the listing, and select Try in chat. Approve the Kreel OAuth login when prompted. Directory availability can depend on your workspace’s admin policy.
2. ChatGPT fallback, via Developer mode: ask a workspace administrator to enable Developer mode (Settings → Security and login), then go to Settings → Plugins, select the add button, and create a developer-mode app pointed at https://api.kreel.ai/mcp. Sign in through the Kreel OAuth screen when prompted. Use this path when the directory listing is hidden by workspace policy, or to diagnose a directory-install issue.
3. Codex CLI or desktop app: add Kreel as a remote MCP server in Codex’s MCP settings, with the server URL https://api.kreel.ai/mcp. Codex prompts an OAuth login to your Kreel account on first use. The packaged skills aren’t distributed for Codex yet, so in Codex you get the MCP tools and ask for the prompt library’s workflows in your own words.

Note

OpenAI’s plugin directory is available across ChatGPT plans. Whether you can install a plugin depends on your plan, workspace settings, role and region; see OpenAI’s help article “Plugins in ChatGPT and Codex”.

What you’re approving

Like the direct MCP connection, signing in creates a read connection by default. The write scope - needed for the Brand Knowledge Base write tools and publish_report - is optional and requested separately; see Connect over MCP for what each scope covers.

What it ships

The plugin ships one skill per prompt in Kreel’s prompt library - the same 23-prompt catalog documented in the prompt library and shipped as slash commands by the Claude Code plugin, generated from the same source so all three surfaces stay in sync.

Skill names are prefixed kreel-, mirroring the Claude Code plugin’s /kreel:* command names without the slash, for example kreel-daily-pulse, kreel-weekly-report, and kreel-tiktok-account-audit. Because ChatGPT skills are model-invoked rather than typed as slash commands, you don’t run them by name - just ask for what you want (for example “run my Kreel daily pulse” or “give me the Kreel weekly report for last week”) and the agent selects and fills in the matching skill. Skills that take an argument in the prompt library (like week_of on kreel-weekly-report) prompt the model to collect that value from you before running.

Draft skills never publish anything

The three draft skills - kreel-draft-google-rsa, kreel-draft-klaviyo-campaign, and kreel-draft-meta-ads-from-folder - only read your performance data and return copy for you to paste into Google Ads, Meta, or Klaviyo yourself. They do not create, upload, change, schedule, activate, or send anything on those platforms.

Need help?

Email support@kreel.ai.