Repository navigation
Update deprecated Brave Search package to point to @brave/brave-search-mcp-server #4694
Description
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?
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.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.
Activity
olaservo commentedon Aug 28, 2026
Agreed, and the proposed message is fine as written. This is blocked on the same thing as #4702: the current maintainers do not yet have admin rights on the
@modelcontextprotocolnpm scope, so nobody here can runnpm deprecatetoday. Tracking it alongside #4702 and will run both once the grant goes through.On the
0.6.3shim: I would rather not publish new code under the old name. A clear deprecation message pointing atnpx -y @brave/brave-search-mcp-serveris enough, and it avoids a package that exists only to redirect.docs(brave-search): point to official @brave/brave-search-mcp-server …