Boot cladding as an MCP server over stdio. Use only when the user wants to expose cladding's tools, resources, and persona prompts to a separate MCP client. Most users don't run this directly — the plugin's .mcp.json launches it automatically.
Installs into .claude/skills of the current project.
Are you the author of Serve?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/qwerfunch-serve)
---
description: Boot cladding as an MCP server over stdio. Use only when the user wants to expose cladding's tools, resources, and persona prompts to a separate MCP client. Most users don't run this directly — the plugin's .mcp.json launches it automatically.
---
# Cladding serve
Run `clad serve` from the project root. Boots an MCP server over stdio that exposes:
- **Tools**: `clad_list_features`, `clad_get_feature`, `clad_run_check`, `clad_get_events`.
- **Resources**: `cladding://spec`, `cladding://events`, `cladding://audit`.
- **Prompts**: 5 personas (orchestrator, librarian, reviewer, observability, specialists).
- **Live audit notifications**: `notifications/resources/updated` fires for `cladding://audit` whenever a new evidence entry lands — a subscribed client can live-tail the audit log without polling.
Registers itself in cladding's sampling context so the host adapters (`generic-mcp`, `claude-code`) route LLM dispatch through `McpSamplingTransport` instead of the Mock fallback.
```
clad serve --cwd /path/to/project
```
**Most users don't run this directly.** Cladding's plugin manifest (`.mcp.json`) launches `clad serve` automatically when the plugin is enabled. Invoke this skill only for debugging the MCP server in isolation.
