design-RFC-010 — KDS MCP server (hosted streamable-http)

ratified

Expose the Koder Design System as a hosted Model Context Protocol endpoint at `kds.koder.dev/mcp/` so AI agents (Claude Code, Cursor, Codex, Windsurf) query specs/tokens/components live over streamable-http instead of static-pulling llms.txt + JSON. Strict descendant of stack-RFC-002. KEY CORRECTION to ticket #117: the stdio MCP server ALREADY EXISTS in `koder-design-lsp --mcp` with the 5 core tools; this RFC extends THAT binary with a streamable-http transport rather than building a duplicate `cmd/kds-mcp-server/`.

Abstract

The ticket tools/design-gen#117 asks to "stand up a Go HTTP server (probably new cmd/kds-mcp-server/)" exposing KDS as an MCP endpoint. This RFC ratifies the architecture and corrects the build target: the MCP server for KDS already exists — koder-design-lsp --mcp ships 5 tools over stdio (engines/sdk/koder-design-lsp, ticket #001). The genuine gap is a hosted, streamable-http transport so remote agents reach kds.koder.dev/mcp/ without running a local binary, plus the *esources