chore: Adding Browserbase MCP to the official registry

[Kylejeong2]

what

Model Context Protocol dropped an official registry, this PR is to get us on it.

[greptile-apps]

Greptile Summary

This PR registers the Browserbase MCP server with the newly launched official Model Context Protocol (MCP) registry. The changes add the necessary configuration and metadata files required for registry submission.

The core changes include:

1. Registry Configuration: A new server.json file defines the server's metadata, including its identity (io.github.browserbase/mcp-server-browserbase), GitHub repository information, npm package details, and transport configuration using stdio. The file specifies three required environment variables: BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, and GEMINI_API_KEY.

2. Package Metadata: The package.json file now includes an mcpName field matching the server identity, ensuring consistency between npm package metadata and MCP server configuration.

3. Security Hygiene: The .gitignore file adds entries for .mcpregistry_github_token and .mcpregistry_registry_token to prevent authentication credentials from being committed during the registry publishing process.

These changes integrate with the broader MCP ecosystem by making the Browserbase server discoverable through official channels, similar to how npm works for Node.js packages. The configuration follows the MCP registry schema and maintains consistency with existing package metadata.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it primarily adds configuration files for registry registration
• Score reflects well-structured configuration that follows MCP registry standards, though the dependency on GEMINI_API_KEY as a required environment variable introduces a slight concern about user setup complexity
• Pay attention to server.json to ensure the environment variable requirements align with your intended user experience

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}