Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
Connect Remote server
claude mcp add --transport http petal-components-mcp https://mcp.petal.build/mcp
{
"mcpServers": {
"petal-components-mcp": {
"url": "https://mcp.petal.build/mcp"
}
}
}
{
"servers": {
"petal-components-mcp": {
"type": "http",
"url": "https://mcp.petal.build/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.petal.build/mcp
Tools 3 found in our last check
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 instru…
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.
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 inste…
Details
| Endpoint | https://mcp.petal.build/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| First published | 14 May 2026 |
| Last updated | 14 May 2026 |
| Registry name | io.github.petalframework/petal-components-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
