mcp-launcher

The mcp-launcher server is a Go-based MCP launcher that wires up and runs another MCP server implementation. It is designed to point at a reference MCP server repository and initialize a working instance configured with a specific game data or deployment channel (for example, the stagehand dataset). Once started, the launcher exposes the standard MCP tooling surface for interacting with the configured server, such as querying available endpoints, deploying small updates, or managing server state through the provided CLI/HTTP interfaces embedded in the launcher. Use it when you want a quick, repeatable way to boot a managed MCP server backed by the browserbase-mcp-server-browserbase integration and a predefined data set like stagehand.

To use it, run the launcher with the target server URL and the desired data/dialect flag. The example in the development notes shows the launcher being invoked with the repository URL and -d stagehand, which selects the stagehand dataset or profile. After startup, you can connect to the running MCP server using your client tooling to explore available commands, endpoints, and capabilities exposed by the managed server instance.

Prerequisites:

• Go 1.18+ installed on your system
• Git (optional, for cloning or fetching dependencies)

Installation steps:

1. Ensure Go is installed. Verify with: go version

2. Retrieve or clone the repository (if you are not running from a local copy): git clone https://github.com/your-org/mcp-launcher-repo.git cd mcp-launcher-repo

3. Build/run the launcher directly from source (no separate binary required): go run ./cmd/mcp-launcher https://github.com/browserbase/mcp-server-browserbase -d stagehand

4. (Optional) If you prefer a binary, you can build it: go build -o mcp-launcher ./cmd/mcp-launcher ./mcp-launcher https://github.com/browserbase/mcp-server-browserbase -d stagehand

Notes:

• The launcher automatically pulls in the referenced MCP server browserbase and initializes with the specified dataset or profile.
• Ensure network access is available for fetching dependencies and the target repository during startup.

Tips and common considerations:

• The -d stagehand flag selects a specific data/profile; replace with another valid profile as needed for your deployment.
• If the launcher fails to fetch the target repository, check your network proxy settings and Git authentication (if private).
• Ensure you have adequate permissions to bind to the required ports on your host and that any required environment variables for the underlying MCP server are configured if you extend the launcher.
• Since this is a Go-based launcher, you won’t find a package.json; there is no npm package for this server (npm_package will be null).
• If you plan to run in production, consider wrapping the launcher in systemd/init systems and binding to a static address/port for stability.