Developer Tools

petal.build

Provides information and usage details for petal_components, a UI component library for Phoenix LiveView.

1 endpoint3 known toolsFirst detected June 5, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.petal.build/mcp

No auth detected

Capabilities

tools

Get the canonical steps for installing petal_components in a Phoenix project.

Inferred read-only

List every component shipped by petal_components, the shadcn-style component library for Phoenix LiveView.

Inferred read-only

Get the full schema for one petal_components component: attrs, slots, defaults, allowed values, and a working HEEx usage example.

Inferred read-only

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.petal-components-mcp]
url = "https://mcp.petal.build/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "petal-components-mcp": {
      "type": "http",
      "url": "https://mcp.petal.build/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: petal-components-mcp
Remote MCP URL: https://mcp.petal.build/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "petal-components-mcp": {
      "url": "https://mcp.petal.build/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "petal-components-mcp": {
      "type": "http",
      "url": "https://mcp.petal.build/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "petal-components-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.petal.build/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for petal.build was fetched 2026-07-29T15:03:55.823Z and is being refreshed.

Trust status Trusted

petal.build is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.