feat: switch to ResourceRenderer

[idosal]

BREAKING CHANGE:
Cuts off deprecated exports (such as HtmlResource) and overhauls the documentation.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	remote-mcp-server-authless	28ea639	Jul 04 2025, 10:42 PM

[Copilot]

Pull Request Overview

This PR replaces deprecated server/client resource components with a unified ResourceRenderer, removes legacy compatibility code, and updates documentation to focus on the new API.

• Remove deprecated HtmlResource/RemoteDomResource exports and legacy URI handling
• Refactor examples and tests to use ResourceRenderer
• Overhaul README and docs content, navigation, and metadata

Reviewed Changes

Copilot reviewed 23 out of 31 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/server/README.md	Updated nav links, added Core Concepts & Security
packages/client/src/utils/processResource.ts	Dropped legacy ui-app:// handling
packages/client/src/index.ts	Removed deprecated exports
packages/client/src/components/tests/HtmlResource.test.tsx	Removed backcompat tests
packages/client/src/components/ResourceRenderer.tsx	Updated props, switched to ResourceRenderer
examples/remote-dom-demo/src/App.tsx	Switched to ResourceRenderer in demo
docs/**/*	Comprehensive docs overhaul

Files not reviewed (2)

• docs/package-lock.json: Language not supported
• examples/server/pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (6)

packages/client/src/components/ResourceRenderer.tsx:8

• The props type no longer declares library or remoteElements, yet both are destructured and used. Add library?: ComponentLibrary and remoteElements?: RemoteElementConfiguration[] back into ResourceRendererProps.

type ResourceRendererProps = Omit<

packages/client/src/components/ResourceRenderer.tsx:32

• remoteElements is being passed to RemoteDomResource but not typed in ResourceRendererProps. Ensure this prop is declared and documented in the props interface.

}

examples/remote-dom-demo/src/App.tsx:146

• Remote DOM examples use ResourceRenderer without the required remoteElements prop. Include your element definitions (e.g., remoteElements={[remoteTextDefinition, remoteButtonDefinition]}) when rendering Remote DOM resources.

          <ResourceRenderer

packages/server/README.md:13

• The anchor ID contains backticks which may break the link. Use a plain slug (e.g., #-whats-mcp-ui) instead of including backticks and apostrophes.

  <a href="#-what's-`mcp-ui`?">What's mcp-ui?</a> •

packages/server/README.md:17

• You have two identical Core Concepts links in the nav. Remove the duplicate entry to avoid confusion.

  <a href="#-core-concepts">Core Concepts</a> •

packages/client/src/components/ResourceRenderer.tsx:13

• There's no test covering the supportedContentTypes filter in ResourceRenderer. Add a unit test to verify that unsupported types render the error message.

  supportedContentTypes?: ResourceContentType[];