document-mcp 1.4.2 → 1.4.4

package/README.md

@@ -50,23 +50,31 @@ graph TD
 
 ## Getting started
 
-Requires Node.js `>=20` and pnpm `11.6.0` (pinned via `packageManager` in `package.json`).
+Run the server directly — no install step needed:
 
 ```sh
-pnpm install
-pnpm build         # turbo -> tsdown -> dist/ (ESM + CJS + .d.ts)
-pnpm typecheck     # turbo -> tsc --noEmit
-pnpm lint          # turbo -> eslint . --fix --cache --max-warnings 0
-pnpm test          # turbo -> vitest run --project unit
-pnpm test:workers  # turbo -> vitest under the real Cloudflare Workers runtime (workerd) via @cloudflare/vitest-pool-workers, driving createServer() through an in-memory JSON-RPC pair
-pnpm test:smoke    # turbo -> tsdown then vitest --project smoke -- spawns dist/bin.js as a real subprocess driven over genuine MCP stdio
+npx document-mcp
 ```
 
-Once published, run the server directly via `npx document-mcp` (stdio transport, no install step needed).
+### Connecting from Claude Code
+
+```sh
+claude mcp add --transport stdio document-mcp -- npx -y document-mcp
+```
+
+### Connecting from Codex CLI
+
+Add to `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.document-mcp]
+command = "npx"
+args = ["-y", "document-mcp"]
+```
 
-### Connecting from Claude Code / Claude Desktop
+### Connecting from Claude Desktop
 
-Add an entry to the client's MCP server configuration (`claude mcp add` for Claude Code, or the `mcpServers` block in Claude Desktop's config file):
+Add to the `mcpServers` block in Claude Desktop's config file (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):
 
 ```json
 {
@@ -92,6 +100,20 @@ Or, for local development against a checkout of this repository rather than the
 }
 ```
 
+### Development
+
+Requires Node.js `>=20` and pnpm `11.6.0` (pinned via `packageManager` in `package.json`).
+
+```sh
+pnpm install
+pnpm build         # turbo -> tsdown -> dist/ (ESM + CJS + .d.ts)
+pnpm typecheck     # turbo -> tsc --noEmit
+pnpm lint          # turbo -> eslint . --fix --cache --max-warnings 0
+pnpm test          # turbo -> vitest run --project unit
+pnpm test:workers  # turbo -> vitest under the real Cloudflare Workers runtime (workerd) via @cloudflare/vitest-pool-workers, driving createServer() through an in-memory JSON-RPC pair
+pnpm test:smoke    # turbo -> tsdown then vitest --project smoke -- spawns dist/bin.js as a real subprocess driven over genuine MCP stdio
+```
+
 ## Document I/O
 
 Every tool that takes or produces document bytes goes through the same two hybrid shapes, documented once here rather than repeated per tool below.

package/dist/bin.js

@@ -7,7 +7,7 @@ import { readFile, writeFile } from "node:fs/promises";
 import { existsSync, readFileSync } from "node:fs";
 import { basename, join } from "node:path";
 //#region package.json
-var version = "1.4.2";
+var version = "1.4.4";
 //#endregion
 //#region src/io/document-input.ts
 const EXTENSION_TO_FORMAT = {

package/dist/index.cjs

@@ -6,7 +6,7 @@ let node_fs_promises = require("node:fs/promises");
 let node_fs = require("node:fs");
 let node_path = require("node:path");
 //#region package.json
-var version = "1.4.2";
+var version = "1.4.4";
 //#endregion
 //#region src/io/document-input.ts
 const EXTENSION_TO_FORMAT = {

package/dist/index.js

@@ -5,7 +5,7 @@ import { readFile, writeFile } from "node:fs/promises";
 import { existsSync, readFileSync } from "node:fs";
 import { basename, join } from "node:path";
 //#region package.json
-var version = "1.4.2";
+var version = "1.4.4";
 //#endregion
 //#region src/io/document-input.ts
 const EXTENSION_TO_FORMAT = {

package/package.json

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