@aicommander/mcp 1.0.14 → 1.0.16

package/README.md

@@ -1,6 +1,6 @@
-# @aicommander/mcp
+# @aicommander/mcp — MCP server for remote command execution (SSH / Ansible alternative)
 
-Universal **stdio MCP server** for [AI Commander](https://aicommander.dev) — run shell commands on remote machines by talking to your AI client.
+Universal **stdio MCP server** for [AI Commander](https://aicommander.dev) — **remote command execution / remote shell** that lets your AI client run shell/bash commands on remote machines, servers and laptops. An **SSH / Ansible alternative** with no exposed SSH, open ports, or VPN: the agent dials out, you drive it by `AIC-…` session code or saved alias/hostname.
 
 Use this package to connect any MCP client that speaks **stdio** (Codex CLI, Claude Desktop's config file, Cursor, Windsurp, …) to your AI Commander relay. It wraps the remote HTTPS/SSE MCP endpoint so clients that can only launch a local process get the same `remote_exec` and `session_status` tools.
 
@@ -15,6 +15,7 @@ Use this package to connect any MCP client that speaks **stdio** (Codex CLI, Cla
 |---|---|
 | `remote_exec` | Run a shell command on one of your machines — the tool for any "connect to / remote shell / run X on" request. Name the machine by its `AIC-…` session code or (with an API key) a saved alias/hostname like `wearfits-m3`; streams stdout/stderr back. |
 | `session_status` | Check whether a machine is online/active/reachable (e.g. "is wearfits-m3 up?"). Same machine naming as above. |
+| `list_machines` | List all of your machines with their live online status (e.g. "what machines do I have?", "which of my computers are online?"). Requires an API key (`AICOMMANDER_TOKEN`); takes no arguments. |
 
 These are the canonical way to reach your machines — your AI client should use them rather than probing the local network, DNS/`.local`, or SSH. A string containing `aic-`/`AIC-` is almost certainly one of your machines.
 
@@ -78,6 +79,29 @@ Then just name a machine in chat — by session code or saved alias:
 
 The client routes it to `session_status` / `remote_exec` for you.
 
+## Publishing
+
+**Re-publish this package whenever you change code that ships in it** — e.g. a new
+tool, an edited tool description, or anything under `bin/`. The version in
+`package.json` / `server.json` is NOT auto-bumped, so a code change without a
+publish silently leaves npm + the registry stale (clients keep getting the old
+tools). Easy to forget — don't.
+
+Steps:
+
+1. Bump `version` in **both** `package.json` and `server.json` (keep them in sync).
+2. `npm publish` — needs npm 2FA OTP; `prepublishOnly: tsc` builds automatically.
+3. Publish to the official MCP Registry (domain ownership proven over HTTP via
+   `https://aicommander.dev/.well-known/mcp-registry-auth`, served by the Worker):
+
+   ```sh
+   mcp-publisher login http --domain=aicommander.dev \
+     --private-key=$(cat ~/.config/aicommander-mcp-publish/privkey.hex)
+   mcp-publisher publish
+   ```
+
+   The Worker must be deployed first so the well-known endpoint is live.
+
 ## License
 
 MIT

package/dist/bin/mcp.js

@@ -10,7 +10,15 @@ const SERVER_URL = process.env["AICOMMANDER_SERVER"] ?? "https://aicommander.dev
 const ACCOUNT_TOKEN = process.env["AICOMMANDER_TOKEN"];
 const server = new McpServer({
     name: "aicommander",
-    version: "1.0.12",
+    version: "1.0.15",
+}, {
+    instructions: "AI Commander — remote command execution / remote shell over an outbound-only agent. " +
+        "Use these tools for any SSH-style remote access: connect to a computer/machine/server, " +
+        "open a remote shell, remote bash, remote terminal, or run/check/install/fix something ON " +
+        "another machine. An SSH / Ansible alternative that needs no exposed SSH, open ports, or VPN. " +
+        "Name the machine by its AIC-… session code or (with an API key) a saved alias/hostname; a " +
+        "string containing 'aic-' is almost certainly one of the user's machines. Do NOT probe the " +
+        "local network, DNS, mDNS/.local, ping, or a raw ssh client — these tools ARE the remote connection.",
 });
 // Tool: remote_exec
 server.registerTool("remote_exec", {
@@ -160,5 +168,38 @@ server.registerTool("session_status", {
         content: content,
     };
 });
+// Tool: list_machines
+server.registerTool("list_machines", {
+    description: "List ALL of the user's machines (the computers/servers linked to their AI Commander account) with each one's live status. USE THIS for fleet-wide questions rather than one named machine — e.g. \"what machines do I have?\", \"which of my computers are online?\", \"list my servers/hosts\" — or when the user wants to act on a machine but hasn't said which yet (call this first to discover the options). Requires an API key (set AICOMMANDER_TOKEN); without it there is no account to list and it returns an error — fall back to session_status with a specific AIC- code. Each entry gives the machine's alias (pass it as `code` to the other tools), whether its agent is online right now, when it was last seen, and whether the link is still awaiting the machine operator's approval. Takes no arguments.",
+    inputSchema: {},
+}, async () => {
+    const res = await fetch(`${SERVER_URL}/mcp`, {
+        method: "POST",
+        headers: {
+            "Content-Type": "application/json",
+            ...(ACCOUNT_TOKEN ? { Authorization: `Bearer ${ACCOUNT_TOKEN}` } : {}),
+        },
+        body: JSON.stringify({
+            jsonrpc: "2.0",
+            id: 1,
+            method: "tools/call",
+            params: { name: "list_machines", arguments: {} },
+        }),
+    });
+    if (!res.ok) {
+        const text = await res.text();
+        return {
+            content: [{ type: "text", text: `Error ${res.status}: ${text}` }],
+            isError: true,
+        };
+    }
+    const data = (await res.json());
+    const content = data?.result?.content ?? [
+        { type: "text", text: JSON.stringify(data) },
+    ];
+    return {
+        content: content,
+    };
+});
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/package.json

@@ -1,16 +1,32 @@
 {
   "name": "@aicommander/mcp",
-  "version": "1.0.14",
+  "version": "1.0.16",
   "mcpName": "dev.aicommander/mcp",
-  "description": "Universal stdio MCP server for AI Commander — connect Codex CLI, Claude Desktop, or any stdio MCP client to your remote machines by session code (AIC-…) or saved alias/hostname.",
+  "description": "MCP server for remote command execution — run shell/bash commands on remote machines, servers and laptops from your AI agent (Claude, Codex, any stdio MCP client). An SSH / Ansible alternative with no exposed SSH, open ports or VPN; drive machines by AIC-… session code or saved alias/hostname.",
   "keywords": [
+    "ssh",
+    "remote",
+    "remote-execution",
+    "remote-command",
+    "remote-access",
+    "remote-management",
+    "remote-shell",
+    "shell",
+    "bash",
+    "terminal",
+    "command-execution",
+    "ssh-alternative",
+    "ansible-alternative",
+    "devops",
+    "sysadmin",
+    "server-management",
+    "fleet",
     "mcp",
     "model-context-protocol",
-    "aicommander",
-    "remote-shell",
+    "ai-agent",
     "claude",
     "codex",
-    "ai-agent"
+    "aicommander"
   ],
   "homepage": "https://aicommander.dev",
   "license": "MIT",