Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
95.5% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
petalframework/petal-components-mcp
GitHub Stars
1
Server Listing
petal-components-mcp
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: list_components enumerates the catalog, get_component fetches one component's schema, and get_install_instructions handles setup. There is no plausible way to confuse these operations.

Naming Consistency5/5

All three names follow a consistent verb_noun pattern (get_component, get_install_instructions, list_components). The convention is predictable and readable.

Tool Count5/5

Three tools is well matched to a focused component-library reference server: discover, inspect, and install. Each tool earns its place without redundancy.

Completeness4/5

The surface covers the core workflow of listing components, inspecting schemas, and installing the library. Minor gaps exist around searching or filtering components by attribute, but agents can work around this via list_components plus get_component.

Available Tools

3 tools
get_componentAInspect

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.

Inputs: name (required).

get_install_instructionsAInspect

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, plus an optional step that keeps the petal_components usage rules synced into CLAUDE.md or AGENTS.md with the usage_rules package. Steps are idempotent - safe to follow on a project that is partially configured.

Inputs: no named parameters.

list_componentsAInspect

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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.