@khotan/cli 0.9.0 → 0.11.0

package/README.md

@@ -1,10 +1,9 @@
-# Khotan CLI & MCP server
+# Khotan CLI
 
-`@khotan/cli` is the first-party command-line interface and Model Context
-Protocol (MCP) server for the Khotan API. Both surfaces are thin adapters over
-the public `/api/v1` HTTP API, driven by the shared capability catalog in
-[`@khotan/core`](../khotan-core). They add nothing the API cannot do — they make
-the same operations ergonomic for humans (CLI) and agents (MCP).
+`@khotan/cli` is the first-party command-line interface for the Khotan API. It
+is a thin adapter over the public `/api/v1` HTTP API, driven by the shared
+capability catalog in [`@khotan/core`](../khotan-core). It adds nothing the API
+cannot do — it makes the same operations ergonomic for humans and agents alike.
 
 ## Install & run
 
@@ -32,27 +31,24 @@ own agents (Cursor, Devin, …) can drive setup. It is non-destructive and
 re-runnable, and never writes secrets.
 
 ```bash
-khotan init                 # Cursor: .cursor/mcp.json + .cursor/rules/khotan.mdc
-khotan init --client generic   # root mcp.json + khotan-agents.md
+khotan init                 # Cursor: .cursor/rules/khotan.mdc
+khotan init --client generic   # khotan-agents.md
 khotan init --force         # regenerate managed assets, overwriting edits
 khotan init --json          # machine-readable summary on stdout
 ```
 
-It writes an MCP config wired to `khotan mcp serve` (credentials referenced by
-`KHOTAN_API_URL` / `KHOTAN_API_KEY`, placeholders only) plus agent guidance. The
-MCP config merges into an existing one, preserving any other servers. Authenticate
-separately with `khotan auth set-key` or environment variables — never commit a key.
+It writes agent guidance for using the CLI. Authenticate separately with
+`khotan auth set-key` or environment variables — never commit a key.
 
 `init` also installs catalog-derived agent **skills** for using the CLI into
 `.cursor/skills/`, `.agents/skills/`, and `.claude/skills/` (regardless of
 `--client`): an overview `khotan` skill plus one per command domain
 (`khotan-apps`, `khotan-databases`, …). The skills are generated from the same
-capability catalog that drives the commands, MCP tools, and `khotan help`, so
-they can never drift. They are **managed assets**: every `khotan init` run
-regenerates them in place (no `--force` needed), so re-running `init` is how a
-workspace picks up new CLI commands — like the `databases branches` group. Your
-hand-authored rule/guide and any MCP edits stay non-destructive (preserved
-unless `--force`).
+capability catalog that drives the commands and `khotan help`, so they can
+never drift. They are **managed assets**: every `khotan init` run regenerates
+them in place (no `--force` needed), so re-running `init` is how a workspace
+picks up new CLI commands — like the `databases branches` group. Your
+hand-authored rule/guide stays non-destructive (preserved unless `--force`).
 
 ## Authentication & profiles
 
@@ -125,10 +121,10 @@ KHOTAN_API_KEY='<org-scoped key>'
 KHOTAN_ORG_ID='<org id>'
 ```
 
-When `KHOTAN_ORG_ID` (or `--assert-org <id>`) is set, every operation and
-`khotan mcp serve` verifies `whoami.organizationId` matches before trusting
-output and fails closed on mismatch (`error [org_mismatch]`). With no expected
-org id set, behavior is unchanged.
+When `KHOTAN_ORG_ID` (or `--assert-org <id>`) is set, every operation verifies
+`whoami.organizationId` matches before trusting output and fails closed on
+mismatch (`error [org_mismatch]`). With no expected org id set, behavior is
+unchanged.
 
 ## Command surface
 
@@ -144,7 +140,9 @@ documented surface and the executable surface cannot drift. Run `khotan help` or
 | Databases | `databases list`, `databases create --name db`, `databases connection <id>`, `databases rotate-credentials <id>`, `databases delete <id>` |
 | Files     | `files list`, `files get <id>`, `files upload <path>`, `files download <id> --output <path>`, `files download-url <id>`, `files preview-url <id>`, `files update <id> --name new.txt`, `files delete <id>` |
 | Folders   | `folders list`, `folders create --name docs`, `folders rename <id> --name new`, `folders delete <id>` |
-| Context   | `context list`, `context get <slug>`, `context raw <slug>`, `context create --title T --kind knowledge --content '...'`, `context update <slug> --expected-revision 3 --content '...'`, `context delete <slug>` |
+| Context   | `context list`, `context get <slug>`, `context raw <slug>`, `context create --title T --kind knowledge --content '...' --folder-id <id>`, `context update <slug> --expected-revision 3 --content '...' --folder-id <id>`, `context delete <slug>` |
+| Context folders | `context folders list`, `context folders create --name docs --parent-id <id>`, `context folders update <id> --name new --parent-id <id>`, `context folders delete <id> --recursive` |
+| Context revisions | `context revisions list <slug>`, `context revisions get <slug> <revision>`, `context revisions restore <slug> <revision>` |
 
 ### Output modes
 
@@ -184,39 +182,6 @@ khotan files download-url file_123    # attachment disposition, any file type
 See [Serving file attachments](../../docs/files-api-attachments.md) for the full
 preview/download flow and the receiver wiring guidance.
 
-## MCP server
-
-`khotan mcp serve` starts a local stdio MCP server that reuses the same profile,
-environment overrides, API client, and catalog as the CLI. It advertises
-**tools** (operations) and **resources** (URI-addressed read data) during
-initialization.
-
-- Operations become tools (e.g. `khotan_apps_create`). Destructive tools require
-  `{ "confirm": true }`; secret tools are labelled `[secret]`. The password-bearing
-  credential exchange is **not** exposed as a tool.
-- Durable read data is exposed as resource templates: `khotan://apps/{appId}`,
-  `khotan://pipelines/{pipelineId}`, `khotan://databases/{databaseId}`,
-  `khotan://files/{fileId}`, `khotan://context/{slug}`.
-- Secret-bearing values (env var values, connection URIs) are never resources.
-- stdout carries JSON-RPC only; all logs go to stderr.
-
-Example MCP client configuration:
-
-```json
-{
-  "mcpServers": {
-    "khotan": {
-      "command": "khotan",
-      "args": ["mcp", "serve"],
-      "env": {
-        "KHOTAN_API_URL": "https://app.example.com",
-        "KHOTAN_API_KEY": "khk_live_..."
-      }
-    }
-  }
-}
-```
-
 ## Catalog ↔ OpenAPI consistency
 
 `@khotan/core` validates that every catalog operation maps to a real `/api/v1`