Skip to main content
Glama
petalframework

petal-components-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoThe port to run the MCP server on8765

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_componentsA

List every component available in petal_components (the Shadcn-style Phoenix LiveView component library). Use this first to see what's available before composing HEEx markup.

get_componentA

Get the full schema for a single petal_components component — attrs, slots, defaults, allowed values, and a HEEx usage example. Call this any time you're about to write a Phoenix LiveView component reference like <.pc_button> or <.input>, to ensure the attrs and slots match the real library.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a distinct purpose: list_components provides an overview, get_component provides detailed schema for a single component. No overlap.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern in snake_case (list_components, get_component), which is predictable and clear.

Tool Count4/5

Two tools is minimal but appropriate for the server's read-only purpose of querying component schemas. A few more tools (e.g., search) could enhance, but not essential.

Completeness5/5

Covers the full lifecycle of accessing component information: listing all components and retrieving detailed schema for one. No gaps for the intended use case.

Maintenance

ActivityActive
ResponsivenessNo issues