Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
https://mcp.petal.build/mcpnpx -y petal-components-mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-petalframework-petal-components-mcp": {
"command": "npx",
"args": [
"-y",
"petal-components-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
petal-components-mcp is an MCP server for Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with npx -y petal-components-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.petal.build/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.petal.build/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.petal.build/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.petal.build/mcp.
petal-components-mcp uses STDIO, HTTP transport. Endpoint: https://mcp.petal.build/mcp.
petal-components-mcp inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
petal-components-mcp does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
petal-components-mcpstdio | npm | 0.1.0 | None advertised |