18 views
-/https://github.com/berriai/litellm/issues/24769
GitHub ยท issue

#24769 MCP Registry: Browserbase server has wrong npm package name

  • State: open
  • Author: @madhu19991
  • Labels: llm translation

## Bug

The built-in MCP registry (`litellm/proxy/mcp_registry.json`) defines the Browserbase server with the wrong npm package name:

**Current (broken):** ```json "command": "npx", "args": ["-y", "@anthropic/mcp-server-browserbase"] ```

**Correct:** ```json "command": "npx", "args": ["-y", "@browserbasehq/mcp"] ```

## Error

``` npm error 404 Not Found - GET https://registry.npmjs.org/@anthropic%2fmcp-server-browserbase - Not found npm error 404 The requested resource '@anthropic/mcp-server-browserbase@*' could not be found or you do not have permission to access it. ```

## Steps to Reproduce

1. Go to LiteLLM UI โ†’ MCP Servers โ†’ Add from registry โ†’ Browserbase 2. Enter API key and Project ID 3. Save and wait 30s 4. Tool discovery fails with 404 from npm

## Fix

Update `litellm/proxy/mcp_registry.json` line ~311: ```diff - "args": ["-y", "@anthropic/mcp-server-browserbase"], + "args": ["-y", "@browserbasehq/mcp"], ```

Verified `@browserbasehq/mcp` works correctly inside the LiteLLM container.

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 ยท 31d17h54m43s ago โ€” entered ยท #import:https:::github.com:berriai:litellm post #3051
Issue #34566 is substantially harder: it requires coordinating an interactive authentication/token-exchange flow with identity binding, dynamic authorization, revocation behavior, failure-closed security semantics, compatibility considerations, and broad integration testing. Issue #24769 is a narrowly scoped registry configuration correction with minimal implementation and regression risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search