@justanothermldude/mcp-exec 1.7.9 → 1.7.11

package/README.md

@@ -156,12 +156,12 @@ const tool: ToolDefinition = {
   },
 };
 
-const wrapper = generateToolWrapper(tool, 'filesystem');
+const wrapper = generateToolWrapper(tool, 'example-filesystem');
 // Generates TypeScript function that calls bridge endpoint
 
 // Generate module for all server tools
 const tools: ToolDefinition[] = [/* ... */];
-const module = generateServerModule(tools, 'filesystem');
+const module = generateServerModule(tools, 'example-filesystem');
 // Generates complete TypeScript module with all tool wrappers
 ```
 
@@ -183,7 +183,7 @@ export async function read_file(input: ReadFileInput): Promise<unknown> {
     method: 'POST',
     headers: { 'Content-Type': 'application/json' },
     body: JSON.stringify({
-      server_name: 'filesystem',
+      server_name: 'example-filesystem',
       tool_name: 'read_file',
       arguments: input,
     }),
@@ -304,7 +304,7 @@ const result = await fetch('http://localhost:3000/call', {
   method: 'POST',
   headers: { 'Content-Type': 'application/json' },
   body: JSON.stringify({
-    server: 'filesystem',
+    server: 'example-filesystem',
     tool: 'read_file',
     args: { path: '/tmp/test.txt' },
   }),
@@ -318,7 +318,7 @@ Or use generated wrappers:
 
 ```typescript
 // Import generated wrappers
-import { read_file, write_file } from './filesystem-wrappers';
+import { read_file, write_file } from './example-filesystem-wrappers';
 
 // Type-safe tool calls
 const content = await read_file({ path: '/tmp/test.txt' });
@@ -336,7 +336,7 @@ mcp-exec maintains a disk-cached tool catalog at `~/.meta-mcp/tool-catalog.json`
 2. **Every session after:** On startup, mcp-exec reads the catalog and embeds the full API reference in the `execute_code_with_wrappers` tool description. The agent sees all tool names and parameter signatures before writing code:
    ```
    Tool API Reference:
-     adobe-mcp-gateway: glean_search({args, config?}), jira_search({args, config?}), ...
+     example-server: tool_one({args, config?}), tool_two({args, config?}), ...
    ```
 
 3. **Self-maintaining:**
@@ -370,11 +370,11 @@ Server and tool names support flexible, case-agnostic access via Proxy-based fuz
 All of these access patterns resolve to the same server:
 
 ```typescript
-// Original server name: "corp-jira"
-mcp['corp-jira']    // Bracket notation with original name
-mcp.corpJira        // camelCase
-mcp.corp_jira       // snake_case
-mcp.corpjira        // Lowercase without separators
+// Original server name: "example-jira-server"
+mcp['example-jira-server']    // Bracket notation with original name
+mcp.exampleJiraServer         // camelCase
+mcp.example_jira_server       // snake_case
+mcp.examplejiraserver         // Lowercase without separators
 ```
 
 ### Tool Name Resolution
@@ -382,13 +382,13 @@ mcp.corpjira        // Lowercase without separators
 Similarly, tool names within a server support fuzzy matching:
 
 ```typescript
-// Original tool name: "search_jira_issues"
-const server = mcp['corp-jira'];
+// Original tool name: "search_issues"
+const server = mcp['example-jira-server'];
 
-server.search_jira_issues     // Original snake_case
-server.searchJiraIssues       // camelCase
-server.searchjiraissues       // Lowercase
-server['search-jira-issues']  // kebab-case via bracket notation
+server.search_issues     // Original snake_case
+server.searchIssues      // camelCase
+server.searchissues      // Lowercase
+server['search-issues']  // kebab-case via bracket notation
 ```
 
 ### How It Works
@@ -403,16 +403,16 @@ The resolution uses a two-step approach:
 When a property doesn't match any available option, a `TypeError` is thrown with helpful suggestions:
 
 ```typescript
-const server = mcp['corp-jira'];
+const server = mcp['example-jira-server'];
 server.nonExistentTool;
-// TypeError: Property "nonExistentTool" not found on corp-jira.
-//            Available: search_jira_issues, create_issue, get_issue, ...
+// TypeError: Property "nonExistentTool" not found on example-jira-server.
+//            Available: search_issues, create_issue, get_issue, ...
 ```
 
 ```typescript
 mcp.unknownServer;
 // TypeError: Property "unknownServer" not found on mcp.
-//            Available: corp-jira, github, filesystem, ...
+//            Available: example-jira-server, example-source, example-filesystem, ...
 ```
 
 This makes it easy to discover available tools and servers when debugging or exploring the API.

package/dist/index.js

@@ -77,7 +77,7 @@ function createListServersHandler() {
         const escapedTags = escapeMarkdownCell(tagsStr);
         return `| \`${escapedName}\` | ${escapedDesc} | ${escapedTags} |`;
       });
-      const table = "## Available MCP Servers\n\n| Name | Description | Tags |\n|------|-------------|------|\n" + rows.join("\n") + '\n\nTo use a server, pass its exact name in the `wrappers` array of `execute_code_with_wrappers`.\nExample: `wrappers: ["adobe-mcp-gateway"]`\n\nTo see tools on a server: `get_mcp_tool_schema({ server: "adobe-mcp-gateway" })`';
+      const table = "## Available MCP Servers\n\n| Name | Description | Tags |\n|------|-------------|------|\n" + rows.join("\n") + '\n\nTo use a server, pass its exact name in the `wrappers` array of `execute_code_with_wrappers`.\nExample: `wrappers: ["example-server"]`\n\nTo see tools on a server: `get_mcp_tool_schema({ server: "example-server" })`';
       return {
         content: [{ type: "text", text: table }],
         isError: false
@@ -2003,7 +2003,7 @@ __name(createMcpExecServer, "createMcpExecServer");
 // dist/index.js
 import { ServerPool, createConnection, getServerConfig as getServerConfig3, loadServerManifest as loadServerManifest2, cleanupOrphanedProcesses } from "@justanothermldude/mcp-exec-core";
 var APP_NAME = "mcp-exec";
-var VERSION2 = "1.7.9";
+var VERSION2 = "1.7.11";
 var defaultExecutor = null;
 function getDefaultExecutor() {
   if (!defaultExecutor) {

package/dist/tools/list-servers.js

@@ -101,8 +101,8 @@ export function createListServersHandler() {
                 rows.join('\n') +
                 '\n\n' +
                 'To use a server, pass its exact name in the `wrappers` array of `execute_code_with_wrappers`.\n' +
-                'Example: `wrappers: ["adobe-mcp-gateway"]`\n\n' +
-                'To see tools on a server: `get_mcp_tool_schema({ server: "adobe-mcp-gateway" })`';
+                'Example: `wrappers: ["example-server"]`\n\n' +
+                'To see tools on a server: `get_mcp_tool_schema({ server: "example-server" })`';
             return {
                 content: [{ type: 'text', text: table }],
                 isError: false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justanothermldude/mcp-exec",
-  "version": "1.7.9",
+  "version": "1.7.11",
   "description": "MCP execution utilities for sandboxed code execution with OS-level isolation",
   "type": "module",
   "main": "dist/index.js",
@@ -21,7 +21,7 @@
   },
   "dependencies": {
     "@anthropic-ai/sandbox-runtime": "^0.0.19",
-    "@justanothermldude/mcp-exec-core": "^0.1.9",
+    "@justanothermldude/mcp-exec-core": "^0.1.11",
     "@modelcontextprotocol/sdk": "^1.25.3",
     "esbuild": "^0.25.12",
     "get-port": "^7.1.0"