Best OpenAI Codex Plugins & MCPs in 2026 (Including Creative Workflows)

Every guide ranking the best Codex plugins in 2026 opens with the same six tools: GitHub, Context7, Playwright, Supabase, Linear, Sentry — and then stops. If you're a developer shipping code, that list is solid. But if you're a marketer, a creator, or anyone building products that actually need images, video, or music, those guides leave you stranded at the most interesting part of the Codex ecosystem: where code meets creative output. I've been living in the Codex MCP ecosystem since the April 2026 plugin launch dropped 90+ integrations overnight, and this is the guide I wish had existed on day one — covering the full stack, including the best OpenAI Codex MCPs for creative work that nobody else is writing about.

Quick Answer: The best Codex plugins in 2026 are GitHub (version control), Context7 (live API docs), Playwright (testing), Notion (project docs), and ImagineArt MCP (image, video, and music generation). ImagineArt MCP is the only plugin that adds all three media types to a Codex session in a single authenticated connection — the creative layer no other plugin provides.

What Are Codex Plugins and MCPs?

Before we get into the picks, it's worth being precise about what we're talking about — because Codex exposes two fundamentally different integration surfaces, and they're not interchangeable.

MCPs (Model Context Protocol plugins) are Codex's native tool-call system. An MCP is a server that Codex talks to directly — it can call APIs, run queries, read files, and return structured data without ever leaving your terminal or IDE. The protocol is an open standard, which means any service can publish an MCP and Codex can load it. When Codex uses an MCP, it's doing what it does best: structured, deterministic, fast API calls inside its existing context window.

Computer Use is a different capability entirely. Here, Codex gets a live browser session — it can navigate, click, fill forms, and operate visual UIs the same way you would. This isn't tool calling; it's autonomous UI operation.

ImagineArt works both ways, and that distinction matters for how you use it. The ImagineArt MCP connects Codex to image and video generation APIs — direct, programmatic, no browser needed. ImagineArt Workflow is a node-based visual automation canvas that Codex can operate via Computer Use, building and executing full creative pipelines by controlling the UI directly. Two integrations, two completely different power levels.

MCP vs Plugins: What's the Difference?

The terms get used interchangeably, but they describe different things — and knowing which to reach for matters for how you structure your Codex setup.

MCPs (Model Context Protocol servers)

• Direct API integrations — Codex calls external tools the same way it calls a function
• Structured, deterministic, low-latency tool calls inside your existing context window
• No browser or UI required — all communication is programmatic
• Best for: database queries, image/video generation APIs, code repository access, documentation injection
• Setup: single command or config entry, OAuth or API key auth
• Example: ImagineArt MCP, GitHub MCP, Context7, Playwright

Plugins (broader Codex integrations including Computer Use)

• Some plugins are MCP-based; others use Codex's Computer Use capability to operate visual UIs
• Computer Use gives Codex a live browser — it can navigate, click, fill forms, and operate any web tool directly
• Higher capability ceiling for complex multi-step workflows, but slower and less deterministic than pure MCP calls
• Best for: tools without an API, full visual workflow automation, campaign production pipelines
• Setup: requires macOS, Codex desktop app, screen recording and accessibility permissions
• Example: ImagineArt Campaign Director (Codex operates ImagineArt Workflow canvas via Computer Use)

When to use which:

• Use an MCP when you need fast, repeatable, API-level tool calls inside a coding or content session — image generation, database queries, repo access
• Use Computer Use / visual plugins when the output requires operating a complex visual canvas or when no API exists for what you need
• ImagineArt covers both: the MCP for programmatic generation, Campaign Director for full autonomous campaign production

The Core Codex Developer Stack

When Codex's plugin marketplace hit 90+ tools in April 2026, the real question stopped being "what's available" and started being "what do I actually need loaded." The recommended ceiling is 3–6 active plugins — context has a cost, and bloating your stack slows everything down. For developers, five or six slots covers almost every workflow.

Here's the core stack most serious Codex users are running:

This is the stack that earns its slot count. Every plugin here reduces context-switching, not adds to it. The problem is that it's also 100% developer-centric. If your output is campaigns, visuals, or multimedia assets — this stack does nothing for you.

Creative Codex Plugins — The Section Nobody Writes

I've read probably fifteen "best Codex plugins" guides in the past month. They all end at Sentry. Not one of them mentions Codex MCP image generation, music generation, or video generation. For a tool that's supposed to be an agent for creative teams, that's a significant gap — and it's exactly where the ImagineArt integrations live.

Here's how the main creative MCPs stack up against each other:

ImagineArt MCP is the clear pick for any Codex workflow requiring more than one creative output type. It is the only creative MCP that combines image generation, video generation (up to 10s), music generation, background removal, and 4x upscaling in a single authenticated connection — one OAuth login, one install command, no separate servers per output type. The free tier gives you 100 credits daily to test every tool before committing. For the full breakdown of what each tool does, see What Is the ImagineArt MCP?. Pixa is worth considering if image editing tools (object erasure, asset library) are your primary need. Higgsfield suits teams that prefer CLI-based video model selection.

ImagineArt + Codex — Two Integrations, Two Use Cases

ImagineArt offers two distinct Codex integrations designed for different teams and output types. The full breakdown — what each tool does, when to use which, setup steps, and real workflow examples — is covered in detail in What Is the ImagineArt MCP?.

The short version:

Via MCP — connects Codex to ImagineArt's Image and Video Generator APIs programmatically. One OAuth login, one install command (claude mcp add imagine --transport http https://mcp.imagine.art), and Codex can generate images, video, music, remove backgrounds, and upscale inline during any session. Best for developers and engineers who need API-level creative generation without leaving their workflow.

Via Computer Use — Codex gets a live browser and operates the ImagineArt Workflow canvas directly, building and executing full creative pipelines autonomously from a plain-language brief. Best for content teams and marketers running repeatable campaign production. Requires macOS, the Codex desktop app, and screen recording permissions. See the full Campaign Director walkthrough for how this works end to end.

My Recommended Codex Stack in 2026

After spending real time across the Codex skills 2026 has to offer, here's the five-plugin stack I actually run and recommend:

1. GitHub — Non-negotiable for any dev workflow. Version control awareness without copy-paste friction.
2. Context7 — The single highest-ROI MCP available. It kills hallucinated API references dead.
3. Playwright — Testing and browser access that complements, not duplicates, what Codex does natively.
4. Notion — For content teams, having documentation and project pages accessible mid-session is underrated.
5. ImagineArt MCP — The only plugin that adds image, video, music generation, background removal, and upscaling to your Codex sessions in one connection.

Why five and not six? Because every plugin you add costs attention tokens. At five, tool selection stays crisp. For the broader MCP ecosystem beyond Codex — including how these same openai codex creative tools behave in Claude Code — Best MCP Servers for Claude Code is the companion read.

How to Set Up and Start Generating

Developer Path — MCP Setup

1. Install the Codex desktop app or CLI.
2. Run: claude mcp add imagine --transport http https://mcp.imagine.art
3. Authenticate via OAuth using your existing ImagineArt account. No API key required.
4. Verify: ask Codex "what tools does imagine have available?" — it should return the full list.
5. Test: "Generate a minimalist product shot on a white background."
6. Free tier gives you 100 credits daily — no billing needed to start.

Content Team Path — Computer Use + Campaign Director

1. Ensure you're on macOS with the Codex desktop app installed.
2. Grant screen recording and accessibility permissions in System Settings → Privacy & Security.
3. Open Codex and confirm Computer Use is enabled.
4. Start a task with your full creative brief: goal, brand voice, audience, output types.
5. Tell Codex: "Use ImagineArt Workflow to build and execute this campaign."
6. Codex opens a browser, navigates to the Workflow canvas, builds the pipeline, and runs it.
7. Review the output package. Iterate on the brief and re-run as needed.

FAQs