Use Curio with Codex
Codex can build whole interfaces — but on its own it defaults to the same generic look as every other agent. Connect Curio and it can apply any of 2543 real design styles instead, consistently, without you writing a design spec by hand.
What this gives Codex
Curio runs a Model Context Protocol (MCP) server. Once Codex is connected, it gains tools to search the library, read a style's metadata, and fetch the full design spec — colors, typography, spacing, components, and rules — for whatever you are building.
It is sign-in based: you connect once with OAuth, no API keys to manage, and your AI asks you before spending a credit. The Codex CLI and IDE share the same ~/.codex/config.toml, so one entry covers both — and the same connection also works in Claude Code, Cursor, VS Code, and other MCP clients.
Connect over MCP
-
1
Add Curio to ~/.codex/config.toml
Add an MCP server entry pointing at https://mcp.designbycurio.com/mcp in your ~/.codex/config.toml. This file is shared by the Codex CLI and IDE, so both pick it up. The developer docs show the exact entry format.
-
2
Sign in with OAuth
On first connect, Codex opens the OAuth sign-in flow in your browser. Sign in with email, Google, or GitHub and approve. Connecting and browsing are free; unlocking a style costs 1 credit, once, and your AI asks you first.
-
3
Find a style
Ask Codex to search Curio — for example, "search Curio for a bold editorial style" — or name one directly, like Bauhaus or Stripe. It uses search_styles and get_style to pick a match.
-
4
Apply it to your build
Tell Codex to build in that style. It fetches the full spec with get_style_spec and generates your page, component, or deck using the style's exact tokens and rules.
What you get
Consistent output: every screen Codex generates holds the same look, because it works from one authoritative spec instead of re-guessing each time.
Real, distinct styles: hundreds of movements, brands, and traditions — not the generic default — so your work stops looking AI-generated.
No file wrangling: you never hand-write or hunt for a DESIGN.md; Codex fetches it live over MCP.
Example prompts
Search Curio for a clean fintech style and rebuild this dashboard component in it.
Use the Memphis style from Curio to build the landing page hero for this product.
FAQ
Does the CLI and IDE need separate setup?
No. The Codex CLI and IDE both read ~/.codex/config.toml, so a single MCP server entry there covers both. You only sign in once.
Does fetching a style cost anything?
Only the first time. Unlocking a style costs 1 credit, once — the same unlock as on the website — and your AI asks you before spending it. After that, fetching that style is free, and searching and reading introductions are always free.
Does this work in other tools too?
Yes. The same MCP endpoint works in Claude Code, Cursor, VS Code, ChatGPT, and other MCP-capable clients. See the developer docs for per-client setup.