Developer · Remote MCP server

Petal Components MCP

Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.

Visit Petal Components MCP's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.petalframework/petal-components-mcp
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-05-14
Updated
2026-05-14
Publisher
petalframework (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/petalframework) · how
Website
petal.build/components/mcp
Repository
github.com/petalframework/petal-components-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.petal.build/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
petal-components-mcp 0.2.0 · protocol 2025-06-18
Tools discovered
3: get_install_instructions, list_components, get_component
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npmpetal-components-mcp0.1.0stdioNone declared

How to connect Petal Components MCP

Petal Components MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.petal.build/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: petal-components-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y petal-components-mcp@0.1.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "petal-components-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "petal-components-mcp@0.1.0"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Periphery Code AuditSwift code analysis with Periphery - detect unused code and improve code quality.Local · stdioMCP Bundle (.mcpb): zyntx-lab/periphery-mcp-server/releases/download
PerplexitySearch the web, generate AI responses, and create embeddings with real-time information.Local · stdioPyPI: mcparmory-perplexity
Perplexity Comet MCPBridge Claude Code with Perplexity Comet for autonomous browsing and tab management.Local · stdionpm: perplexity-comet-mcp
Perseus: MCP server and live context engineLive context MCP server: resolves git, services, and tests into agent context. Local-first, MIT.Local · stdioPyPI: perseus-ctx
petro-mcpMCP server for petroleum engineering: LAS logs, decline curves, PVT, petrophysics, volumetrics.Local · stdioPyPI: petro-mcp
petromcpLocal-first MCP server: read LAS well logs and DLIS files from your own disk.Local · stdioPyPI: petroleum-mcp
PetsonalityAn MBTI-powered terminal pet companion for Claude Code and OpenClaw.Local · stdionpm: petsonality
Petstore MCP ServerSwagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server.Remote · HTTPLive check: ✗ no handshakepetstore.run.mcp.com.ai