Petal Components MCP Server

MCP server for petal_components — Phoenix LiveView component schemas exposed to AI coding assistants.

Remote serverstreamable-httpTypeScript

What is the Petal Components MCP MCP server?

MCP server for petal_components — Phoenix LiveView component schemas exposed to AI coding assistants. Exposed over MCP by the petal components mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP server that exposes petal_components — the Shadcn-style component library for Phoenix LiveView — to AI coding assistants (Claude Code, Cursor, Windsurf, etc).

Its toolset

Everything the assistant can do here goes through one of these:

  • list_components — every component in the library with a one-line summary
  • get_component — full schema (attrs, slots, defaults, values, docs) + HEEx usage example

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Petal Components MCP's toolset — list_components, get_component — is a fair guide to whether it matches your workflow. It is maintained by petalframework; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Petal Components MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the petal components mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
list_componentsevery component in the library with a one-line summary
get_componentfull schema (attrs, slots, defaults, values, docs) + HEEx usage example

How to install the Petal Components MCP MCP server

{
  "mcpServers": {
    "petal-components": {
      "command": "npx",
      "args": ["-y", "npm"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Petal Components MCP to list components.
  • Use Petal Components MCP to get component.

Frequently asked questions

It connects Petal Components MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (list_components, get_component) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Petal Components MCP directly.