@awesomate/hosting-mcp 0.13.0 → 0.13.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Awesomate MCP server \u2014 lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/awesomate-hosting/scripts/bootstrap.mjs

@@ -345,10 +345,18 @@ function installSkill() {
 // 2026-07-28). npx treats both forms identically at runtime; the = form keeps
 // the value glued to the token so these args are safe to copy anywhere.
 // The explicit package must stay: this package ships two bins.
-const CLEAN_ENTRY = {
-  command: 'npx',
-  args: ['-y', '--package=@awesomate/hosting-mcp', 'awesomate-hosting-mcp'],
-};
+// Windows: a bare `npx` spawn fails silently (it's npx.cmd there), so the
+// server never starts and the tools never appear — even after a restart.
+// First observed on the first Windows client, 2026-08-19. cmd /c resolves it.
+const CLEAN_ENTRY = process.platform === 'win32'
+  ? {
+      command: 'cmd',
+      args: ['/c', 'npx', '-y', '--package=@awesomate/hosting-mcp', 'awesomate-hosting-mcp'],
+    }
+  : {
+      command: 'npx',
+      args: ['-y', '--package=@awesomate/hosting-mcp', 'awesomate-hosting-mcp'],
+    };
 const MANUAL_ADD_JSON = JSON.stringify({ mcpServers: { 'awesomate-hosting': CLEAN_ENTRY } }, null, 2);
 
 /**
@@ -377,7 +385,11 @@ function ensureMcpRegistration() {
 
   const entry = cfg.mcpServers?.['awesomate-hosting'];
   const entryIsClean =
-    entry && !entry.env?.AWESOMATE_PAT && JSON.stringify(entry.args ?? []).includes('awesomate-hosting-mcp');
+    entry &&
+    !entry.env?.AWESOMATE_PAT &&
+    JSON.stringify(entry.args ?? []).includes('awesomate-hosting-mcp') &&
+    // A bare-npx registration is broken on Windows — rewrite it.
+    (process.platform !== 'win32' || entry.command === 'cmd');
 
   let changed = false;
   if (!entryIsClean) {
@@ -550,7 +562,13 @@ async function main() {
 
   const who = profile.email ? `${slug} (${profile.email}, plan ${redeemed.plan})` : `${slug} (plan ${redeemed.plan})`;
   console.log(`\n✓ Connected: ${who}${pinPath ? ` — pinned ${dirname(pinPath)}` : ''}`);
-  console.log('Setup complete. Next: run awesomate_whoami to confirm the account, then ask me to read your plan and list your sites.');
+  console.log('Setup complete.');
+  console.log('');
+  console.log('IMPORTANT — restart Claude Code now: the MCP tools and skills load only at startup.');
+  console.log('Until the restart, builds still work — the assistant should follow');
+  console.log('~/.claude/skills/awesomate-n8n/references/rest-fallback.md (n8n) or');
+  console.log('~/.claude/skills/awesomate-hosting/references/rest-fallback.md (hosting).');
+  console.log('After restarting: run awesomate_whoami to confirm the account, then ask for your first build.');
   console.log('(The skill works in your current Claude session right away via its REST fallback — restart Claude Code when convenient to load the MCP tools.)');
   if (issues.length) {
     console.log(SUPPORT_HINT);

package/skill/awesomate-n8n/SKILL.md

@@ -64,9 +64,11 @@ conflicts with anything under `references/vendor/`, platform-notes wins.
 | Provision a Postgres DB + n8n credential | `awesomate_n8n_provision_pg` |
 | Refresh these skills from the latest package | `awesomate_skill_update` |
 
-No MCP tools available (server not connected yet)? One restart of Claude
-Code usually fixes it; the awesomate-hosting skill's
-`references/rest-fallback.md` covers the interim.
+No `awesomate_n8n_*` tools in this session (fresh bootstrap, or the server
+didn't load)? Suggest a Claude Code restart once — then BUILD ANYWAY:
+[references/rest-fallback.md](references/rest-fallback.md) maps every tool
+to its REST endpoint, and the full loop works over it. Never tell the user
+they're blocked on a restart.
 
 ## 2. References — read on demand
 

package/skill/awesomate-n8n/references/rest-fallback.md

@@ -0,0 +1,69 @@
+# No MCP tools? The full build loop works over REST
+
+The `awesomate_n8n_*` tools load only when Claude Code starts — a session
+that just ran the bootstrap doesn't have them until the app restarts. That
+must not block the user's first build: every tool is a thin wrapper over
+these endpoints, so the ENTIRE loop (context → inventory → validate → draft
+→ test → activate) runs over plain REST. Tell the user a restart will make
+this smoother, then build anyway.
+
+## Auth (never echo the token)
+
+Read `~/.awesomate/credentials.json` (Windows:
+`%USERPROFILE%\.awesomate\credentials.json`) with a small Node script — it
+is JSON: `{ profiles: { <slug>: { pat, apiBase } }, defaultProfile }`. Pick
+the profile named by `.awesomate.json`'s `{"account"}` in the project root
+if present, else `defaultProfile`, else the sole profile. Send
+`Authorization: Bearer <pat>` to `<apiBase>` (default
+`https://hub.awesomate.ai`). On macOS/Linux,
+`node ~/.claude/skills/awesomate-hosting/scripts/resolve-account.mjs --api`
+prints `ACCT/API/PAT` in shell format (NOT JSON). Never print the PAT into
+the conversation or logs.
+
+## Reads (any plan, consent-gated server-side)
+
+| What | Endpoint |
+|---|---|
+| Session context + consent + limits + fingerprint (CALL FIRST) | `GET /api/my-n8n/machine/context` |
+| All workflows, node-level summaries | `GET /api/my-n8n/machine/workflows?active=&limit=&offset=` |
+| One workflow, full JSON | `GET /api/my-n8n/workflows/:id` |
+| Node inventory rollup | `GET /api/my-n8n/machine/nodes` |
+| Credential inventory (names/types, never secrets) | `GET /api/my-n8n/machine/credentials` |
+| Credential type schema | `GET /api/my-n8n/machine/credentials/schema/:type` |
+| `$vars` keys | `GET /api/my-n8n/machine/variables` |
+| Datatables (+ rows) | `GET /api/my-n8n/machine/datatables` · `GET …/datatables/:id/rows?limit=` |
+| Possibilities brief | `GET /api/my-n8n/machine/possibilities` |
+| Executions | `GET /api/my-n8n/workflows/:id/executions` · `GET /api/my-n8n/executions/:execId` |
+| Node-by-node execution debug | `GET /api/my-n8n/machine/executions/:execId/debug` |
+| Live node docs + community templates | `POST /api/my-n8n/machine/node-catalog/:tool` — tool ∈ search_nodes, get_node, search_templates, get_template, validate_node, tools_documentation; body = the tool's args (e.g. `{"query":"gmail"}`, `{"nodeType":"n8n-nodes-base.gmail"}`) |
+
+## Writes (Support Plus+, consent + quotas + audit apply identically)
+
+| Action | Endpoint |
+|---|---|
+| Validate workflow JSON | `POST /api/my-n8n/machine/workflows/validate` `{workflow}` |
+| Create inactive `[CLI]` draft | `POST /api/my-n8n/machine/workflows/draft` `{name, nodes, connections, settings?}` |
+| Update a draft in place | `PATCH /api/my-n8n/machine/workflows/:id` `{name?, nodes, connections, settings?}` |
+| Activate / deactivate | `POST /api/my-n8n/machine/workflows/:id/activate` `{active: true|false}` |
+| Test-fire the production webhook | `POST /api/my-n8n/machine/workflows/:id/test-fire` `{payload}` |
+| Promote draft → live (webhookIds preserved) | `POST /api/my-n8n/machine/workflows/:id/promote` `{draftId}` (`:id` = LIVE id) |
+| Roll a promote back | `POST /api/my-n8n/machine/operations/:operationId/rollback` |
+| Delete an inactive draft | `DELETE /api/my-n8n/machine/workflows/:id` |
+| Create a datatable (pass workflowId!) | `POST /api/my-n8n/machine/datatables` `{name, columns, workflowId?}` |
+| Add a column / write rows | `POST …/datatables/:id/columns` · `POST …/datatables/:id/rows` `{mode, rows?/filter?/data?}` |
+| Provision Postgres + n8n credential | `POST /api/my-n8n/machine/pg-credentials` |
+
+## Error contract (same as the tools)
+
+- `403 consent_required` + `flag` + `settingsUrl` → relay the link, re-check
+  after the user toggles (a null `settingsUrl` means contact support).
+- `403 missingScopes` → token predates n8n support — reconnect from
+  hub.awesomate.ai/sites.
+- `429 quota_exceeded` → the plan's daily cap; stop, don't retry-loop.
+- `503 node_catalog_unavailable` → use `references/vendor/` knowledge.
+- `404` on a path in this table → check the path against this file
+  EXACTLY; do not probe variations — anything not listed here does not
+  exist, and everything listed here is the complete surface.
+
+The skill's judgment (six-phase loop, approval gates, testing policy,
+never-activate-a-copy) applies unchanged — only the transport differs.