@visulima/vis-mcp 1.0.9 → 1.0.10

package/CHANGELOG.md

@@ -1,3 +1,11 @@
+## @visulima/vis-mcp [1.0.10](https://github.com/visulima/visulima/compare/%40visulima%2Fvis-mcp%401.0.9...%40visulima%2Fvis-mcp%401.0.10) (2026-07-27)
+
+
+### Dependencies
+
+* **@visulima/fs:** upgraded to 5.0.11
+* **@visulima/vis:** upgraded to 2.0.1
+
 ## @visulima/vis-mcp [1.0.9](https://github.com/visulima/visulima/compare/%40visulima%2Fvis-mcp%401.0.8...%40visulima%2Fvis-mcp%401.0.9) (2026-07-27)
 
 

package/dist/index.d.ts

@@ -1,18 +1,18 @@
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 /**
-* Spawn a `vis` subprocess and capture stdout/stderr without piping to the
-* parent's stdio. The MCP server must keep its own stdout pristine — anything
-* other than JSON-RPC frames corrupts the protocol stream.
-*
-* `visBin` is the resolved path to the user's installed vis CLI; injected so
-* tests can point at a fixture instead of the real CLI.
-*/
+ * Spawn a `vis` subprocess and capture stdout/stderr without piping to the
+ * parent's stdio. The MCP server must keep its own stdout pristine — anything
+ * other than JSON-RPC frames corrupts the protocol stream.
+ *
+ * `visBin` is the resolved path to the user's installed vis CLI; injected so
+ * tests can point at a fixture instead of the real CLI.
+ */
 declare const execVis: (visBin: string, args: ReadonlyArray<string>, options?: ExecOptions) => Promise<ExecResult>;
 /**
-* Run `vis` and parse stdout as JSON. Throws when the subprocess fails or
-* stdout isn't valid JSON — callers map this into an `isError: true` MCP
-* response.
-*/
+ * Run `vis` and parse stdout as JSON. Throws when the subprocess fails or
+ * stdout isn't valid JSON — callers map this into an `isError: true` MCP
+ * response.
+ */
 declare const execVisJson: <T>(visBin: string, args: ReadonlyArray<string>, options?: ExecOptions) => Promise<T>;
 interface ExecResult {
   exitCode: number;
@@ -26,29 +26,29 @@ interface ExecOptions {
   cwd?: string;
   env?: Record<string, string | undefined>;
   /**
-  * Maximum combined stdout+stderr (in code units, an over-approximation of
-  * bytes) before the child is killed. Defaults to 64 MiB.
-  */
+   * Maximum combined stdout+stderr (in code units, an over-approximation of
+   * bytes) before the child is killed. Defaults to 64 MiB.
+   */
   maxBufferBytes?: number;
   /** Hard ceiling. The default 120s suits cache lookups and listings. */
   timeoutMs?: number;
 }
 /**
-* Run `vis list ...` and parse stdout as JSON, served from a short-TTL memo
-* keyed on `workspaceRoot` + `args`. A rejected lookup is never cached, so a
-* transient CLI failure does not poison subsequent calls.
-*/
+ * Run `vis list ...` and parse stdout as JSON, served from a short-TTL memo
+ * keyed on `workspaceRoot` + `args`. A rejected lookup is never cached, so a
+ * transient CLI failure does not poison subsequent calls.
+ */
 declare const listVisJson: <T>(visBin: string, workspaceRoot: string, args: ReadonlyArray<string>, ttlMs?: number) => Promise<T>;
 /** Clear the memo. Exposed for tests and long-running embeds that need a reset. */
 declare const clearListCache: () => void;
 /**
-* MCP tool response shape used across all `vis` tools. Kept in one place so
-* adding a new tool doesn't require re-deriving the type from the SDK.
-*
-* The index signature matches the SDK's `CallToolResult` shape — the SDK
-* extends the JSON-RPC result with an open `_meta` bag and refuses anything
-* stricter at the assignment site.
-*/
+ * MCP tool response shape used across all `vis` tools. Kept in one place so
+ * adding a new tool doesn't require re-deriving the type from the SDK.
+ *
+ * The index signature matches the SDK's `CallToolResult` shape — the SDK
+ * extends the JSON-RPC result with an open `_meta` bag and refuses anything
+ * stricter at the assignment site.
+ */
 interface McpToolResponse {
   [key: string]: unknown;
   content: {
@@ -57,19 +57,19 @@ interface McpToolResponse {
   }[];
   isError?: boolean;
   /**
-  * Typed payload mirrored from `content`. Present only for tools that declare
-  * an `outputSchema`; lets MCP clients validate and render the result instead
-  * of re-parsing the JSON string in the text block.
-  */
+   * Typed payload mirrored from `content`. Present only for tools that declare
+   * an `outputSchema`; lets MCP clients validate and render the result instead
+   * of re-parsing the JSON string in the text block.
+   */
   structuredContent?: Record<string, unknown>;
 }
 declare const okResponse: (payload: unknown) => McpToolResponse;
 /**
-* Like {@link okResponse} but also attaches `structuredContent` so clients of a
-* tool that declared an `outputSchema` get a validated, typed payload alongside
-* the JSON text block. Only object payloads are valid structured content per the
-* MCP spec, so the caller must pass a record.
-*/
+ * Like {@link okResponse} but also attaches `structuredContent` so clients of a
+ * tool that declared an `outputSchema` get a validated, typed payload alongside
+ * the JSON text block. Only object payloads are valid structured content per the
+ * MCP spec, so the caller must pass a record.
+ */
 declare const okStructuredResponse: (payload: Record<string, unknown>) => McpToolResponse;
 declare const errorResponse: (error: unknown) => McpToolResponse;
 interface ToolContext {
@@ -79,90 +79,64 @@ interface ToolContext {
   workspaceRoot: string;
 }
 /**
-* Dependencies a tool needs from the MCP SDK. Threaded through so each tool
-* stays a plain registration function and tests can swap in a fake `server`
-* without touching the real SDK.
-*/
+ * Dependencies a tool needs from the MCP SDK. Threaded through so each tool
+ * stays a plain registration function and tests can swap in a fake `server`
+ * without touching the real SDK.
+ */
 interface ToolDeps {
   server: McpServer;
 }
 /**
-* Register every tool against an already-built MCP server. Pure wiring — no
-* I/O — so tests can drive it against an `InMemoryTransport` without forking
-* a subprocess.
-*/
+ * Register every tool against an already-built MCP server. Pure wiring — no
+ * I/O — so tests can drive it against an `InMemoryTransport` without forking
+ * a subprocess.
+ */
 declare const registerAllTools: (deps: ToolDeps, context: ToolContext) => void;
 /**
-* Build a fully-configured MCP server with all vis tools registered. Returns
-* the server and deps so callers can connect any transport. Tests use this
-* with `InMemoryTransport.createLinkedPair()`.
-*/
+ * Build a fully-configured MCP server with all vis tools registered. Returns
+ * the server and deps so callers can connect any transport. Tests use this
+ * with `InMemoryTransport.createLinkedPair()`.
+ */
 declare const createMcpServer: (context: ToolContext) => Promise<{
   deps: ToolDeps;
   server: McpServer;
 }>;
 /**
-* Boot the vis MCP server over stdio.
-*
-* Critical invariant: nothing in this process may write to stdout outside
-* the MCP transport. Any console.log in tool handlers will frame-corrupt
-* the JSON-RPC stream. Logs go to stderr only.
-*/
+ * Boot the vis MCP server over stdio.
+ *
+ * Critical invariant: nothing in this process may write to stdout outside
+ * the MCP transport. Any console.log in tool handlers will frame-corrupt
+ * the JSON-RPC stream. Logs go to stderr only.
+ */
 declare const startMcpServer: () => Promise<void>;
-declare const registerAdvisoryStatus: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerAudit: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerCacheHash: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerCacheWhy: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerDescribeProject: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerDescribeTemplate: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerFmt: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerGetRunLogs: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerLint: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerListProjects: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerListRuns: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerListTargets: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
-declare const registerListTemplates: ({
-  server
-}: ToolDeps, context: ToolContext) => void;
+declare const registerAdvisoryStatus: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerAudit: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerCacheHash: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerCacheWhy: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerDescribeProject: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerDescribeTemplate: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerFmt: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerGetRunLogs: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerLint: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerListProjects: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerListRuns: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerListTargets: ({ server }: ToolDeps, context: ToolContext) => void;
+declare const registerListTemplates: ({ server }: ToolDeps, context: ToolContext) => void;
 declare const isValidRunId: (value: string) => boolean;
 /**
-* Task IDs are `&lt;project>:&lt;target>`; both halves are package or npm-scope
-* shaped. The exec layer uses argv-form spawn so shell metacharacters are
-* inert, but a leading `-` would be parsed as a CLI flag by the vis CLI.
-*/
+ * Task IDs are `&lt;project>:&lt;target>`; both halves are package or npm-scope
+ * shaped. The exec layer uses argv-form spawn so shell metacharacters are
+ * inert, but a leading `-` would be parsed as a CLI flag by the vis CLI.
+ */
 declare const isValidTaskId: (value: string) => boolean;
 /**
-* Guard for free-form positional arguments forwarded to the vis CLI (template
-* names, file paths). Spawn is argv-form so shell metacharacters are inert, but
-* a leading `-` would be parsed as a CLI flag — turning an LLM-supplied
-* `files: ["--fix"]` into a write operation that violates the `readOnlyHint`
-* contract clients rely on for auto-approval. Callers must additionally insert
-* a literal `--` separator before any positionals so a value that *becomes*
-* flag-shaped through some other path can never be reinterpreted as an option.
-*/
+ * Guard for free-form positional arguments forwarded to the vis CLI (template
+ * names, file paths). Spawn is argv-form so shell metacharacters are inert, but
+ * a leading `-` would be parsed as a CLI flag — turning an LLM-supplied
+ * `files: ["--fix"]` into a write operation that violates the `readOnlyHint`
+ * contract clients rely on for auto-approval. Callers must additionally insert
+ * a literal `--` separator before any positionals so a value that *becomes*
+ * flag-shaped through some other path can never be reinterpreted as an option.
+ */
 declare const isSafePositional: (value: string) => boolean;
 export { type ExecOptions, type ExecResult, type McpToolResponse, type ToolContext, type ToolDeps, clearListCache, createMcpServer, errorResponse, execVis, execVisJson, isSafePositional, isValidRunId, isValidTaskId, listVisJson, okResponse, okStructuredResponse, registerAdvisoryStatus, registerAllTools, registerAudit, registerCacheHash, registerCacheWhy, registerDescribeProject, registerDescribeTemplate, registerFmt, registerGetRunLogs, registerLint, registerListProjects, registerListRuns, registerListTargets, registerListTemplates, startMcpServer };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visulima/vis-mcp",
-  "version": "1.0.9",
+  "version": "1.0.10",
   "description": "MCP (Model Context Protocol) server for @visulima/vis — exposes vis tooling to AI agents over stdio",
   "keywords": [
     "agent",
@@ -59,12 +59,12 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@visulima/fs": "5.0.10",
+    "@visulima/fs": "5.0.11",
     "@visulima/path": "3.0.0",
     "zod": "4.4.3"
   },
   "peerDependencies": {
-    "@visulima/vis": "2.0.0"
+    "@visulima/vis": "2.0.1"
   },
   "engines": {
     "node": "^22.14.0 || >=24.10.0"