overleaf-forge 2.7.1 → 2.7.2

package/README.md

@@ -33,14 +33,17 @@ Editing a LaTeX project through an AI normally means one of two bad options: pas
 
 ## Install
 
-For most clients the whole install is a few lines of JSON: point the client at the published npm package via `npx`, which fetches and runs it on demand with nothing to clone or update by hand.
+**Recommended: npx.** Nothing to clone, nothing to keep updated by hand. The whole install is a few lines of JSON in your MCP client, plus two values from Overleaf.
+
+1. Get your two values: an Overleaf **git token** (Account Settings → Git Integration → create token) and your **project id** (the `<ID>` in `https://www.overleaf.com/project/<ID>`).
+2. Add this block to your client's config file (locations in the table below):
 
 ```json
 {
   "mcpServers": {
     "overleaf": {
       "command": "npx",
-      "args": ["-y", "overleaf-forge"],
+      "args": ["-y", "overleaf-forge@latest"],
       "env": {
         "OVERLEAF_GIT_TOKEN": "olp_xxxxxxxxxxxxxxxxxxxxxxxx",
         "OVERLEAF_PROJECT_ID": "0123456789abcdef01234567"
@@ -50,7 +53,17 @@ For most clients the whole install is a few lines of JSON: point the client at t
 }
 ```
 
-A token and a project id in that `env` block are the entire setup for a single project, with no config file. This is **env-only mode** (see Configuration for the multi-project path).
+3. Restart the client (or reload its MCP servers). That's it.
+
+`npx` fetches and runs the published package on demand. The token and project id are the entire setup for a single project, with no config file (this is **env-only mode**). `@latest` means each client restart picks up the newest published version automatically; pin `overleaf-forge@2.7.1` instead to freeze a version. For multiple projects, per-project contexts, or the SSA bootstrap, see [Configuration](#configuration).
+
+An MCP server is not an app you launch yourself: the client starts it as a subprocess, so "installing" it just means making its command available to the client. The `npx` form above needs no install step. If you would rather have a real command on your `PATH`, install it globally:
+
+```bash
+npm install -g overleaf-forge
+```
+
+and set `"command": "overleaf-forge"` with no `args` (keep the same `env` block). A global install does not auto-update: refresh it yourself with `npm update -g overleaf-forge`. `npx` is recommended precisely because it skips that step.
 
 To hack on the server instead, run it from source:
 
@@ -75,6 +88,20 @@ The `mcpServers` schema is identical across clients; only the file location diff
 
 Restart the client (or reload its MCP servers) after editing, so it spawns the server with the new config.
 
+## Updating
+
+**As a user.** With `overleaf-forge@latest` in your config (the recommended form), restart the client or reload its MCP servers and it fetches the newest published version. If you pinned a version (`overleaf-forge@2.7.1`), change the number. If `npx` seems to keep running an old version, clear its cache with `npx clear-npx-cache` and restart. If you installed globally instead, update with `npm update -g overleaf-forge`.
+
+**As the maintainer (publishing a new release).** From the repository:
+
+```bash
+npm version patch        # or minor / major; bumps package.json and tags
+npm publish              # enter your npm 2FA one-time code when prompted
+git push --follow-tags   # push the commit and the version tag
+```
+
+Anyone on `@latest` picks the new version up on their next client restart.
+
 ## Configuration
 
 Two modes, smallest first.

package/overleaf-mcp-server.js

@@ -7,7 +7,7 @@ import {
   ListToolsRequestSchema,
 } from '@modelcontextprotocol/sdk/types.js';
 import { readFile, writeFile, access, mkdir, readdir, stat, rm, rename, copyFile } from 'fs/promises';
-import { existsSync, realpathSync } from 'fs';
+import { existsSync, realpathSync, readFileSync } from 'fs';
 import { promisify } from 'util';
 import { execFile as execFileCallback } from 'child_process';
 import path from 'path';
@@ -30,6 +30,12 @@ const execFile = promisify(execFileCallback);
 // cache. Anything a user edits resolves user-copy-first, bundled-default-last.
 const PACKAGE_DIR = __dirname;
 
+// Single source of truth for the version: read it from the shipped package.json
+// so `npm version` is the only place a release number changes. Fall back to '0.0.0'
+// if package.json is somehow unreadable (never fatal).
+let PKG_VERSION = '0.0.0';
+try { PKG_VERSION = JSON.parse(readFileSync(path.join(PACKAGE_DIR, 'package.json'), 'utf-8')).version || PKG_VERSION; } catch { /* keep fallback */ }
+
 // Expand a leading ~ to the user's home. Plain join elsewhere assumes absolute.
 function expandHome(p) {
   if (!p) return p;
@@ -927,7 +933,7 @@ async function readContext(projectKey, project) {
 
 // MCP server
 const server = new Server(
-  { name: 'overleaf-forge', version: '2.7.1' },
+  { name: 'overleaf-forge', version: PKG_VERSION },
   { capabilities: { tools: {} } }
 );
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overleaf-forge",
-  "version": "2.7.1",
+  "version": "2.7.2",
   "description": "MCP server to read, edit, compile, and verify Overleaf/LaTeX projects over git: conflict-safe edits, figure upload, clean-build verification, citation and voice linting.",
   "type": "module",
   "main": "overleaf-mcp-server.js",