io.github.petalframework/petal-components-mcp · v0.1.0 · design
io.github.petalframework/petal-components-mcp is healthy: it completed an MCP handshake in 3027 ms and exposes 3 tools.
Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
Endpoint: https://mcp.petal.build/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 3027 ms |
| Last checked (UTC) | 2026-10-15T06:25:43.567Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T06:25:43.567Z | Healthy | 3027 |
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 |