PODIE MCP for Codex & Claude Code
PODIE MCP lets Codex and Claude Code search a curated React UI library, recommend components and app templates, retrieve their source and prepare installation commands. Your editor applies the selected UI to your local project. You do not need to remember tool names.
Connect once. Then ask for the UI you need.
- Sign in to PODIE and open Connect PODIE MCP.
- Choose Codex or Claude Code and click Copy setup prompt.
- Paste it into your editor. The prompt asks it to preserve existing settings and add PODIE to your user-level MCP configuration.
- If the editor requests a server reload, complete that step. Then ask for a component. The PODIE dialog shows Connected · tool call confirmed only after a successful tool call.
Use PODIE to find 3 UI components that fit this project. Show previews and explain the fit before installing.After choosing one:
Install the second option. Keep this project's package manager and existing design. Integrate it into the page, then run the type check and production build.What happens between a request and a working component?
- Search and recommend
- The agent searches published entries and can ask PODIE for recommendations using a short design brief. Results link to real preview pages.
- Inspect
- It reads the selected source, dependencies and license before adapting anything. A native React component and an isolated scene wrapper have different integration boundaries.
- Install and verify
- PODIE returns a shadcn-compatible installation plan. Your editor runs it with your authorization, imports the component and checks it in your application.
The remote MCP server cannot modify your filesystem or run a shell on your computer. A successful search proves the connection works; it does not prove the component has been installed. Accept the result only after seeing it run in your project.
Which MCP tools are available?
search_catalog: find components or Apps.recommend_ui: get suggestions for a non-sensitive brief. If the model is unavailable, explicitly labeled catalog matches are returned.get_component: inspect source and dependencies.get_install_plan: get the command for your package manager.report_installation: optionally record outcomes for a tracked installation, with permission. These are client-reported results.
How is this different from a shadcn registry?
A registry delivers source files and dependencies. PODIE MCP adds catalog search, recommendations and installation plans to the editor conversation. It uses shadcn-compatible delivery; it is not the official shadcn MCP server. You can also install directly without MCP using the CLI guide.
Connection troubleshooting
- Saved configuration, but no tools: reload the server using your editor's supported controls, then send the first request above. Saving a file alone is not a connection test.
- Waiting for your editor: no successful call has arrived for this token yet. Use Check connection in the dialog.
- Expired token or 401: copy a fresh setup prompt and update the editor. Tokens expire after 30 days; reconnecting replaces that editor's previous token.
- 403 before the tool runs: distinguish an edge/network block from an MCP authentication error. Check the native editor connection; share a redacted error when reporting the issue.
- Installation or styling failed: check aliases, dependencies and styles in the installation guide. A preview is not proof of compatibility with every project.
What is sent to PODIE?
Keep private source, credentials and customer data in your project. Send only a short, non-sensitive design brief and stack. Model recommendations send that brief and public catalog metadata to AtlasCloud. The setup prompt contains a private, revocable account token; keep it in user-local editor settings, outside source control. Disconnect an editor from the connection dialog to revoke access.
Browse App templates, component guides or the live library. Editor configuration details: official Codex MCP documentation and official Claude Code MCP documentation.
Last updated: .