@slexkit/mcp 0.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 SlexKit contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,58 @@
+# @slexkit/mcp
+
+Read-only MCP server for SlexKit docs, component APIs, examples, and source validation.
+
+## Configure
+
+```json
+{
+  "mcpServers": {
+    "slexkit": {
+      "command": "npx",
+      "args": ["-y", "@slexkit/mcp"]
+    }
+  }
+}
+```
+
+The same command shape works in clients such as Codex, Claude Desktop, and other MCP-compatible agent tools:
+
+```sh
+npx -y @slexkit/mcp
+```
+
+## Tools
+
+The server exposes three read-only tools:
+
+| Tool | Purpose |
+|------|---------|
+| `slexkitDocs` | Search or fetch generated Markdown docs, including runtime, security, package, ToolHost, and component pages. |
+| `slexkitExamples` | Return component examples or generated templates such as `status`, `calculator`, `toolhost-form`, and `host-integration`. |
+| `slexkitValidate` | Parse Slex source and return diagnostics plus detected component usage. |
+
+Example validation request:
+
+```json
+{
+  "name": "slexkitValidate",
+  "arguments": {
+    "source": "{ slex: \"0.1\", namespace: \"demo\", layout: { \"text:message\": { text: \"Hello\" } } }"
+  }
+}
+```
+
+Successful validation returns structured content similar to:
+
+```json
+{
+  "ok": true,
+  "componentUsage": ["text"]
+}
+```
+
+Invalid source returns `ok: false` plus a SlexKit diagnostic with message, location, and excerpt.
+
+## Safety
+
+The MCP server is read-only. It serves bundled docs and generated metadata from the package, validates source text, and writes no project files.

package/dist/data/llms-authoring.txt

@@ -0,0 +1,44 @@
+# SlexKit Authoring Rules for LLMs
+
+SlexKit's agent-readable source is Markdown with explicit `slex` fences. Do not use `.mdx`; `slex` fences are the interactive layer.
+
+## Always Do
+
+- Emit explicit `slex` fenced code blocks for display-oriented interactive UI.
+- Use a Slex expression envelope: `slex`, `namespace`, `g`, and `layout`.
+- Put mutable state and helper functions in `g`; put component structure in `layout`.
+- Use component keys in `type:identifier` form, such as `card:summary`.
+- Use `$` read-pipes for dynamic props and `on*` write-pipes for event handlers.
+- Include readable Markdown fallback text after the fence.
+- Use secure runtime integration for untrusted or agent-generated source.
+
+## Do Not
+
+- Do not emit imports, JSX, Svelte, Vue, or project scaffolding inside `slex` fences.
+- Do not ask hosts to scan plain JavaScript, JSON, or untagged code blocks.
+- Do not wrap ordinary status cards or summaries in ToolHost.
+- Do not bypass the sandbox for untrusted source.
+- Do not invent `.mdx` routes for SlexKit docs.
+
+## Display UI Example
+
+```slex
+{
+  slex: "0.1",
+  namespace: "release_status",
+  g: { done: 3, total: 4 },
+  layout: {
+    "card:summary": {
+      title: "Release status",
+      "text:count": { "$text": "g.done + '/' + g.total + ' complete'" },
+      "progress:bar": { "$value": "g.done / g.total * 100" }
+    }
+  }
+}
+```
+
+**Fallback:** Release status: 3/4 complete.
+
+## ToolHost Boundary
+
+Use ToolHost only when the UI must return structured user input to the host, such as confirmations, option lists, or forms. Display-only dashboards, metrics, and status blocks should stay as `slex` fences.