litellm - 💡(How to fix) Fix MCP Registry: Browserbase server has wrong npm package name [1 participants]

Fix Plan

To resolve the issue, update the mcp_registry.json file with the correct npm package name for the Browserbase server.

Step-by-Step Solution:

1. Open the litellm/proxy/mcp_registry.json file.
2. Locate the line with the incorrect package name (around line 311).
3. Replace the incorrect line with the correct one:

-  "args": ["-y", "@anthropic/mcp-server-browserbase"],
+  "args": ["-y", "@browserbasehq/mcp"],

Example Code Snippet: The corrected JSON object should look like this:

"command": "npx",
"args": ["-y", "@browserbasehq/mcp"]

Verification

After updating the mcp_registry.json file, verify the fix by:

• Going to LiteLLM UI → MCP Servers → Add from registry → Browserbase
• Entering the API key and Project ID
• Saving and waiting 30 seconds to ensure tool discovery completes successfully without the 404 error.

Extra Tips

• Make sure to test the updated configuration in a controlled environment before deploying it to production.
• If issues persist, check the npm package version and ensure it is compatible with the LiteLLM container.