# MCP server bootstrap kit for KittyClaw

This kit helps you coordinate an MCP server release with KittyClaw, from a sourced decision brief to a verified registry submission.

Use the files in this order:

1. `install-kittyclaw-workflow.ps1`: install the pipeline, columns, processor missions and routes through the documented KittyClaw API.
2. `kittyclaw-workflow.json`: review the exact names, roles, evidence rules and outcomes used by the installer.
3. `ticket-templates.md`: create the decision, build and release-proof tickets.
4. `decision-brief-template.md`: freeze the audience, tool count and distribution plan before code.
5. `mcp-endpoint.example.cs`: adapt the embedded Streamable HTTP pattern to your existing API.
6. `server.json.example`: prepare official registry metadata and verify namespace casing.
7. `submission-checklist.md`: prove the tagged artifact with a real client before submission.

Run the installer against an existing project:

```powershell
./install-kittyclaw-workflow.ps1 -ProjectSlug "my-product"
```

Use `-BaseUrl` if KittyClaw is not running at `http://localhost:5230`. The installer is repeatable: it reuses a pipeline and columns with the same names, then creates or updates the processors and their routes using the IDs returned by the API.

The workflow keeps one manual `Owner decision` column. Move a ticket there only for choices that change the repository, product boundary or approved scope. After the decision, move it back to `Build`. All automated stages must attach their proof before returning the configured outcome.

The sample does not choose safe product actions for you. Review authorization, data exposure and destructive operations for your own product.