[dependabot]

Removes @modelcontextprotocol/server. It's no longer used after updating ancestor dependency @mcp-b/webmcp-polyfill. These dependencies need to be updated together.

Removes @modelcontextprotocol/server

Updates @mcp-b/webmcp-polyfill from 5.1.0 to 6.0.3

Release notes

Sourced from @​mcp-b/webmcp-polyfill's releases.

@​mcp-b/webmcp-polyfill@​6.0.3

Patch Changes

• d1c3454: A declarative form that lost a name to an earlier form no longer takes the name over when its attributes change. The registered form keeps the tool until it is removed or renamed, matching Chrome and the WebMCP WPT.

@​mcp-b/webmcp-polyfill@​6.0.2

No release notes provided.

@​mcp-b/webmcp-polyfill@​6.0.1

No release notes provided.

@​mcp-b/webmcp-polyfill@​6.0.0

Major Changes

• 160acc3: Breaking: replace the MCP-B core implementation with the upstream WebMCP polyfill. Declarative tools remain available until upstream supports them. This package vendors upstream revision 6bf6c57 and uses webmcp-types@0.1.9 for the browser contract.

  The existing package name remains available as a temporary compatibility alias. It will eventually be removed; no removal date is set. Sites using declarative tools should keep it until the upstream polyfill supports them. Follow the official upstream installation instructions when migrating to its distribution. Until that release is available, keep using @mcp-b/webmcp-polyfill with the changes below.

  Replace initialization and cleanup

  - import { initializeWebMCPPolyfill } from '@mcp-b/webmcp-polyfill';
  - initializeWebMCPPolyfill({ installTestingShim: true });
  + import { installWebMCP } from '@mcp-b/webmcp-polyfill';
  + installWebMCP();

  installWebMCP() takes no options. Remove imports of WebMCPPolyfillInitOptions and calls to cleanupWebMCPPolyfill(): the upstream context lives for the lifetime of the document. To remove tools, pass an AbortController's signal to registerTool(tool, { signal }) and abort that controller during cleanup. Tests that need a completely fresh runtime should create a new page or document realm.

  The @mcp-b/webmcp-polyfill/iife export and dist/index.iife.js script still install automatically. The script's global is now WebMCPPolyfill.installWebMCP (formerly WebMCPPolyfill.initializeWebMCPPolyfill), and it ignores window.__webMCPPolyfillOptions; remove that assignment. An ESM import alone does not install the polyfill. Pin the major in CDN URLs (@mcp-b/webmcp-polyfill@6); pages that are not ready to migrate pin @5 instead of @latest.

... (truncated)

Changelog

Sourced from @​mcp-b/webmcp-polyfill's changelog.

6.0.3

Patch Changes

• d1c3454: A declarative form that lost a name to an earlier form no longer takes the name over when its attributes change. The registered form keeps the tool until it is removed or renamed, matching Chrome and the WebMCP WPT.

6.0.2

6.0.1

6.0.0

Major Changes

• 160acc3: Breaking: replace the MCP-B core implementation with the upstream WebMCP polyfill. Declarative tools remain available until upstream supports them. This package vendors upstream revision 6bf6c57 and uses webmcp-types@0.1.9 for the browser contract.

  The existing package name remains available as a temporary compatibility alias. It will eventually be removed; no removal date is set. Sites using declarative tools should keep it until the upstream polyfill supports them. Follow the official upstream installation instructions when migrating to its distribution. Until that release is available, keep using @mcp-b/webmcp-polyfill with the changes below.

  Replace initialization and cleanup

  - import { initializeWebMCPPolyfill } from '@mcp-b/webmcp-polyfill';
  - initializeWebMCPPolyfill({ installTestingShim: true });
  + import { installWebMCP } from '@mcp-b/webmcp-polyfill';
  + installWebMCP();

  installWebMCP() takes no options. Remove imports of WebMCPPolyfillInitOptions and calls to cleanupWebMCPPolyfill(): the upstream context lives for the lifetime of the document. To remove tools, pass an AbortController's signal to registerTool(tool, { signal }) and abort that controller during cleanup. Tests that need a completely fresh runtime should create a new page or document realm.

  The @mcp-b/webmcp-polyfill/iife export and dist/index.iife.js script still install automatically. The script's global is now WebMCPPolyfill.installWebMCP (formerly WebMCPPolyfill.initializeWebMCPPolyfill), and it ignores window.__webMCPPolyfillOptions; remove that assignment. An ESM import alone does not install the polyfill. Pin the major in CDN URLs (@mcp-b/webmcp-polyfill@6); pages that are not ready to migrate pin @5 instead of @latest.

... (truncated)

Commits

• a0bb194 chore(release): version packages
• d1c3454 fix(webmcp-polyfill): keep a declarative tool name with the form that registe...
• 1d978f3 chore(release): version packages
• 97e40ca chore(release): version packages
• 383a9eb chore(release): version packages
• bc0c924 fix(webmcp-polyfill): keep responded declarative calls when the form is removed
• 4d07bdf fix(webmcp-polyfill): settle declarative submits after dispatch
• 01aeb9c fix(webmcp-polyfill): vendor upstream 6bf6c57
• 160acc3 feat(root)!: adopt upstream WebMCP core and simplify React hooks (#329)
• See full diff in compare view