About BrowserBee MCP Demo
A minimal demo combining a web app, browser extension, and MCP server, tested with the BrowserBee extension. It demonstrates message-based communication between the app and extension.
Key features
- 01Web app and browser extension demo
- 02MCP messages via `window.postMessage`
- 03`mcp:` message prefix
- 04Session and source fields
- 05`ping` server advertisement
Use cases
- 01Explore MCP messaging between a web app and browser extension
- 02Test MCP server discovery with BrowserBee
MCP support
The demo includes an MCP server that communicates with the BrowserBee extension through `window.postMessage`. It advertises the server with a `ping` message.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEBrowserBee MCP Demo
Minimalist demo of a web app and browser extension which includes an MCP server, tested with the BrowserBee extension.
MCP in the Browser
- All messages are prefixed with
mcp: - Additional fields
mcpSessionIdandsourceare added to all messages pingmessage is used to advertise the MCP server to the browser extension
Web App
MCPServerTransportuseswindow.postMessageto communicate with the BrowserBee extension.
Comments
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.