BrowserBee MCP Demo

What is BrowserBee MCP Demo?

BrowserBee MCP Demo is a minimalist demo of a web app and browser extension that includes an MCP server, designed to work with the BrowserBee extension. It demonstrates how MCP can be integrated into a browser environment.

How to use BrowserBee MCP Demo?

Messages are prefixed with "mcp:" and include additional fields "mcpSessionId" and "source". The MCP server uses a "ping" message to advertise itself to the BrowserBee extension. The transport layer uses window.postMessage for communication.

Key features of BrowserBee MCP Demo

• Minimalist demo of web app and browser extension.
• Includes an MCP server.
• Communicates via window.postMessage.
• All messages prefixed with "mcp:".
• Adds "mcpSessionId" and "source" fields to messages.
• Uses "ping" message to advertise MCP server to extension.

Use cases of BrowserBee MCP Demo

• Demonstrating MCP server integration in a browser environment.
• Testing MCP communication between a web app and a browser extension.

FAQ from BrowserBee MCP Demo

What message prefix does the MCP server use?

All messages are prefixed with "mcp:".

What additional fields are added to MCP messages?

The fields "mcpSessionId" and "source" are added to all messages.

How does the MCP server advertise itself to the BrowserBee extension?

It sends a "ping" message.

What transport mechanism does the MCP server use for communication?

It uses window.postMessage to communicate with the browser extension.