MCP Upgrade - Your AI Agent Knows Every Component

Mcp upgrade your ai agent knows every componentMCP Upgrade: Your AI Agent Knows Every Component

Since we launched the MCP server, AI agents like Claude have been able to create and render Imejis.io designs. There was a catch, though: the agent had to already know what components exist and which properties they take. Get a property name slightly wrong and the render ignores it.

That catch is gone. The MCP server is now wired directly into the component registry, the same source of truth that powers the editor palette and the component library.

Whats newWhat's new

• list_component_types - a new tool that returns the full catalog. Called bare, it lists all 27 component types with descriptions, categories, and their ready-made styles. Called with a type, it returns the complete spec: every property with its allowed values and defaults, a sample design you can render as-is, override examples for the render endpoint, and the exact property overrides behind each style.
• A generated design guide. The get_design_guide tool's component documentation is now built from the registry at request time. When we ship a new component or property, every connected agent sees it immediately. The docs can't drift from the renderer, because they're generated from the same schemas the renderer validates against.

Why it mattersWhy it matters

Ask your agent for "a dark stats card with a revenue metric, a sparkline, and a QR code to the dashboard" and it can look up all three components, use real property names with valid values, and get the design right on the first try. Fewer silently-ignored properties, fewer retry loops, less babysitting.

If you've already connected the MCP server, there's nothing to update. It's the same server, now with better answers. New here? The server card has the connection details, and the tutorial on generating images with Claude walks through setup.