Skip to content
MCP server

petal-components-mcp

By petalframeworkAll Petal servers

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

Listed on

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

3
Directories
2 via MCP Toplist
3
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
1
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
get_componentGet 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.Not declared
get_install_instructionsGet 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 follow on a project that is partially configured.Not declared
list_componentsList 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.Not declared

Directory listings

DirectoryListingTierFirst seen
Official MCP Registryio.github.petalframework/petal-components-mcp-2 Oct 2026
GlamaListed there according to MCP Toplist’s dataset; not collected by InvokeRank.
PulseMCPListed there according to MCP Toplist’s dataset; not collected by InvokeRank.