Skip to content

io.github.petalframework/petal-components-mcp

by petalframework · remote · local (npm) · no sign-in to list tools · v0.1.0 · published by GitHub user petalframework

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

Read only
CompareRegistry entry

3 tools: 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Only reads 3Claude Code: allow
  • get_componentGet the full schema for one petal_components component: attrs, slots, defaults, allowed values, and a working HEEx usage example.No findings

    Why it is in this group

    • The name "get_component" says "get": a word for reading.
    Description, as the server wrote it
    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 guesses.
  • get_install_instructionsGet the canonical steps for installing petal_components in a Phoenix project.No findings

    Why it is in this group

    • The name "get_install_instructions" says "get": a word for reading.
    Description, as the server wrote it
    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.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to follow on a project that is partially configured.
  • list_componentsList every component shipped by petal_components, the shadcn-style component library for Phoenix LiveView.No findings

    Why it is in this group

    • The name "list_components" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__petal-components__get_install_instructions",
      "mcp__petal-components__list_components",
      "mcp__petal-components__get_component"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as petal-components. Review it before you use it.