chore(release): sync server.json to 1.0.101 and enforce parity with pyproject.toml in CI

server.json had drifted to 1.0.93 while pyproject.toml is at 1.0.101. The MCP Registry publish step has been failing with cannot publish duplicate version on every release since (v1.0.99, .100, .101 all rejected) because the registry already has 1.0.93 from a prior publish.

Catch server.json up to 1.0.101 and replace the no-op validate-version CI step with a real check that fails the build when pyproject.toml and server.json versions diverge.

Author: nictuku

.github/workflows/test.yml

@@ -49,8 +49,13 @@ jobs:
       with:
         python-version: "3.10"
 
-    - name: Check version bump
+    - name: Check pyproject.toml and server.json versions match
       run: |
-        # This is a simple check - you might want to make it more sophisticated
-        echo "Current version in pyproject.toml:"
-        grep "version = " pyproject.toml 
+        PY_VERSION=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+        JSON_VERSION=$(python -c "import json; print(json.load(open('server.json'))['version'])")
+        echo "pyproject.toml version: $PY_VERSION"
+        echo "server.json version:    $JSON_VERSION"
+        if [ "$PY_VERSION" != "$JSON_VERSION" ]; then
+          echo "::error::pyproject.toml ($PY_VERSION) and server.json ($JSON_VERSION) must match. Bump both."
+          exit 1
+        fi 

server.json

@@ -2,7 +2,7 @@
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "co.pipeboard/meta-ads-mcp",
   "description": "Facebook / Meta Ads automation with AI: analyze performance, test creatives, optimize spend.",
-  "version": "1.0.93",
+  "version": "1.0.101",
   "remotes": [
     {
       "type": "streamable-http",