DexThemes Codex Plugin and MCP App

DexThemes provides an MCP-backed interactive app and bundled skill for finding, creating, previewing, importing, collecting, and publishing Codex themes inside a supported conversation host. Use it in browser chat or open full-page Studio when the connected host offers that view. The capability exists in the repository and MCP endpoint; this page does not claim that DexThemes is approved, publicly listed, or available through every plugin distribution channel.

Anonymous and read-only capabilities

The public tool set works without DexThemes sign-in for:

• natural-language search across built-in Codex, curated DexThemes, and published community themes;
• fetching one exact theme by the stable ID returned from search;
• drafting a private dark, light, or paired theme from an idea;
• validating structure, exact colors, contrast, protected palettes, and optional public wording;
• rendering full Codex-style dark and light workspace previews;
• preparing the selected variant's import string and Settings handoff;
• viewing daily, weekly, monthly, and all-time public leaderboards; and
• preparing a best-effort redacted GitHub Issue draft.

These tools read public data or compute a private draft. Preparing an import can let the interactive card copy a string and open Codex Settings after user action, but it does not modify community data or silently apply the theme. Preparing an issue shows the exact draft and warning; it does not submit anything to GitHub.

In full-page Studio, Color Me Lucky creates a named dark-and-light draft for the current session. It remains private until a separate publication action; the button itself does not publish a theme or write account data. The full-page editor also lets you adjust the Background, Surface, Text, Accent, and Skill palette roles while previewing the draft. Preview rendering is a DexThemes simulation.

OAuth-protected personal tools

Account tools use OAuth with GitHub as the upstream identity. The implemented scopes divide access by purpose:

• themes:read allows personal creator stats and supported account unlocks.
• themes:write allows public-submission review and publication.

The stats view can show published theme totals, copies, likes, qualified adoptions, current ranks, repeat daily and weekly wins, finalized monthly Top 10 placements, and achievements. The unlock view can render supported reward themes for the signed-in account.

The resource server verifies the signed token and derives account identity from it. Personal and publication tool arguments do not accept a user ID, owner ID, email address, API key, or access token. If OAuth is unavailable or incomplete in a particular deployment or host, the public tools can still work while account-bound tools remain gated.

Publication is the only public write

In full-page Studio, one explicit Create & copy action starts the publication flow. Review the theme name, summary, and both dark and light palettes, choose the variant to copy, and activate the button once. Studio obtains the signed-in review and submits that same pair. It then fetches the returned theme ID and checks that the public record matches the reviewed ID, name, summary, and dark and light palettes. Only after that readback does Studio prepare and copy the selected Codex variant. This action does not open Settings or apply the import. If a returned theme ID cannot be confirmed, retry checks that record without resubmitting. If no confirmation is returned, check the community before taking further action. If clipboard access fails after confirmed publication, you can retry Copy for Codex.

Other submission-review screens retain a separate Publish action:

1. Validate the draft for public use.
2. Call the submission-preparation tool with themes:write.
3. Inspect the exact public name, summary, variants, and mockups in the app.
4. Press the app's Publish button.
5. Let the first-party app call submit_theme with a short-lived confirmation bound to the reviewed payload and current sign-in.

OAuth themes:write is the terminal publication authorization. The confirmation is not a value the model should invent or request: it preserves exact-payload continuity and expires after a short window, but it is not single-use and does not independently prove that a human pressed Publish. App visibility is presentation metadata rather than authorization. The server rechecks public wording, colors, protected palettes, identity, rate limits, and the exact payload before creating the community theme. The write creates a new theme under the verified identity; it cannot edit or delete another creator's theme.

Safe Codex apply handoff

For an existing theme, the app prepares a validated codex-theme-v1 string. Depending on the host surface, the user can copy it and request that generic Codex Settings open; in full-page Studio's confirmed Create & copy flow, the selected variant is copied directly after public readback. The user still chooses Appearance, chooses Import theme, pastes, and approves. Clipboard failure leaves the exact string available to copy again or select manually.

No plugin tool claims that opening Settings or copying a string proves the theme loaded.

Discovery and distribution limits

The MCP endpoint and installable repository bundle are implementation and testing surfaces. Whether a user can connect them depends on the host, account permissions, organization policy, and active distribution path. Capability in source is not evidence of marketplace approval or public directory listing.

The visual app adapts to compact host layouts, but preview rendering remains a DexThemes simulation. OAuth-protected features additionally depend on correctly configured authorization infrastructure. Public theme search may omit protected reward palettes and uses policy-clean public names for catalog items that need descriptive aliases.

DexThemes is community-built, open source, and not affiliated with OpenAI. It is an independent theme tool, not an official Codex or OpenAI plugin.