MCP CLIENT BROSWER

@autoexpect

Basic information

About MCP CLIENT BROSWER

TypeScript SDK for using large language models with an MCP server directly in the browser, powered by Cherry Studio's prompt templates.

MCP CLIENT BROSWER 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

MCP CLIENT BROSWER 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 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

Frequently asked questions

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.

Comments

More Browser Automation MCP servers

Apify Model Context Protocol (MCP) Server

apify

The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.

1.7K

Fastcrw

Fast, lightweight Firecrawl/Tavily alternative in Rust. Web scraper, crawler & search API with MCP server for AI agents. Drop-in Firecrawl-compatible API (/scrape, /crawl, /search). 2.3x faster than Tavily, 1.5x faster than Firecrawl in 1K-URL benchmarks. 6 MB RAM, single binary.

286