io.github.petalframework/petal-components-mcp
io.github.petalframework/petal-components-mcp · v0.1.0
Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
MCPremotelocal · npmno credentialsDeveloper tools
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 95/100
What it does: 3 tools · 3 read, 0 write
Test call list_components: worked (1,042 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://mcp.petal.build/mcpPackage
registry: npm
identifier: petal-components-mcp
version: 0.1.0
transport: stdioTools
3 tools listed at 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 instructions covering mix.elist_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 instead of training-data g
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.petalframework/petal-components-mcp)