@zibby/mcp-cli 0.3.2 → 0.3.4

package/index.js

@@ -479,7 +479,7 @@ server.tool(
     appType: z.string().min(1).optional().describe('Catalog id (e.g. "grafana", "gastown"). MUTUALLY EXCLUSIVE with goal — pass exactly one. Use this when the user wants something from the curated catalog.'),
     goal: z.string().min(1).optional().describe('Free-form description of what to install (e.g. "install n8n on port 5678 with sqlite persistence"). MUTUALLY EXCLUSIVE with appType. Use this when the user wants something NOT in catalog OR has custom config needs — the agent-ops bootstrap will follow the description to install whatever it describes. Examples: "install n8n", "set up an Outline wiki at /wiki", "deploy a basic Rails app from <repo URL>". The user is responsible for any license terms of software they install via this path.'),
     projectId: z.string().min(1).describe('Project the instance attaches to'),
-    name: z.string().min(1).optional().describe('Display name for the instance (defaults to appType, or the first line of goal)'),
+    name: z.string().min(1).optional().describe('Display name for the instance (shown as the dashboard header). ALWAYS pick a meaningful name based on WHAT is being installed and its purpose, NOT the install command. Good examples: `n8n-workflows`, `team-wiki`, `vaultwarden-secrets`, `rails-blog`. Bad examples: `test`, `goal-test`, `instance-1`, `install-n8n`. Max 80 chars, alphanumeric + dashes. Defaults to appType on catalog deploys; for goal deploys you MUST provide one or the server falls back to the first line of the goal text which is usually ugly.'),
     provider: z.enum(['claude', 'codex']).optional().describe('Agent provider. Default "claude" (Anthropic). "codex" runs the OpenAI Codex agent and requires an OpenAI API key in workspace-credentials.'),
     architecture: z.enum(['x86_64', 'arm64']).optional().describe('CPU architecture for the Fargate task. "arm64" runs on AWS Graviton — ~20% cheaper compute (same price to user). "x86_64" is the historical default + widest catalog compatibility. Omit to accept the catalog tile\'s preferred arch (first entry in its `architectures` array — usually arm64 for tiles that support it).'),
   },
@@ -515,7 +515,7 @@ server.tool(
 // resources, app version, project.
 server.tool(
   'zibby_get_app',
-  'Show one deployed app instance: status (running / pending / failed), running task count, app type+version, resources, public URL, project. Use when the user asks "is my app up?" or "what URL is it on?".',
+  'Show one deployed app instance: status (running / pending / failed), running task count, app type+version, resources, public URL, project. For multi-container apps the output also includes a per-service table (name/status/health/exit code) so the agent can diagnose which sidecar is unhealthy. Use when the user asks "is my app up?" or "what URL is it on?".',
   {
     instanceId: z.string().min(1).describe('Instance ID returned from zibby_deploy_app or zibby_list_apps'),
     projectId: z.string().min(1).optional()
@@ -535,14 +535,16 @@ server.tool(
 // (no streaming over MCP — agents can call again for fresh batches).
 server.tool(
   'zibby_get_app_logs',
-  'Fetch the most recent log lines from a deployed app instance. One-shot snapshot (the user should call again for new lines). Useful for diagnosing why an app is stuck, failed to provision, or to confirm a feature works end-to-end. Returns a string with one event per line, prefixed by ISO timestamp.',
+  'Fetch the most recent log lines from a deployed app instance. One-shot snapshot (the user should call again for new lines). Useful for diagnosing why an app is stuck, failed to provision, or to confirm a feature works end-to-end. Returns a string with one event per line, prefixed by ISO timestamp. For multi-container apps pass `service` to narrow to one container (e.g. `db`, `web`, `agent-ops`); without it, lines from all containers are interleaved by timestamp.',
   {
     instanceId: z.string().min(1).describe('Instance ID returned from zibby_deploy_app or zibby_list_apps'),
     projectId: z.string().min(1).optional().describe('Project the instance belongs to (picks the right cached API token)'),
     lines: z.number().int().min(1).max(5000).optional().default(200)
       .describe('Max number of recent lines to fetch (default 200, max 5000)'),
+    service: z.string().min(1).max(40).optional()
+      .describe('Multi-container apps only: limit logs to one service name (e.g. "db", "web", "agent-ops"). Defaults to interleaved across every container in the task.'),
   },
-  async ({ instanceId, projectId, lines }) => {
+  async ({ instanceId, projectId, lines, service }) => {
     const extraEnv = {};
     if (projectId) {
       const apiKey = getProjectApiToken(projectId);
@@ -550,6 +552,7 @@ server.tool(
     }
     const args = ['app', 'logs', instanceId];
     if (lines) args.push('--lines', String(lines));
+    if (service) args.push('--service', service);
     return cliResult(await runCli(args, { extraEnv }));
   }
 );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zibby/mcp-cli",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Zibby local-essential MCP Server — local workflow scaffold/validate/run + deploy/download (bundles local files). Pure-API tools live in the Zibby Remote MCP (api-prod.zibby.app/mcp).",
   "type": "module",
   "main": "index.js",