MCP.so
Sign In

Browserbase SSE Server MCP Server

@BryanVillaDev

Basic information

Category

Browser Automation

Transports

stdio

Author

BryanVillaDev

About Browserbase SSE Server MCP Server

No overview available yet

Browserbase SSE Server MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Browserbase SSE Server MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is 🧠 Browserbase SSE Server?

A Node.js SSE (Server-Sent Events) server that proxies the Browserbase API, streaming real-time responses from models like GPT-4. Designed for use in MCP (Master Control Program) projects and frontends needing live communication.

How to use 🧠 Browserbase SSE Server?

Clone the repository, install dependencies with npm install, then run the server. Pass parameters prompt, browserbase_api_key, and project_id via URL query strings.

Key features of 🧠 Browserbase SSE Server

  • Streams responses using EventSource (SSE).
  • Supports dynamic parameters via URL.
  • Acts as a proxy for Browserbase API.
  • Ideal for real‑time chat and frontend integration.

Use cases of 🧠 Browserbase SSE Server

  • Embedding real‑time AI chat in a web frontend.
  • Proxying Browserbase API calls for MCP projects.
  • Streaming model responses without blocking.
  • Building live assistants that need low‑latency output.

Frequently asked questions

1

What runtime environment does the server require?

Node.js version 18 or higher is required.

2

What credentials are needed to use it?

A Browserbase account, including an API key and a project ID.

3

How is authentication handled?

API keys and project IDs are passed as URL query parameters (`browserbase_api_key` and `project_id`).

4

What transport protocol does it use?

Server‑Sent Events (SSE) over HTTP, using the `EventSource` interface.

5

Can this server be used with MCP projects?

Yes, the README explicitly states it is suitable for MCP (Master Control Program) integrations.

Comments

More Browser Automation MCP servers