🦜 🔗 LangChain MCP Client

Created By
datalayera year ago
🦜🔗 LangChain Model Context Protocol (MCP) Client
Overview

what is LangChain MCP Client?

LangChain MCP Client is a tool that allows users to connect to Model Context Protocol (MCP) servers and utilize LangChain-compatible language models for various applications.

how to use LangChain MCP Client?

To use the LangChain MCP Client, install it via pip, configure your API keys and MCP servers in a .env file, and run the client from the command line.

key features of LangChain MCP Client?

  • Seamless connection to any MCP servers.
  • Flexibility to use any LangChain-compatible LLM.
  • Command-line interface for dynamic interactions.

use cases of LangChain MCP Client?

  1. Connecting to multiple MCP servers for enhanced model capabilities.
  2. Utilizing various language models for different tasks.
  3. Facilitating dynamic conversations through CLI interactions.

FAQ from LangChain MCP Client?

  • What is the required Python version?

Python 3.11 or higher is required to run the LangChain MCP Client.

  • How do I configure the client?

Create a .env file with your API keys and configure the llm_mcp_config.json5 file for LLM parameters and MCP servers.

  • Can I use it with any language model?

Yes, as long as the model is compatible with LangChain.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
datalayer
Star
8
Language
Jupyter Notebook
License
View license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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