document-mcp 4.10.1 → 4.11.0

package/README.md

@@ -187,6 +187,10 @@ Then add the server URL (e.g., `https://your-host:3000/mcp`) as a connector in C
 
 > **Security note:** this HTTP listener has no authentication and no Host/Origin allowlisting of its own — anyone who can reach it can call every tool, including ones that read and write arbitrary filesystem paths. It is safe by default only because it binds to loopback; whatever fronts it for remote access (tunnel, reverse proxy) is responsible for authenticating callers before traffic ever reaches this process.
 
+### Standalone binary
+
+Every release also attaches a Node [single-executable application](https://nodejs.org/api/single-executable-applications.html) build for Linux, macOS, and Windows to that release's own GitHub Release assets — the entire server and its dependencies embedded in one file, needing no Node.js install or `npx` at all. It supports both `stdio` and `--transport http` exactly as above; point an MCP client's `command` at the downloaded binary directly instead of `npx`/`node`. Download the asset matching your platform from the package's tag on the [Releases page](https://github.com/ExaDev/documents.js/releases) and run it directly (`chmod +x` on Linux/macOS first).
+
 ### Development
 
 Requires Node.js `>=20` and pnpm `11.6.0` (pinned via `packageManager` in `package.json`).

package/dist/bin.js

@@ -6,7 +6,7 @@ import { McpServer, createMcpHandler } from "@modelcontextprotocol/server";
 import { computeFormulaOperation, convertDocumentOperation, describeFontFileOperation, documentAppendParagraphsOperation, documentCreateOperation, docxExtrasOperation, fontsOperation, fromPackageOperation, listDocumentConversionsOperation, metadataReadOperation, metadataWriteOperation, odbFormsOperation, odbQueryOperation, odbRenderReportOperation, odbReportsOperation, odbTablesOperation, odbToCsvOperation, odbToXlsxOperation, odmToPdfOperation, outlineDocumentOperation, pdfInspectOperation } from "document-operations";
 import { OdbReportNotSpecifiedError, OdmUnresolvedSectionError } from "documents.js";
 //#region package.json
-var version = "4.10.1";
+var version = "4.11.0";
 //#endregion
 //#region src/register-operation.ts
 function toErrorResult(error) {
@@ -172,7 +172,7 @@ function serveHttp(port) {
 	});
 }
 //#endregion
-//#region src/bin.ts
+//#region src/cli.ts
 const DEFAULT_HTTP_PORT = 3e3;
 function readFlag(args, name) {
 	const prefix = `--${name}=`;
@@ -190,6 +190,11 @@ function parsePort(raw) {
 	if (!Number.isInteger(port) || String(port) !== raw.trim() || port < 0 || port > 65535) throw new Error(`--port must be an integer between 0 and 65535, got "${raw}"`);
 	return port;
 }
+/**
+* The real CLI entry logic, shared by both distribution shapes this package ships: `src/bin.ts` (the published npm `bin`, run under a real Node.js install) and `src/sea-entry.ts` (bundled into a Node single-executable application, which embeds its own Node runtime). Node's SEA feature runs only a CommonJS entry with no top-level await (see that file's own comment), so this function itself contains no top-level await of its own -- only `bin.ts` awaits calling it, at its own top level, which SEA never sees.
+*
+* Returns the bound `http.Server` for the `--transport http` path so a caller with a reason to stop it again (a test binding an ephemeral port for the duration of one assertion) can; `undefined` for `--transport stdio`, which has no equivalent handle to return -- `serveStdio` wires the process's own stdin/stdout directly and keeps the process alive on its own.
+*/
 async function main() {
 	const args = process.argv.slice(2);
 	const transport = readFlag(args, "transport") ?? "stdio";
@@ -199,13 +204,16 @@ async function main() {
 	}
 	if (transport === "http") {
 		const portArg = readFlag(args, "port");
-		const address = (await serveHttp(portArg === void 0 ? DEFAULT_HTTP_PORT : parsePort(portArg))).address();
+		const httpServer = await serveHttp(portArg === void 0 ? DEFAULT_HTTP_PORT : parsePort(portArg));
+		const address = httpServer.address();
 		if (address === null || typeof address === "string") throw new Error("Expected the HTTP server to bind a TCP address, not a pipe or Unix socket");
 		console.error(`document-mcp listening on http://127.0.0.1:${String(address.port)}${MCP_HTTP_PATH}`);
-		return;
+		return httpServer;
 	}
 	throw new Error(`Unknown --transport "${transport}". Supported values: stdio, http.`);
 }
+//#endregion
+//#region src/bin.ts
 await main();
 //#endregion
 export {};

package/dist/index.cjs

@@ -3,7 +3,7 @@ let _modelcontextprotocol_server = require("@modelcontextprotocol/server");
 let document_operations = require("document-operations");
 let documents_js = require("documents.js");
 //#region package.json
-var version = "4.10.1";
+var version = "4.11.0";
 //#endregion
 //#region src/register-operation.ts
 function toErrorResult(error) {

package/dist/index.js

@@ -2,7 +2,7 @@ import { McpServer } from "@modelcontextprotocol/server";
 import { computeFormulaOperation, convertDocumentOperation, describeFontFileOperation, documentAppendParagraphsOperation, documentCreateOperation, docxExtrasOperation, fontsOperation, fromPackageOperation, listDocumentConversionsOperation, metadataReadOperation, metadataWriteOperation, odbFormsOperation, odbQueryOperation, odbRenderReportOperation, odbReportsOperation, odbTablesOperation, odbToCsvOperation, odbToXlsxOperation, odmToPdfOperation, outlineDocumentOperation, pdfInspectOperation } from "document-operations";
 import { OdbReportNotSpecifiedError, OdmUnresolvedSectionError } from "documents.js";
 //#region package.json
-var version = "4.10.1";
+var version = "4.11.0";
 //#endregion
 //#region src/register-operation.ts
 function toErrorResult(error) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document-mcp",
-  "version": "4.10.1",
+  "version": "4.11.0",
   "description": "MCP (Model Context Protocol) server exposing documents.js's document-conversion, .odb, metadata, and font tooling as MCP tools.",
   "type": "module",
   "repository": {