langchain-box-mcp-adapter

Created By
box-communitya year ago
This sample implements the Langchain MCP adapter to the Box MCP server.
Overview

What is langchain-box-mcp-adapter?

The langchain-box-mcp-adapter is a sample project that implements the Langchain MCP adapter to the Box MCP server, demonstrating how to integrate Langchain with a Box MCP server using various tools and agents.

How to use langchain-box-mcp-adapter?

To use the adapter, clone the repository, install the required dependencies, set up the environment variables in a .env file, and ensure the MCP server is accessible. You can then run the simple client or the graph-based agent to interact with the AI capabilities.

Key features of langchain-box-mcp-adapter?

  • Integration with Langchain's ChatOpenAI model for AI interactions.
  • Communication with the Box MCP server using stdio transport.
  • Dynamic loading of tools from the MCP server.
  • Creation of a React-style agent for handling user prompts.
  • User-friendly console interface with markdown rendering and typewriter effects.

Use cases of langchain-box-mcp-adapter?

  1. Building AI-driven applications that require integration with Box services.
  2. Creating interactive console applications for user engagement.
  3. Developing complex workflows using the graph-based agent.

FAQ from langchain-box-mcp-adapter?

  • What programming language is used in this project?

The project is implemented in Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I contribute to this project?

Contributions are welcome! You can open an issue or submit a pull request for improvements or bug fixes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
box-community
Star
0
Language
Python
License
MIT 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
Tavily Mcp
@tavily-ai

JavaScript
a year ago