Solar MCP Server

An MCP server for the Solar framework (solarbuild). Gives AI agents live, runtime access to your component registry so they can discover, inspect, and validate Solar components without guessing.

Tools

• manifest — Returns a full JSON schema of every registered component: prop names, types, required fields, and valid values. Call this before generating any composition code.
• component — Returns the schema for a single component by name.
• validate — Validates a props object against a component's schema. Returns valid: true or a structured error with expected, received, and fix fields the agent can act on directly.

Usage

{
  "command": "npx",
  "args": ["solarbuild-mcp", "--components", "./components"]
}

Point --components at your components directory. The server imports each .js file, triggers registry.register(), and exposes the full manifest to the agent.

Why

When an agent builds UI with Solar, it should read the manifest first — not guess prop names. When it passes wrong props, it gets a structured ContractError with a fix field. This MCP server brings both capabilities into any MCP-compatible client (Cursor, Claude, etc.).

- npm: solarbuild-mcp
- Docs: docs.solarbuild.dev/docs/integrations/mcp