Hello, friends! Consistent with the README below, could we update the npm deprecation message for @modelcontextprotocol/server-brave-search to explicitly direct users to @brave/brave-search-mcp-server?
|
- **[Brave Search](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/brave-search)** - Web and local search using Brave's Search API. Has been replaced by the [official server](https://github.com/brave/brave-search-mcp-server). |
The following would be terrific:
npm deprecate @modelcontextprotocol/server-brave-search "This package has moved to @brave/brave-search-mcp-server, the official Brave-maintained MCP server. Please update your configuration to use: npx -y @brave/brave-search-mcp-server"
The old package still sees a meaningful amount of usage, so this would help existing users find the actively maintained server.
If there's interest, I'd also be happy to put together a small 0.6.3 compatibility release that delegates to @brave/brave-search-mcp-server. That could keep existing configurations working while still nudging users toward the new package name.
I'm happy to do the implementation and testing, and work with whatever publishing process you all prefer.
Hello, friends! Consistent with the README below, could we update the npm deprecation message for @modelcontextprotocol/server-brave-search to explicitly direct users to @brave/brave-search-mcp-server?
servers/README.md
Line 42 in 599dafc
The following would be terrific:
npm deprecate @modelcontextprotocol/server-brave-search "This package has moved to @brave/brave-search-mcp-server, the official Brave-maintained MCP server. Please update your configuration to use: npx -y @brave/brave-search-mcp-server"The old package still sees a meaningful amount of usage, so this would help existing users find the actively maintained server.
If there's interest, I'd also be happy to put together a small
0.6.3compatibility release that delegates to@brave/brave-search-mcp-server. That could keep existing configurations working while still nudging users toward the new package name.I'm happy to do the implementation and testing, and work with whatever publishing process you all prefer.