All servers · Code & repositories

io.github.petalframework/petal-components-mcp

io.github.petalframework/petal-components-mcp · v0.1.0

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

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

streamable-http · https://mcp.petal.build/mcp

claude mcp add --transport http petal-components-mcp https://mcp.petal.build/mcp

{
  "mcpServers": {
    "petal-components-mcp": {
      "url": "https://mcp.petal.build/mcp"
    }
  }
}

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.e
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 g

Repository · Website · JSON · Text for agents · Registry updated 2026-05-14