MCP-CLIENT-BROSWER

What is MCP-CLIENT-BROSWER?

MCP-CLIENT-BROSWER is a TypeScript library that brings MCP (Model Control Protocol) support to the browser, enabling interaction with large language models (LLMs) through an MCP server. It leverages Cherry Studio's prompt templates and communication logic and is designed for use in modern web applications.

How to use MCP-CLIENT-BROSWER?

Install via npm i @autoexpect/mcp-sseclient-browser. Instantiate the MCPClient class with an array of server configurations and an options object (containing base URL, API key, and model), then call connect() and processQueryStream() with system and user prompts, a boolean flag, and callback functions for chunks and the full response.

Key features of MCP-CLIENT-BROSWER

• Runs entirely in the browser (no backend required)
• Communicates with MCP-compatible servers
• Built-in support for Cherry Studio's MCP prompt format
• Simple, extendable, and TypeScript-friendly API
• Designed for easy integration into modern web apps

Use cases of MCP-CLIENT-BROSWER

• AI chatbots powered by LLMs directly in the browser
• Embedding customizable prompt workflows into frontend apps
• Creating interactive educational or creative writing tools

FAQ from MCP-CLIENT-BROSWER

How does MCP-CLIENT-BROSWER run without a backend?

It operates entirely in the browser, communicating directly with MCP-compatible servers via SSE (Server-Sent Events) as shown in the configuration example.

Does MCP-CLIENT-BROSWER store any user data?

No. The library does not store user data; all interactions happen directly between the browser and the configured MCP server.

What dependencies or runtime requirements does it have?

The MCP server must support CORS and the Cherry prompt specification. The library is TypeScript-based and works with OpenAI-compatible or custom MCP servers.

What transport and authentication does MCP-CLIENT-BROSWER use?

It uses SSE for transport and supports API key authentication via the apiKey option in the client configuration.