LibreChat - MCP Server Client

Created By
alan-meigsa year ago
Overview

What is LibreChat - MCP Server Client?

LibreChat - MCP Server Client is a modified version of the LibreChat application designed to serve as a comprehensive client for the Model Context Protocol (MCP) Server experiment, providing advanced capabilities for interacting with MCP-powered agents.

How to use LibreChat - MCP Server Client?

To use the MCP Server Client, follow the setup instructions provided in the MCP Server Documentation and LibreChat Documentation to configure the client for your needs.

Key features of LibreChat - MCP Server Client?

  • Advanced agent capabilities for tool-calling architecture
  • Extensible architecture for seamless integration of MCP features
  • Support for multimodal conversations, file handling, and code execution
  • Secure sandboxed environment for running MCP tools
  • User-friendly modern UI for interacting with agents

Use cases of LibreChat - MCP Server Client?

  1. Integrating and managing various MCP tools and agents.
  2. Running code securely within a sandboxed environment.
  3. Handling file uploads and downloads efficiently.
  4. Facilitating multimodal conversations with users.

FAQ from LibreChat - MCP Server Client?

  • What is the purpose of the MCP Server Client?

The MCP Server Client is designed to provide a robust interface for interacting with Model Context Protocol tools and agents, enhancing the user experience.

  • Is there documentation available for setup?

Yes! Detailed setup instructions can be found in the MCP Server Documentation and LibreChat Documentation.

  • What programming language is used in this project?

The project is primarily developed in JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
alan-meigs
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago