Major Changes
Package Renaming
Several packages have been renamed for clarity and consistency:| Old Name | New Name | Migration |
|---|---|---|
@mcp-b/mcp-react-hooks | @mcp-b/react-webmcp | Update import statements |
useMcpServer() hook | useWebMCP() | Replace hook calls |
API Changes
@mcp-b/react-webmcp- Removed
useMcpServer()hook - useuseWebMCP()instead - New
useWebMCPContext()hook for read-only context - Automatic registration/cleanup (no manual
useEffectneeded) - Built-in Zod support for type-safe schemas
navigator.modelContext API
Version 1.0.0 aligns with the W3C Web Model Context API proposal:registerTool()is now the recommended approach (returnsunregister())provideContext()only for base tools (replaces all base tools)- Two-bucket tool management system introduced
New Features
@mcp-b/global
- ✨ Two-bucket tool management (base vs dynamic tools)
- ✨ IIFE build for CDN usage (no build step required)
- ✨ Event-based tool call handling
- ✨ Improved TypeScript types
@mcp-b/react-webmcp
- ✨
useWebMCP()hook with automatic lifecycle management - ✨
useWebMCPContext()for read-only tools - ✨ Execution state tracking (
isExecuting,lastResult,error) - ✨
McpClientProvideranduseMcpClient()for consuming tools
@mcp-b/transports
- ✨ Enhanced origin validation
- ✨ Keep-alive support for extension transports
- ✨ Server discovery for tab clients
- ✨ Cross-extension communication support
@mcp-b/extension-tools
- ✨ 62+ Chrome Extension API wrappers
- ✨ Comprehensive TypeScript definitions
- ✨ Zod-based validation
- ✨ Manifest V3 compatible
Migration Guide
1
Update package names
2
Update imports
3
Replace useMcpServer with useWebMCP
4
Update vanilla JS tool registration
5
Test your integration
- Verify all tools register correctly
- Test tool execution with MCP-B extension
- Check that tools unregister on component unmount
- Validate input schemas work as expected
Bug Fixes
- Fixed tool name collision errors
- Improved error messages for schema validation
- Fixed memory leaks in React StrictMode
- Corrected TypeScript definitions for transport options
- Fixed race condition in extension port connections
Performance Improvements
- Reduced bundle size by 30%
- Optimized tool registration performance
- Improved transport message handling
- Better memory management in long-running sessions
Upcoming Features
Version 1.1.0 (Planned - Q1 2025)
- 🔄 Firefox extension support
- 🔄 Enhanced developer tools
- 🔄 Performance monitoring
- 🔄 Tool analytics and insights
Version 1.2.0 (Planned - Q2 2025)
- 🔄 Safari extension support
- 🔄 Advanced caching strategies
- 🔄 Tool versioning support
- 🔄 Multi-language tool descriptions
Deprecation Notices
Deprecated in 1.0.0
@mcp-b/mcp-react-hookspackage (use@mcp-b/react-webmcp)useMcpServer()hook (useuseWebMCP())- Implicit tool registration patterns (use explicit
registerTool())
Migration Timeline
| Version | Release | Deprecated Features | Removed Features |
|---|---|---|---|
| 1.0.0 | Jan 2025 | Old package names | - |
| 1.5.0 | Jun 2025 | - | - |
| 2.0.0 | Sep 2025 | - | Old packages, useMcpServer() |
Breaking Change Policy
WebMCP follows Semantic Versioning:- Major versions (X.0.0): Breaking changes, major new features
- Minor versions (1.X.0): New features, backward compatible
- Patch versions (1.0.X): Bug fixes, backward compatible
Deprecation Process
- Announce: Deprecated features announced in release notes
- Warn: Console warnings added in code
- Grace period: Minimum 6 months before removal
- Remove: Removed in next major version
Stay Updated
GitHub Releases
View detailed release notes
NPM Changelog
Browse version history
Discord Community
Discuss updates and ask questions
Migration Guides
Step-by-step upgrade instructions
Reporting Issues
Found a bug or regression? Please report it:- Check existing issues
- Create a new issue with:
- Version numbers
- Steps to reproduce
- Expected vs actual behavior
- Browser and extension versions
For security vulnerabilities, please email [email protected] instead of creating a public issue.
