Petal Components is a remote MCP server that gives an AI agent 3 tools, among them get_component, get_install_instructions, list_components. It answers at https://mcp.petal.build/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_component | 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 Inputs: name |
get_install_instructions | 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 in |
list_components | 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 han |
Every block below points at https://mcp.petal.build/mcp. Pick your client and copy.
claude mcp add --transport http petal-components https://mcp.petal.build/mcp
{
"mcpServers": {
"petal-components": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.petal.build/mcp"]
}
}
}{
"mcpServers": {
"petal-components": {
"url": "https://mcp.petal.build/mcp"
}
}
}{
"servers": {
"petal-components": {
"type": "http",
"url": "https://mcp.petal.build/mcp"
}
}
}{
"context_servers": {
"petal-components": {
"url": "https://mcp.petal.build/mcp"
}
}
}{
"mcpServers": {
"petal-components": {
"serverUrl": "https://mcp.petal.build/mcp"
}
}
}{
"mcpServers": {
"petal-components": {
"url": "https://mcp.petal.build/mcp"
}
}
}name: Petal Components
version: 0.0.1
schema: v1
mcpServers:
- name: Petal Components
type: streamable-http
url: https://mcp.petal.build/mcp{
"mcpServers": {
"petal-components": {
"httpUrl": "https://mcp.petal.build/mcp"
}
}
}{
"mcpServers": {
"petal-components": {
"type": "http",
"url": "https://mcp.petal.build/mcp"
}
}
}{
"mcpServers": {
"petal-components": {
"url": "https://mcp.petal.build/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.petal.build%2Fmcp&type=streamable_http&id=petal-components&name=Petal%20Components
It answered our last check on 23 October 2026 in 141 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 17 September 2026: get_component, get_install_instructions, list_components.
It answered our last check on 23 October 2026 in 141 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.petal.build/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.petalframework. Endpoint host: mcp.petal.build. ARD identifier: urn:air:io.github.petalframework:mcp:petal-components-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.