standup-mr 0.2.1 → 0.3.0

package/CHANGELOG.md

@@ -4,6 +4,37 @@ All notable changes to standup-mr are recorded here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
 [semantic versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.0] - 2026-09-01
+
+### Added
+
+- `standup mcp` — starts the stdio MCP server directly from the CLI, so
+  `npx -y standup-mr mcp` works without a local clone.
+- `standup instructions` — prints the note-writing playbook (the standup
+  skill body, minus its YAML frontmatter) to stdout, for teaching a
+  non-Claude assistant the same rules, e.g.
+  `npx standup-mr instructions >> AGENTS.md`.
+- README section for using the MCP server from Cursor, Codex, or another
+  assistant.
+
+### Fixed
+
+- The skill wrote the note in English even when the user was speaking Turkish.
+  The language rule was buried as a clause inside a sentence about section
+  structure, and `fetch` was called with no `--lang`, so every date label in
+  the JSON came back English and outweighed it. The rule is now a standalone,
+  unmissable line, and the skill passes `--lang` to match the user's language
+  so the payload reinforces the note instead of fighting it.
+- On a machine where both `gh` and `glab` are authenticated, every run failed
+  once before succeeding: the skill called `fetch` with no `--provider`, hit
+  the "both authenticated" error, then retried with the flag. The skill now
+  passes `--provider` on the first call whenever it's known, and only asks the
+  user (instead of guessing) when it genuinely isn't.
+
+Nothing breaking. `@modelcontextprotocol/sdk` moves from a dev dependency to
+a regular dependency, since the CLI can now start the MCP server itself; the
+CLI's `fetch`/`post`/`instructions` path still pulls nothing.
+
 ## [0.2.1] - 2026-08-31
 
 ### Fixed

package/README.md

@@ -76,6 +76,52 @@ skill. From inside Claude Code:
 
 Then type `/standup`. Updates come with `/plugin marketplace update standup-mr`.
 
+### Using it from Cursor, Codex, or another assistant
+
+If you're not using Claude Code, wire up the MCP server for live data and
+paste in the note-writing rules separately.
+
+**Cursor** — add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json`
+(project-local):
+
+```json
+{
+  "mcpServers": {
+    "standup": {
+      "command": "npx",
+      "args": ["-y", "standup-mr", "mcp"],
+      "env": {
+        "GITHUB_TOKEN": "ghp_..."
+      }
+    }
+  }
+}
+```
+
+**Codex** — add to `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.standup]
+command = "npx"
+args = ["-y", "standup-mr", "mcp"]
+
+[mcp_servers.standup.env]
+GITHUB_TOKEN = "ghp_..."
+```
+
+The exact config key and file path are version-dependent for both clients —
+if a snippet above doesn't work, check [Cursor's MCP
+docs](https://docs.cursor.com/context/mcp) or Codex's own config
+documentation for the current format rather than trusting this file blindly.
+
+The tool only returns data; the assistant still needs the note-writing rules
+that the Claude Code skill carries. Paste them into whatever instructions
+file your assistant reads (e.g. `AGENTS.md`):
+
+```bash
+npx standup-mr instructions >> AGENTS.md
+```
+
 ## `--markdown` is a digest, not a written note
 
 `--markdown` organizes the raw material into readable sections. It does **not**
@@ -162,7 +208,9 @@ the `standup` skill changed along with the report shape.
 
 ## Requirements
 
-Node 20 or newer. No runtime dependencies.
+Node 20 or newer. The CLI core (`fetch`, `post`, `instructions`) pulls no
+runtime dependencies. The MCP server (`mcp` command) brings one:
+`@modelcontextprotocol/sdk`.
 
 ## License
 

package/dist/cli.js

@@ -8,8 +8,9 @@ import {
 } from "./chunk-DL2P3XR6.js";
 
 // src/cli/cli.ts
-import { realpathSync } from "fs";
-import { pathToFileURL } from "url";
+import { existsSync, readFileSync, realpathSync } from "fs";
+import { dirname, join } from "path";
+import { fileURLToPath, pathToFileURL } from "url";
 import { parseArgs } from "util";
 
 // src/cli/cli.constants.ts
@@ -19,13 +20,20 @@ Usage:
   standup fetch [--provider github|gitlab] [--host H] [--token T]
                 [--lang en|tr] [--markdown]
   standup post (--slack URL | --discord URL) [--text TEXT]
+  standup mcp
+  standup instructions
 
 The provider is taken from --provider, then STANDUP_PROVIDER, then whichever of
 GITHUB_* / GITLAB_* is set, then whichever of gh / glab is logged in.
 
 Credentials resolve as: flag, then GITHUB_HOST / GITHUB_TOKEN (or GITLAB_HOST /
 GITLAB_TOKEN), then the gh or glab config.
---text defaults to '-', meaning read stdin.`;
+--text defaults to '-', meaning read stdin.
+
+standup mcp starts the stdio MCP server, exposing get_standup_data.
+standup instructions prints the note-writing playbook (the standup skill body)
+to stdout, for teaching a non-Claude assistant the same rules, e.g.:
+  npx standup-mr instructions >> AGENTS.md`;
 
 // src/cli/cli.ts
 async function readStdin() {
@@ -33,6 +41,27 @@ async function readStdin() {
   for await (const chunk of process.stdin) chunks.push(Buffer.from(chunk));
   return Buffer.concat(chunks).toString("utf8");
 }
+function findPackageRoot(startDir) {
+  let dir = startDir;
+  while (!existsSync(join(dir, "package.json"))) {
+    const parent = dirname(dir);
+    if (parent === dir) {
+      throw new Error(`Could not locate package.json above ${startDir}`);
+    }
+    dir = parent;
+  }
+  return dir;
+}
+function readStandupSkillBody() {
+  const moduleDir = dirname(fileURLToPath(import.meta.url));
+  const skillPath = join(findPackageRoot(moduleDir), "skills", "standup", "SKILL.md");
+  if (!existsSync(skillPath)) {
+    throw new Error(`Cannot find the standup skill file at ${skillPath}`);
+  }
+  const content = readFileSync(skillPath, "utf8");
+  const withoutFrontmatter = content.replace(/^---\r?\n[\s\S]*?\r?\n---\r?\n/, "");
+  return withoutFrontmatter.replace(/^\n+/, "");
+}
 async function main(argv) {
   const [command, ...rest] = argv;
   if (!command || command === "--help" || command === "-h") {
@@ -80,6 +109,18 @@ async function main(argv) {
       await postWebhook(url, text, values.slack ? "slack" : "discord");
       return 0;
     }
+    if (command === "mcp") {
+      const moduleDir = dirname(fileURLToPath(import.meta.url));
+      const serverPath = join(findPackageRoot(moduleDir), "dist", "mcp", "server.js");
+      const serverUrl = pathToFileURL(serverPath).href;
+      const { main: startMcpServer } = await import(serverUrl);
+      await startMcpServer();
+      return 0;
+    }
+    if (command === "instructions") {
+      process.stdout.write(readStandupSkillBody());
+      return 0;
+    }
     process.stderr.write(`Unknown command: ${command}
 
 ${USAGE}

package/dist/mcp/server.js

@@ -3,6 +3,8 @@
 // mcp/server.ts
 import { realpathSync } from "fs";
 import { pathToFileURL } from "url";
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 
 // src/config/config.ts
 import { execFileSync } from "child_process";
@@ -964,9 +966,7 @@ async function collect(options = {}) {
   return buildReport(provider, /* @__PURE__ */ new Date(), options.lang ?? "en");
 }
 async function main() {
-  const { McpServer } = await import("@modelcontextprotocol/sdk/server/mcp.js");
-  const { StdioServerTransport } = await import("@modelcontextprotocol/sdk/server/stdio.js");
-  const server = new McpServer({ name: "standup-mr", version: "0.2.1" });
+  const server = new McpServer({ name: "standup-mr", version: "0.3.0" });
   server.tool(
     "get_standup_data",
     "Collect merge-request-based standup data from GitLab or GitHub. Returns the previous working day activity, open merge requests or pull requests bucketed by state (ready / blocked / draft / stale), pending reviews, and the error lines from any failed pipeline or check.",
@@ -987,14 +987,9 @@ try {
 }
 if (entryUrl && import.meta.url === entryUrl) {
   main().catch((error) => {
-    if (error instanceof Error && error.code === "ERR_MODULE_NOT_FOUND") {
-      process.stderr.write(
-        "standup-mr MCP server requires the optional dependency @modelcontextprotocol/sdk. Install it with: npm install @modelcontextprotocol/sdk\n"
-      );
-      process.exitCode = 1;
-      return;
-    }
-    throw error;
+    process.stderr.write(`${error instanceof Error ? error.message : String(error)}
+`);
+    process.exitCode = 1;
   });
 }
 export {

package/mcp/README.md

@@ -3,12 +3,6 @@
 Exposes one tool, `get_standup_data`, for either GitLab or GitHub, returning
 the same JSON as `standup fetch`.
 
-## Install
-
-```bash
-npm install standup-mr @modelcontextprotocol/sdk
-```
-
 ## Configure
 
 GitLab:
@@ -17,8 +11,8 @@ GitLab:
 {
   "mcpServers": {
     "standup": {
-      "command": "node",
-      "args": ["/absolute/path/to/standup-mr/dist/mcp/server.js"],
+      "command": "npx",
+      "args": ["-y", "standup-mr", "mcp"],
       "env": {
         "GITLAB_HOST": "gitlab.example.com",
         "GITLAB_TOKEN": "glpat-..."
@@ -30,6 +24,26 @@ GitLab:
 
 GitHub:
 
+```json
+{
+  "mcpServers": {
+    "standup": {
+      "command": "npx",
+      "args": ["-y", "standup-mr", "mcp"],
+      "env": {
+        "GITHUB_HOST": "github.com",
+        "GITHUB_TOKEN": "ghp_..."
+      }
+    }
+  }
+}
+```
+
+### Running from a clone
+
+If you're working from a local clone instead of the published package, point
+`command` at `node` and `args` at the absolute path to the built server:
+
 ```json
 {
   "mcpServers": {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "standup-mr",
-    "version": "0.2.1",
+    "version": "0.3.0",
     "description": "Standup notes from merge request state, not commit logs.",
     "keywords": [
         "standup",
@@ -58,19 +58,13 @@
         "typecheck": "tsc --noEmit",
         "prepublishOnly": "tsup"
     },
+    "dependencies": {
+        "@modelcontextprotocol/sdk": "^1.0.0"
+    },
     "devDependencies": {
-        "@modelcontextprotocol/sdk": "^1.0.0",
         "@types/bun": "^1.0.0",
         "@types/node": "^22.0.0",
         "tsup": "^8.0.0",
         "typescript": "^5.5.0"
-    },
-    "peerDependencies": {
-        "@modelcontextprotocol/sdk": "^1.0.0"
-    },
-    "peerDependenciesMeta": {
-        "@modelcontextprotocol/sdk": {
-            "optional": true
-        }
     }
 }

package/skills/standup/SKILL.md

@@ -19,22 +19,43 @@ Not a commit log — what finished, what is waiting, what is stuck.
 npx standup-mr fetch
 ```
 
-Prints one JSON document. The command picks GitLab or GitHub on its own — from
-flags, host, environment, or whichever of `gh`/`glab` is logged in. If the user
-already said which one they mean, pass it explicitly instead of guessing:
+Prints one JSON document. Nothing else needs running: the command resolves
+the host and token, works out which day to report on, and reads failed job
+logs itself.
+
+**Know the provider before the first call, don't discover it from a failure.**
+If the user has named GitHub or GitLab, or it is otherwise obvious from
+context, pass it on the very first invocation:
 
 ```bash
 npx standup-mr fetch --provider github
 npx standup-mr fetch --provider gitlab
 ```
 
-Add `--lang tr` for Turkish date labels. Nothing else needs running: the
-command resolves the host and token, works out which day to report on, and
-reads failed job logs itself.
-
-If the command exits non-zero, relay its stderr verbatim — do not invent a
-cause. The usual fix is `gh auth login` or `glab auth login`, depending on
-which provider it was trying to reach.
+If it is not known, do not guess. The command resolves it itself, in order:
+`--provider` → a recognisable `--host` → `STANDUP_PROVIDER` → the
+`GITHUB_*`/`GITLAB_*` env pair → whichever of `gh`/`glab` is logged in → an
+error naming what it found. On a machine where both `gh` and `glab` are
+authenticated, that resolution is ambiguous and the bare call fails with
+`Both gh and glab are authenticated. Pass --provider github or --provider
+gitlab.` — if you hit that, ask the user which one they mean rather than
+picking one silently, unless the conversation already makes it obvious, in
+which case pass that provider and say so in the note.
+
+If the command exits non-zero for any other reason, relay its stderr verbatim
+— do not invent a cause. The usual fix is `gh auth login` or `glab auth
+login`, depending on which provider it was trying to reach.
+
+**Pass `--lang` to match the language the user is speaking** — `--lang tr`
+for Turkish. It only affects the date labels inside the JSON (`"label":
+"Friday, 28 August"` → `"Cuma, 28 Ağustos"`); the prose of the note is always
+your own work, in the user's language, regardless of this flag. Passing it
+matters because the payload is otherwise ~1000 lines of English labels
+fighting a note you're trying to write in another language. Today `--lang`
+supports only `en` (default) and `tr` — any other value silently falls back
+to English labels. If the user speaks a language `--lang` doesn't cover,
+still write the note in their language; just leave the date labels in
+English rather than passing a value that won't take effect.
 
 ## 2. Shape of the JSON
 
@@ -57,8 +78,12 @@ under its own `label`, never merged into a single "yesterday".
 
 ## 3. Write the note
 
-Three sections: **Previous day · Today · Blockers**. Short, in the language the
-user is speaking, phrased the way they would say it out loud.
+**Write in the language the user is speaking, not the language of the JSON.**
+The payload's labels and field names are English regardless of `--lang`
+coverage — that is source data, not a cue for what language to write in.
+
+Three sections: **Previous day · Today · Blockers**. Short, phrased the way
+the user would say it out loud.
 
 ### Previous day