Skip to content

Release 17.0.0-beta.6#25

Merged
hifi-phil merged 12 commits intomainfrom
release/17.0.0-beta.6
Mar 30, 2026
Merged

Release 17.0.0-beta.6#25
hifi-phil merged 12 commits intomainfrom
release/17.0.0-beta.6

Conversation

@hifi-phil
Copy link
Copy Markdown
Contributor

Summary

  • CLI E2E tests covering full pipeline (scaffold → init → discover → generate → compile → test → worker)
  • Container mode for wrapping MCP servers via chaining
  • Template bug fixes (McpOAuthComposer resilience, appsettings, self-signed certs, MSW conditional)
  • Skill improvements (compile-per-file, builder examples, anti-pattern warnings)

Version bump

All packages: 17.0.0-beta.517.0.0-beta.6

🤖 Generated with Claude Code

hifi-phil and others added 12 commits January 27, 2026 14:50
* Add MIT license and bump version to 17.0.0-beta.1

- Add MIT LICENSE file
- Update monorepo version to align with Umbraco 17

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* Standardise version to 17.0.0-beta.1 and update repository URLs

- Bump SDK version from 1.0.0-beta.1 to 17.0.0-beta.1
- Update all repository URLs to github.com/umbraco/Umbraco-MCP-Base
- Add junit.xml to .gitignore

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Phil Whittaker <pjw@umbraco.dk>
Co-authored-by: Claude <noreply@anthropic.com>
- Bump PSW_VERSION from 1.2.0-alpha01 to 1.2.0-alpha03
- Replace --no-run with --build-only (renamed upstream in PR #195)
- Remove -u flag (sets SQLite defaults, conflicts with --database-type)
- Add --run-dir to explicitly set script execution directory
- Use dotnet tool update instead of install to handle upgrades
- Auto-update PSW when installed version doesn't match expected
- Remove .gitkeep from demo-site/ before PSW runs to avoid empty dir issues

Co-authored-by: Phil Whittaker <pjw@umbraco.dk>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
  Simplify createToolResult() to a single `data` parameter and add a
  compatibility mode that controls whether tool results include both
  `structuredContent` and a JSON-stringified `content` fallback.

  By default, both fields are populated for maximum MCP client
  compatibility. Set `DISABLE_OUTPUT_COMPATIBILITY_MODE=true` to return
  `structuredContent` only, reducing token duplication for clients that
  support it (e.g. Claude Code, Claude Desktop).

  - Simplify createToolResult(data?) — replaces the 3-parameter overload
  - Add configureToolResultMode() for server startup configuration
  - Fall back to env var for hosted Workers where config isn't available
  - Preserve empty text content for void (no-data) tool results
  - Update test environment to set mode via env var
Simplify tool result API and add output compatibility mode
 Add hosted MCP package and multi-transport chaining

  - Add @umbraco-cms/mcp-hosted package for Cloudflare Worker-hosted MCP
    servers with OAuth authorization, consent screens, multi-site support,
    and KV-based token storage
  - Add registerChainedTools helper supporting stdio and in-process
    transports to proxy tools from other MCP servers
  - Migrate SDK HTTP client from axios to native fetch
  - Add readOnlyHint annotation filtering and in-process MCP connections
  - Add worker entry point, tunnel support, and get-server-info tool to
    template
  - Add integration and E2E test infrastructure for hosted and chained MCP
  - Add add-tool, add-test, and add-eval Claude Code skills
  - Fix scaffold to rewrite @umbraco-cms/mcp-hosted file: refs and exclude
    test-results/ from template copy
Resolves conflicts to bring release changes (version bumps, hosted-mcp
CI pipeline, jest-junit, CLAUDE.md release docs) into dev.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Merge main back into dev after beta.5 release
loadServerConfig is async but tests were calling it synchronously
with mockReturnValue instead of mockResolvedValue. This caused
TypeScript errors when scaffolding new projects via create-mcp-server.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Without this, Jest globals (describe, it, expect) don't resolve
in the IDE when the types array is explicitly set.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ents

Comprehensive E2E testing for the create-mcp-server CLI, bug fixes found during manual testing, a new container mode for wrapping MCP servers, and template/skill improvements from real-world usage feedback.

  CLI Bug Fixes

  - McpOAuthComposer.cs: Try-catch resilience so Umbraco starts before DB is ready (unattended install)
  - setup-instance.ts: Write connection string to appsettings.local.json, unattended install config to appsettings.Development.json, patch Program.cs to load appsettings.local.json
  - Template TS errors: Fix createToolResult signature, jest.fn typing in server-config.test.ts
  - collections.ts cleanup: removeExamples() now cleans up collections.ts imports

  E2E Tests

  CLI E2E (19 deterministic steps, cli-e2e.test.ts):
  - Scaffold → init (Forms + SQL Server) → start Umbraco → API user creation → token verification → swagger discovery → .discover.json → generate client → TypeScript compile → unit tests → integration test against real Umbraco → real API calls → hosted worker

  Container Mode E2E (5 steps):
  - Scaffold → remove API tools → compile → build → worker starts

  Skill E2E (3 steps, skill-e2e.test.ts, opt-in via RUN_SKILL_TESTS=true):
  - /build-tools creates Language collection that compiles
  - /build-tools-tests creates integration tests
  - Integration tests pass against real Umbraco

  Infrastructure: Random SQL Server database per run, KEEP_E2E_ASSETS=true for preserving project between runs, test:e2e:revert for resetting skill output, test:e2e:cleanup for teardown.

  Container Mode

  New init prompt choice: "Container mode — wrap other MCP servers via chaining, no direct API tools"
  - removeApiTools() strips orval, generated client, example tools while keeping chaining infrastructure
  - Tool mode question comes after Umbraco instance setup (instance always needed for OAuth)

  Template Improvements

  - Self-signed certs in Jest: Override globalThis.fetch with undici's fetch (Node 22's built-in fetch ignores NODE_TLS_REJECT_UNAUTHORIZED in Jest VM sandbox)
  - MSW conditional: Gate setupMswServer() behind USE_MOCK_API=true (was blocking real API calls in integration tests)
  - .gitignore: Added to template (demo-site/, .env, appsettings.local.json, .discover.json)

  Skill Improvements

  - build-tools: Compile after EACH tool file, not batch
  - build-tools-tests: Complete working builder example with delete/cleanup, anti-pattern warning for result.content[0].text (must use createSnapshotResult), initializeUmbracoFetch in setup.ts template, read-only collection guidance
  - count-tools: Replace glob npm package with Node 22 built-in fs.globSync
  - Plugin install: Correct commands in discover output (/plugin marketplace add + /plugin install)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hifi-phil hifi-phil merged commit 4a6f872 into main Mar 30, 2026
hifi-phil added a commit that referenced this pull request Mar 30, 2026
Release 17.0.0-beta.6 (#25) - Add CLI E2E tests, container mode, temp…
@hifi-phil hifi-phil deleted the release/17.0.0-beta.6 branch April 27, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant