@stigmer/mcp-server 3.12.9 → 3.13.0

package/README.md

@@ -38,7 +38,7 @@ MCP client ──JSON-RPC──▶ stdio | HTTP session ──▶ tool handler
 - **`apply_*` ergonomics are generated.** The flattened, LLM-friendly input
   schemas for the `apply_*` tools (metadata hoisting, enum→string, reference
   flattening, oneof / `task_config` expansion) are produced at build time by the
-  codegen in `tools/codegen/generator/mcp_ts.go`. Never hand-edit `src/gen/`.
+  codegen in `tools/codegen/src/generator/mcp-ts.ts`. Never hand-edit `src/gen/`.
 
 ## Tools (30)
 
@@ -175,9 +175,10 @@ The `apply_*` tool schemas and proto bridges in `src/gen/` are generated:
 make codegen-apply
 ```
 
-This runs the Go emitter (`tools/codegen/generator`, target `mcp-ts`) over the
-proto contracts. Adding an `apply_*` tool for a new resource is an append to
-`mcpTSApplyResources` in `tools/codegen/generator/mcp_ts.go` plus regeneration.
+This runs the TypeScript emitter (`tools/codegen/src/generator`, target
+`mcp-ts`) over the proto contracts. Adding an `apply_*` tool for a new resource
+is an append to `MCP_TS_APPLY_RESOURCES` in
+`tools/codegen/src/generator/mcp-ts.ts` plus regeneration.
 
 ## Conventions
 

package/domains/client.d.ts

@@ -37,7 +37,7 @@ export declare function resolveToken(extra: RequestAuth | undefined, fallback: s
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */

package/domains/client.js

@@ -37,7 +37,7 @@ export function resolveToken(extra, fallback) {
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stigmer/mcp-server",
-  "version": "3.12.9",
+  "version": "3.13.0",
   "description": "Model Context Protocol server for the Stigmer platform — exposes Stigmer agents, skills, MCP servers, and workflows as MCP tools and resources",
   "license": "Apache-2.0",
   "type": "module",
@@ -35,8 +35,8 @@
     "@connectrpc/connect": "^2.0.0",
     "@connectrpc/connect-node": "^2.1.1",
     "@modelcontextprotocol/sdk": "^1.26.0",
-    "@stigmer/protos": "3.12.9",
-    "@stigmer/sdk": "3.12.9",
+    "@stigmer/protos": "3.13.0",
+    "@stigmer/sdk": "3.13.0",
     "yaml": "^2.8.2",
     "zod": "^3.25.0"
   }

package/src/domains/client.ts

@@ -58,7 +58,7 @@ export function resolveToken(extra: RequestAuth | undefined, fallback: string):
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */