@awesomate/hosting-mcp 0.20.1 → 0.20.2

package/dist/index.js

@@ -41939,10 +41939,11 @@ var KB_UPLOAD_TYPES = {
   ".webp": "image/webp"
 };
 var KB_MAX_UPLOAD_BYTES = 100 * 1024 * 1024;
+var KB_UNPARSEABLE = /* @__PURE__ */ new Set([".doc", ".docx", ".ppt", ".pptx", ".rtf", ".epub", ".html", ".htm"]);
 server.registerTool(
   "awesomate_knowledge_upload",
   {
-    description: "Ingest ONE file from the user's own computer into their Knowledge Base (Pro+). Pass a LOCAL PATH \u2014 this server runs on their machine and streams the file to the hub itself, so the file contents never pass through the conversation. Handles documents (pdf, docx, pptx, xlsx, csv, txt, md, epub), audio and video (transcribed), and images. Max 100 MB per file; bigger media goes through the hub's Knowledge \u2192 Sources page. INGESTING COSTS MONEY and counts against the monthly allowance, so ALWAYS get explicit approval for the specific file(s) first and say what it will consume. For several files, call once per file and report progress \u2014 do not loop silently. Returns a job; poll awesomate_knowledge_sources {action:'jobs'} until it succeeds, then probe the content with awesomate_knowledge_ask before building anything on it. A pack_required response means the allowance is exhausted: nothing was ingested and nothing was purchased.",
+    description: "Ingest ONE file from the user's own computer into their Knowledge Base (Pro+). Pass a LOCAL PATH \u2014 this server runs on their machine and streams the file to the hub itself, so the file contents never pass through the conversation. Handles documents (pdf, md, txt), business data (csv, tsv, xls, xlsx, json), audio and video (transcribed), and images. Word/PowerPoint/RTF/EPUB files are NOT parseable yet \u2014 the tool refuses them with the workaround (export to PDF, or save as .md/.txt). Max 100 MB per file; bigger media goes through the hub's Knowledge \u2192 Sources page. INGESTING COSTS MONEY and counts against the monthly allowance, so ALWAYS get explicit approval for the specific file(s) first and say what it will consume. For several files, call once per file and report progress \u2014 do not loop silently. Returns a job; poll awesomate_knowledge_sources {action:'jobs'} until it succeeds, then probe the content with awesomate_knowledge_ask before building anything on it. A pack_required response means the allowance is exhausted: nothing was ingested and nothing was purchased.",
     inputSchema: {
       path: external_exports.string().min(1).max(4096).describe("Path to the file on the user's machine (~ is expanded)"),
       title: external_exports.string().max(300).optional().describe("Display title; defaults to the filename")
@@ -41979,6 +41980,13 @@ server.registerTool(
         );
       }
       const ext = extname(abs).toLowerCase();
+      if (KB_UNPARSEABLE.has(ext)) {
+        return errorResult(
+          new Error(
+            `${basename(abs)} is a format the Knowledge Base cannot parse yet (${ext}). Export it to PDF, or save the text as .md or .txt, and upload that instead. For a web page, add its public URL with awesomate_knowledge_sources {action:'add'} rather than uploading the HTML file.`
+          )
+        );
+      }
       const contentType = KB_UPLOAD_TYPES[ext] ?? "application/octet-stream";
       const filename = title?.trim() ? `${title.trim()}${ext}` : basename(abs);
       const result = await hubUploadFile(requireConfig(), "/api/knowledge/sources", {

package/package.json

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

package/skill/CHANGELOG.json

@@ -1,5 +1,12 @@
 {
   "versions": [
+    {
+      "version": "0.20.2",
+      "highlights": [
+        "Plain-text (.txt) and Markdown files now ingest into your Knowledge Base - a bug stopped both from working",
+        "Unsupported file types (Word, PowerPoint, EPUB) are refused up front with the fix - export to PDF - instead of failing later"
+      ]
+    },
     {
       "version": "0.20.1",
       "highlights": [
@@ -41,13 +48,13 @@
       "highlights": [
         "Search your knowledge base with filters and ask questions within a slice of your content",
         "People & entities: your knowledge base now recognises who appears in your content, and you can name and merge them",
-        "Build AI agents from your own content — drafted, tested privately, and published only when you approve"
+        "Build AI agents from your own content \u2014 drafted, tested privately, and published only when you approve"
       ]
     },
     {
       "version": "0.14.0",
       "highlights": [
-        "Tools built for business owners, not developers — plain-language answers about your account, plan and limits",
+        "Tools built for business owners, not developers \u2014 plain-language answers about your account, plan and limits",
         "New support skill: get help, understand credits, or request a done-for-you build without leaving Claude",
         "New database skill: Claude picks the right place to keep your data and sets it up for you"
       ]

package/skill/awesomate-knowledge/references/from-your-files.md

@@ -37,6 +37,9 @@ contents never pass through the conversation and a 100 MB PDF costs no context.
 - A folder path is rejected on purpose — list it, agree the files, then upload.
 - Public URLs and whole sitemaps stay on `awesomate_knowledge_sources`
   `{action:'add'}`. Use that for their website; use upload for their disk.
+- **What parses:** pdf, md, txt (documents); csv, tsv, xls, xlsx, json (business data);
+  audio, video, images. Word/PowerPoint/RTF/EPUB/HTML files are refused with a
+  workaround — export to PDF or save as .md/.txt; a web page goes in by URL.
 
 ## 3. Wait for ingestion, and check it actually succeeded
 
@@ -52,17 +55,19 @@ processing never creates a source row, so `{action:'summary'}` still reports
 a failed ingest looks exactly like one that was never attempted.
 
 So: read the job's `status` AND its `error`, and relay the error text to the
-user. Two real ones seen in the wild, both platform-side configuration rather
-than anything wrong with their file:
+user. Real ones seen in the wild, all platform-side rather than anything wrong
+with their file:
 
-- `new row violates row-level security policy for table "documents"` —
-  document/markdown ingestion is not currently permitted for that tenant.
+- `new row violates row-level security policy for table "documents"` — a
+  platform bug in markdown/text ingestion, fixed 2026-09-02. A failed job wrote
+  nothing, so once support confirms the fix is deployed the same file can
+  simply be re-uploaded.
 - `transcription_not_configured: DEEPGRAM_API_KEY is not set` — audio/video
   cannot be transcribed on that deployment yet.
 
-Neither is fixable by the user or by retrying. Say plainly that the upload
-reached Awesomate and failed on our side, and raise it with support
-(awesomate-support skill) rather than re-uploading and spending allowance again.
+None of these are fixable by the user. Say plainly that the upload reached
+Awesomate and failed on our side, and raise it with support (awesomate-support
+skill) rather than blindly re-uploading and spending allowance again.
 
 Then `{action:'summary'}` for the whole-library counts once the job has
 actually succeeded.