shads.app
Open builder →

shads.app docs

Connect Codex to shads

One command (CLI and IDE share config). Set up the shads.app MCP server in Codex, check the connection, and use it to install shadcn/ui themes.

Open theme builder → All MCP clients

Install

Or run:

codex mcp add shads --url https://mcp.shads.app

Or edit the config file by hand:

~/.codex/config.toml (or .codex/config.toml in a project)

[mcp_servers.shads]
url = "https://mcp.shads.app"

The CLI and the IDE extension read the same file.

Add your API key (optional)

Skip this for public themes. Pro adds your saved themes and AI generation.

Create a key in Account settings → API keys (Pro plan). Keep it out of git.

Export SHADS_API_KEY in your shell profile, then use:

[mcp_servers.shads]
url = "https://mcp.shads.app"
bearer_token_env_var = "SHADS_API_KEY"

Check that it works

Restart Codex and run /mcp in the TUI.

Then ask your assistant:

Use the shads MCP server and run connection_status.

It returns the server version, whether your API key was accepted, and which tools are unlocked.

Try it

  • Use shads to install the Workspace theme in this repo.
  • Use shads to list the starter themes.
  • Use shads to validate this theme.json.

More jobs: recipes.

Troubleshooting

  • Codex says the key environment variable is unset. Apps launched from a desktop launcher do not inherit your shell variables. Export the variable where Codex starts, or put the key in http_headers instead.

More general fixes: MCP troubleshooting. Vendor documentation: Codex MCP docs (checked 2026-10-19).