mcpField
🧠
🧠 Browserbase SSE Server

🧠 Browserbase SSE Server

Local
github.com/BryanVillaDevBrowser Automation0Updated 81w ago

About 🧠 Browserbase SSE Server

A Node.js SSE server that proxies the Browserbase API and streams responses in real time. It is described for use in frontends or embedded chats that need live communication.

Key features

  1. 01Stream responses over SSE
  2. 02Pass parameters through the URL
  3. 03Use Browserbase API credentials and project ID

Use cases

  1. 01Add real-time responses to a frontend
  2. 02Embed a live-response chat
  3. 03Provide prompts and Browserbase settings through URL parameters

MCP support

The README says the server can be used in MCP projects, but does not specify MCP tools or resources it exposes.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

🧠 Browserbase SSE Server

Servidor SSE (Server-Sent Events) en Node.js que actúa como proxy para la API de Browserbase. Envía respuestas en tiempo real desde modelos como GPT-4 usando Browserbase y puede ser usado en proyectos MCP (Master Control Program).


🚀 Características

  • Streaming de respuestas usando EventSource (SSE).
  • Soporte para parámetros dinámicos vía URL (prompt, browserbase_api_key, project_id).
  • Ideal para frontends o chats embebidos que requieren comunicación en tiempo real.

🛠️ Requisitos


📦 Instalación local

git clone https://github.com/tuusuario/browserbase-sse-server.git
cd browserbase-sse-server
npm install
npm start

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.