PC

Petal Components MCP

io.github.petalframework/petal-components-mcp

Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.

Yes, your AI can use this right now.Answered a live MCP handshake in 400 ms with no sign-in needed and exposes 3 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://mcp.petal.build/mcp

3 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
get_install_instructions

Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks to install petal_components, when you are setting up a new Phoenix project that needs UI components, or when verifying an existing installation. Returns step-by-step instructions covering mix.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to

list_components

List every component shipped by petal_components, the shadcn-style component library for Phoenix LiveView. This is the canonical Phoenix UI vocabulary - call it before composing any HEEx so you reach for an existing component instead of hand-rolling Tailwind divs.

get_component

Get the full schema for one petal_components component: attrs, slots, defaults, allowed values, and a working HEEx usage example. Call this every time you are about to write a tag like <.button>, <.modal>, <.table>, or <.field> so the attrs and slots match the real library instead of training-data guesses.

Alternatives in Developer Tools

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”