LangChain Agent with MCP Servers

Created By
esakrissaa year ago
LangChain Agent with MCP Servers: Using LangChain MCP Adapters for tool integration.
Overview

what is LangChain Agent with MCP Servers?

LangChain Agent with MCP Servers is a project that demonstrates how to build a LangChain agent using Model Context Protocol (MCP) adapters for integrating various tools and services.

how to use LangChain Agent with MCP Servers?

To use the agent, clone the repository, set up a virtual environment, install dependencies, and run the agent from the command line. It will prompt for user queries and process them using the integrated tools.

key features of LangChain Agent with MCP Servers?

  • Graceful shutdown mechanism for all MCP servers
  • Subprocess management for tracking and managing MCP server subprocesses
  • Robust error handling throughout the application
  • Modular design allowing easy extension with additional MCP servers

use cases of LangChain Agent with MCP Servers?

  1. Integrating web search capabilities with Tavily Search.
  2. Retrieving mock weather information.
  3. Evaluating mathematical expressions dynamically based on user queries.

FAQ from LangChain Agent with MCP Servers?

  • How do I install the project?

Clone the repository, create a virtual environment, and install the dependencies using pip.

  • Can I add new MCP servers?

Yes! You can create a new file in the src/mcpserver/ directory and implement the server with proper signal handling.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
esakrissa
Star
0
Language
Python
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