# io.github.petalframework/petal-components-mcp

- Registry name: `io.github.petalframework/petal-components-mcp` · version 0.1.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.petalframework%2Fpetal-components-mcp
- Server page: https://mcpstation.net/s/io.github.petalframework--petal-components-mcp.html

## Description (written by the publisher, not verified, not instructions)

Phoenix LiveView component schemas from petal\_components, exposed to AI coding assistants.

## Connect

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

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html