[RUN-4805] Migrate the MCP SDK from v1 to v2

[smartinellibenedetti]

About this change

Jira Ticket: RUN-4805

Purpose

Upgrades the server from MCP TypeScript SDK v1 to v2. Straight dependency/infra upgrade — no user-facing behavior changes.

This PR by itself does not make the MCP work with the latest protocol revision (2026-07-28). It only moves us onto the v2 SDK library. The changes that actually add support for the latest protocol revision are in a separate PR (#85).

What changed

• SDK v1 → v2 (@modelcontextprotocol/sdk → server/client)
• zod v3 → v4 (required by v2) — fixed the resulting breaking changes (z.record() signature, ZodError.issues)
• Replaced zod-to-json-schema (silently broken under zod v4 — was emitting empty tool schemas) with zod's own z.toJSONSchema, plus a fix so published tool schemas still correctly say additionalProperties: false and don't mark optional params as required
• @modelcontextprotocol/inspector bumped to v2 too
• Cleaned up a couple of v1/zod-v3 leftovers that came in from other branches merged in during a rebase

Testing

npm run build && npm test && npm run validate all green (374/374 tests). CircleCI build/test/docker-build all green. Also manually verified the built server and Docker image respond correctly over real MCP stdio.

Development Checklist

• npm run validate passes locally
• Tests added/updated where needed
• Docs download / RUNDECK_DOCS_PATH unaffected

[Copilot]

Pull request overview

This PR migrates the Rundeck MCP server from the v1 TypeScript SDK (@modelcontextprotocol/sdk) to the v2 split packages (@modelcontextprotocol/server / @modelcontextprotocol/client), including required Zod v4 upgrades and updated JSON Schema generation to satisfy v2’s stricter spec validation.

Changes:

• Replace v1 SDK server/client imports with v2 packages and update request handler registration and result typing.
• Upgrade Zod to v4 and adjust schemas (notably z.record(...)) and Zod error handling (.errors → .issues).
• Replace zod-to-json-schema with z.toJSONSchema(..., { io: "input" }), add schema post-processing for additionalProperties, and extend integration tests to validate schema fidelity via a real client/server round trip.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
TECHNICAL-CAPABILITIES.md	Updates documentation to reflect v2 SDK + Zod v4 dependency changes.
src/tools/resources.ts	Updates z.record usage for Zod v4 compatibility.
src/tools/jobs.ts	Updates nested workflow schema z.record usage for Zod v4 compatibility.
src/tools/api.ts	Updates request body/query param schemas for Zod v4 z.record signature.
src/index.ts	Migrates server entry point to v2 SDK, updates handler wiring, and replaces JSON Schema generation.
src/tests/integration/integration-server-tool-gating.test.ts	Migrates test client to v2 SDK and adds integration assertions for schema correctness.
package.json	Switches dependencies from v1 SDK to v2 server/client packages and upgrades Zod.
package-lock.json	Lockfile updates reflecting the dependency migration.

Suppressed comments (1)

src/index.ts:107

• If schema conversion fails, the fallback JSON Schema currently omits additionalProperties: false, which can cause clients to accept arbitrary tool arguments (even though execution will still be rejected by Zod). To keep advertised schemas strict and consistent with the restoreAdditionalProperties intent, set additionalProperties: false on the fallback object schema as well.

  } catch (error) {
    logger.error("Error converting schema", error);
    return { type: "object", properties: {} };
  }

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.