@typescape-ai/mcp 1.9.33 → 1.11.0

package/README.md

@@ -1,13 +1,12 @@
 # @typescape-ai/mcp
 
-Typescape MCP server for external agent harnesses that need canonical review, finding, decision, rules, corpus, and export workflows.
+Typescape MCP server for external agent harnesses that need canonical review, finding, decision, rules, governance-signal, corpus, and export workflows.
 
-The published package exposes a broad multi-family tool registry for review, finding, workflow, rules, advisory, project, issue, and repository operations. MCP is the easiest discovery surface for agent clients such as Claude Code, Cursor, and Windsurf, but it is not the whole product surface. Typescape also ships the same operating model over the API and CLI.
+The published package exposes a broad multi-family tool registry for review, finding, workflow, rules, governance-signal, project, issue, and repository operations. MCP is the easiest discovery surface for agent clients such as Claude Code, Cursor, and Windsurf, but it is not the whole product surface. Typescape also ships the same operating model over the API and CLI.
 
 ## Requirements
 
-- [Bun](https://bun.sh/) `>=1.0` is preferred
-- [Node.js](https://nodejs.org/) `>=18.17` also works for `npx`-style launchers
+- [Bun](https://bun.sh/) `>=1.3.10`
 - `TYPESCAPE_API_KEY` and `TYPESCAPE_BASE_URL`
 
 ## Install
@@ -24,12 +23,6 @@ If you want to pin the package in a repo:
 bun add -D @typescape-ai/mcp
 ```
 
-Node-based MCP clients can also launch it without installing Bun:
-
-```bash
-npx -y @typescape-ai/mcp
-```
-
 ## Client Config
 
 Generic MCP config shape:
@@ -72,8 +65,8 @@ Cursor example: `.cursor/mcp.json`
 {
   "mcpServers": {
     "typescape": {
-      "command": "npx",
-      "args": ["-y", "@typescape-ai/mcp"],
+      "command": "bunx",
+      "args": ["@typescape-ai/mcp"],
       "env": {
         "TYPESCAPE_API_KEY": "ts_op_your_token",
         "TYPESCAPE_BASE_URL": "https://your-typescape-instance.example.com"
@@ -91,14 +84,26 @@ Review workflow:
 2. `typescape_get_render`
 3. `typescape_create_finding`
 4. `typescape_post_comment` / `typescape_record_decision`
-5. `typescape_export_review`
+5. `typescape_supersede_review`
+6. `typescape_export_review`
+
+`typescape_supersede_review` is the generic content-review revision flow.
+Rules working drafts use `typescape_revise_rules`.
 
 Rules workflow:
 
 1. `typescape_get_rules`
-2. `typescape_check_content`
-3. `typescape_import_rules`
-4. `typescape_rules_dashboard`
+2. `typescape_list_rule_documents`
+3. `typescape_check_content`
+4. `typescape_import_rules`
+5. `typescape_revise_rules`
+6. `typescape_publish_rules`
+7. `typescape_create_release_candidate`
+8. `typescape_transition_release_candidate`
+
+Supplemental diagnostics:
+
+- `typescape_rules_dashboard`
 
 API/CLI parity:
 
@@ -111,6 +116,7 @@ API/CLI parity:
 Reviews:
 
 - `typescape_create_review`
+- `typescape_supersede_review`
 - `typescape_export_review`
 - `typescape_list_reviews`
 - `typescape_get_review`
@@ -159,8 +165,17 @@ Corpus:
 Rules:
 
 - `typescape_get_rules`
+- `typescape_list_rule_documents`
 - `typescape_check_content`
 - `typescape_import_rules`
+- `typescape_revise_rules`
+- `typescape_publish_rules`
+- `typescape_deprecate_rules`
+- `typescape_create_release_candidate`
+- `typescape_list_release_candidates`
+- `typescape_get_release_candidate`
+- `typescape_get_release_candidate_status`
+- `typescape_transition_release_candidate`
 - `typescape_rules_dashboard`
 
 Repo, asset, and collection support:
@@ -175,10 +190,11 @@ Repo, asset, and collection support:
 ## Notes
 
 - Feature-gated tools return `feature_disabled` when the backing capability is off for the tenant.
+- The server publishes a compact `typescape://workspace/summary` resource for ambient tool discovery and workspace context.
 
 ## Response Shape
 
-Every MCP tool returns JSON text in `content[0].text`.
+Every MCP tool returns compact JSON text in `content[0].text`. The tool-call layer stays JSON for compatibility, while the workspace summary resource is optimized for agent bootstrap text.
 
 Success example:
 

package/bin/typescape-mcp

@@ -14,15 +14,10 @@ done
 
 SCRIPT_DIR="$(CDPATH= cd -P -- "$(dirname -- "$SOURCE")" && pwd -P)"
 
-if command -v node >/dev/null 2>&1; then
-  exec node "$SCRIPT_DIR/../dist/mcp.js" "$@"
-fi
-
 if command -v bun >/dev/null 2>&1; then
   exec bun "$SCRIPT_DIR/../dist/mcp.js" "$@"
 fi
 
-echo "Typescape MCP requires Node.js (>=18) or Bun." >&2
-echo "Install Node.js: https://nodejs.org/" >&2
+echo "Typescape MCP requires Bun 1.3.10 or newer." >&2
 echo "Install Bun: https://bun.sh/docs/installation" >&2
 exit 127