@programinglive/dev-workflow-mcp-server 1.4.5 → 1.4.6

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [1.4.6](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.4.5...v1.4.6) (2025-11-27)
+
+
+### 🧹 Chores
+
+* add MCP registry metadata (mcpName & server.json) ([66caea1](https://github.com/programinglive/dev-workflow-mcp-server/commit/66caea1d684473cfc916917faa42e16fc4ad9e14))
+
 ### [1.4.5](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.4.4...v1.4.5) (2025-11-27)
 
 

package/README.md

@@ -228,6 +228,28 @@ For MCP server usage, point your client at `index.js` (source) to avoid stdio tr
 - Performance optimization
 - Embedding in other projects
 
+### MCP Tools Registry (Publishing)
+
+This package is configured for the official MCP Tools Registry using **npm package deployment**:
+
+- `package.json` declares `mcpName: "io.github.programinglive/dev-workflow-mcp-server"`.
+- `server.json` describes the server and links it to the npm package `@programinglive/dev-workflow-mcp-server`.
+
+To publish a new server version to the registry:
+
+1. Release a new npm version (for example):
+   - `npm test`
+   - `npm run release:patch` (runs your existing release pipeline and publishes to npm)
+2. Verify the new version exists on npm:
+   - `npm view @programinglive/dev-workflow-mcp-server version`
+3. Install the MCP publisher CLI (once per machine):
+   - `brew install mcp-publisher` (or follow the docs at https://modelcontextprotocol.info/tools/registry/publishing/)
+4. From this repo root, authenticate and publish:
+   - `mcp-publisher login github`
+   - `mcp-publisher publish`
+5. Optionally verify in the registry:
+   - `curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.programinglive/dev-workflow-mcp-server"`
+
 #### PowerShell CLI tip
 
 When invoking the lightweight CLI from PowerShell, use `--%` to prevent PowerShell from rewriting JSON arguments, for example:

package/docs/release-notes/RELEASE_NOTES.md

@@ -4,6 +4,9 @@ Authoritative history of user-visible changes for the Development Workflow MCP S
 
 ## Unreleased
 
+## 1.4.5 — 2025-11-27 — 🐛 Bug Fixes
+- display dynamic version in web dashboard from /api/version (69f561d)
+
 ## 1.4.4 — 2025-11-27 — ♻️ Refactors
 - consolidate workflow state to root .state folder only (3d69a14)
 - ensure release guard uses freshest workflow state (e07eb42)

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "@programinglive/dev-workflow-mcp-server",
-  "version": "1.4.5",
+  "version": "1.4.6",
   "description": "MCP server to enforce development workflow discipline",
   "homepage": "https://devworkflow.programinglive.com/",
+  "mcpName": "io.github.programinglive/dev-workflow-mcp-server",
   "type": "module",
   "main": "index.js",
   "bin": {

package/server.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
+  "name": "io.github.programinglive/dev-workflow-mcp-server",
+  "description": "MCP server to enforce development workflow discipline",
+  "version": "1.4.6",
+  "packages": [
+    {
+      "registry_type": "npm",
+      "identifier": "@programinglive/dev-workflow-mcp-server",
+      "version": "1.4.6"
+    }
+  ]
+}

package/tests/mcpRegistry.test.js

@@ -0,0 +1,55 @@
+import { test } from "node:test";
+import assert from "node:assert";
+import { readFile } from "node:fs/promises";
+import path from "node:path";
+
+const projectRoot = process.cwd();
+
+async function readJson(relativePath) {
+  const fullPath = path.join(projectRoot, relativePath);
+  const content = await readFile(fullPath, "utf-8");
+  return JSON.parse(content);
+}
+
+test("package.json includes mcpName for MCP registry", async () => {
+  const pkg = await readJson("package.json");
+
+  assert.strictEqual(
+    pkg.mcpName,
+    "io.github.programinglive/dev-workflow-mcp-server",
+    "package.json should declare mcpName matching the MCP server namespace",
+  );
+});
+
+test("server.json is configured for npm package deployment", async () => {
+  const server = await readJson("server.json");
+
+  assert.strictEqual(
+    server.name,
+    "io.github.programinglive/dev-workflow-mcp-server",
+    "server.json name should match the MCP server namespace",
+  );
+
+  assert.ok(Array.isArray(server.packages) && server.packages.length > 0,
+    "server.json should declare at least one package entry",
+  );
+
+  const npmPkg = server.packages[0];
+
+  assert.strictEqual(
+    npmPkg.registry_type,
+    "npm",
+    "First server.json package entry should use npm registry_type",
+  );
+
+  assert.strictEqual(
+    npmPkg.identifier,
+    "@programinglive/dev-workflow-mcp-server",
+    "server.json npm identifier should match the published npm package name",
+  );
+
+  assert.ok(
+    typeof npmPkg.version === "string" && npmPkg.version.length > 0,
+    "server.json npm package version should be a non-empty string",
+  );
+});