langchain-mcp-tools 0.0.16__tar.gz → 0.1.0__tar.gz

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: langchain-mcp-tools
-Version: 0.0.16
+Version: 0.1.0
 Summary: Model Context Protocol (MCP) To LangChain Tools Conversion Utility
 Project-URL: Bug Tracker, https://github.com/hideya/langchain-mcp-tools-py/issues
 Project-URL: Source Code, https://github.com/hideya/langchain-mcp-tools-py
@@ -8,7 +8,6 @@ Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: jsonschema-pydantic>=0.6
-Requires-Dist: langchain-core>=0.3.29
 Requires-Dist: langchain>=0.3.14
 Requires-Dist: langchain-anthropic>=0.3.1
 Requires-Dist: langchain-groq>=0.2.3
@@ -19,7 +18,8 @@ Requires-Dist: pyjson5>=1.6.8
 Requires-Dist: pympler>=1.1
 Requires-Dist: python-dotenv>=1.0.1
 Provides-Extra: dev
-Requires-Dist: twine>=6.0.1; extra == "dev"
+Requires-Dist: pytest>=8.3.4; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.25.2; extra == "dev"
 
 # MCP To LangChain Tools Conversion Utility [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/hideya/langchain-mcp-tools-py/blob/main/LICENSE) [![pypi version](https://img.shields.io/pypi/v/langchain-mcp-tools.svg)](https://pypi.org/project/langchain-mcp-tools/)
 
@@ -29,8 +29,7 @@ server tools with LangChain / Python.
 
 It contains a utility function `convert_mcp_to_langchain_tools()`.  
 This function handles parallel initialization of specified multiple MCP servers
-and converts their available tools into a list of
-[LangChain-compatible tools](https://js.langchain.com/docs/how_to/tool_calling/).
+and converts their available tools into a list of LangChain-compatible tools.
 
 A typescript equivalent of this utility library is available
 [here](https://www.npmjs.com/package/@h1deya/langchain-mcp-tools)
@@ -54,43 +53,44 @@ but only the contents of the `mcpServers` property,
 and is expressed as a `dict`, e.g.:
 
 ```python
-    mcp_configs = {
-        'filesystem': {
-            'command': 'npx',
-            'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
-        },
-        'fetch': {
-            'command': 'uvx',
-            'args': ['mcp-server-fetch']
-        }
+mcp_configs = {
+    'filesystem': {
+        'command': 'npx',
+        'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
+    },
+    'fetch': {
+        'command': 'uvx',
+        'args': ['mcp-server-fetch']
     }
+}
 
-    tools, cleanup = await convert_mcp_to_langchain_tools(
-        mcp_configs
-    )
+tools, cleanup = await convert_mcp_to_langchain_tools(
+    mcp_configs
+)
 ```
 
-The utility function initializes all specified MCP servers in parallel,
-and returns LangChain Tools (`List[BaseTool]`)
-by gathering all available MCP server tools,
-and by wrapping them into [LangChain Tools](https://js.langchain.com/docs/how_to/tool_calling/).
-It also returns a cleanup callback function (`McpServerCleanupFn`)
+This utility function initializes all specified MCP servers in parallel,
+and returns LangChain Tools
+([`tools: List[BaseTool]`](https://python.langchain.com/api_reference/core/tools/langchain_core.tools.base.BaseTool.html#langchain_core.tools.base.BaseTool))
+by gathering available MCP tools from the servers,
+and by wrapping them into LangChain tools.
+It also returns an async callback function (`cleanup: McpServerCleanupFn`)
 to be invoked to close all MCP server sessions when finished.
 
 The returned tools can be used with LangChain, e.g.:
 
 ```python
-    # from langchain.chat_models import init_chat_model
-    llm = init_chat_model(
-        model='claude-3-5-haiku-latest',
-        model_provider='anthropic'
-    )
-
-    # from langgraph.prebuilt import create_react_agent
-    agent = create_react_agent(
-        llm,
-        tools
-    )
+# from langchain.chat_models import init_chat_model
+llm = init_chat_model(
+    model='claude-3-5-haiku-latest',
+    model_provider='anthropic'
+)
+
+# from langgraph.prebuilt import create_react_agent
+agent = create_react_agent(
+    llm,
+    tools
+)
 ```
 A simple and experimentable usage example can be found
 [here](https://github.com/hideya/langchain-mcp-tools-py-usage/blob/main/src/example.py)
@@ -112,11 +112,11 @@ I'm new to Python, so it is very possible that my ignorance is playing
 a big role here...  
 I'll summarize the difficulties I faced below.
 The source code is available
-[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/langchain_mcp_tools/langchain_mcp_tools.py).  
+[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/src/langchain_mcp_tools/langchain_mcp_tools.py).  
 Any comments pointing out something I am missing would be greatly appreciated!
 [(comment here)](https://github.com/hideya/langchain-mcp-tools-ts/issues)
 
-1. Core Challenge:
+1. Challenge:
 
    A key requirement for parallel initialization is that each server must be
    initialized in its own dedicated task - there's no way around this as far as
@@ -129,11 +129,10 @@ Any comments pointing out something I am missing would be greatly appreciated!
      (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Need to keep sessions alive for later use by different tasks
-     after initialization
-   - Need to ensure proper cleanup later in the same task that created them
+   - Server cleanup can be initiated later by a task other than the one
+     that initialized the resources
 
-2. Solution Strategy:
+2. Solution:
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.
@@ -155,7 +154,8 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   The following illustrates how to implement the above-mentioned strategy:
+   The following task lifecyle diagram illustrates how the above strategy
+   was impelemented:
    ```
    [Task starts]
      ↓
@@ -176,5 +176,5 @@ It usually means I'm doing something very worng...
 I think it is a natural assumption that MCP SDK is designed with consideration
 for parallel server initialization.
 I'm not sure what I'm missing...
-(FYI, with the TypeScript MCP SDK, parallel initialization was 
+(FYI, with the TypeScript MCP SDK, parallel initialization was
 [pretty straightforward](https://github.com/hideya/langchain-mcp-tools-ts/blob/main/src/langchain-mcp-tools.ts))

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0}/README.md

@@ -6,8 +6,7 @@ server tools with LangChain / Python.
 
 It contains a utility function `convert_mcp_to_langchain_tools()`.  
 This function handles parallel initialization of specified multiple MCP servers
-and converts their available tools into a list of
-[LangChain-compatible tools](https://js.langchain.com/docs/how_to/tool_calling/).
+and converts their available tools into a list of LangChain-compatible tools.
 
 A typescript equivalent of this utility library is available
 [here](https://www.npmjs.com/package/@h1deya/langchain-mcp-tools)
@@ -31,43 +30,44 @@ but only the contents of the `mcpServers` property,
 and is expressed as a `dict`, e.g.:
 
 ```python
-    mcp_configs = {
-        'filesystem': {
-            'command': 'npx',
-            'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
-        },
-        'fetch': {
-            'command': 'uvx',
-            'args': ['mcp-server-fetch']
-        }
+mcp_configs = {
+    'filesystem': {
+        'command': 'npx',
+        'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
+    },
+    'fetch': {
+        'command': 'uvx',
+        'args': ['mcp-server-fetch']
     }
+}
 
-    tools, cleanup = await convert_mcp_to_langchain_tools(
-        mcp_configs
-    )
+tools, cleanup = await convert_mcp_to_langchain_tools(
+    mcp_configs
+)
 ```
 
-The utility function initializes all specified MCP servers in parallel,
-and returns LangChain Tools (`List[BaseTool]`)
-by gathering all available MCP server tools,
-and by wrapping them into [LangChain Tools](https://js.langchain.com/docs/how_to/tool_calling/).
-It also returns a cleanup callback function (`McpServerCleanupFn`)
+This utility function initializes all specified MCP servers in parallel,
+and returns LangChain Tools
+([`tools: List[BaseTool]`](https://python.langchain.com/api_reference/core/tools/langchain_core.tools.base.BaseTool.html#langchain_core.tools.base.BaseTool))
+by gathering available MCP tools from the servers,
+and by wrapping them into LangChain tools.
+It also returns an async callback function (`cleanup: McpServerCleanupFn`)
 to be invoked to close all MCP server sessions when finished.
 
 The returned tools can be used with LangChain, e.g.:
 
 ```python
-    # from langchain.chat_models import init_chat_model
-    llm = init_chat_model(
-        model='claude-3-5-haiku-latest',
-        model_provider='anthropic'
-    )
-
-    # from langgraph.prebuilt import create_react_agent
-    agent = create_react_agent(
-        llm,
-        tools
-    )
+# from langchain.chat_models import init_chat_model
+llm = init_chat_model(
+    model='claude-3-5-haiku-latest',
+    model_provider='anthropic'
+)
+
+# from langgraph.prebuilt import create_react_agent
+agent = create_react_agent(
+    llm,
+    tools
+)
 ```
 A simple and experimentable usage example can be found
 [here](https://github.com/hideya/langchain-mcp-tools-py-usage/blob/main/src/example.py)
@@ -89,11 +89,11 @@ I'm new to Python, so it is very possible that my ignorance is playing
 a big role here...  
 I'll summarize the difficulties I faced below.
 The source code is available
-[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/langchain_mcp_tools/langchain_mcp_tools.py).  
+[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/src/langchain_mcp_tools/langchain_mcp_tools.py).  
 Any comments pointing out something I am missing would be greatly appreciated!
 [(comment here)](https://github.com/hideya/langchain-mcp-tools-ts/issues)
 
-1. Core Challenge:
+1. Challenge:
 
    A key requirement for parallel initialization is that each server must be
    initialized in its own dedicated task - there's no way around this as far as
@@ -106,11 +106,10 @@ Any comments pointing out something I am missing would be greatly appreciated!
      (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Need to keep sessions alive for later use by different tasks
-     after initialization
-   - Need to ensure proper cleanup later in the same task that created them
+   - Server cleanup can be initiated later by a task other than the one
+     that initialized the resources
 
-2. Solution Strategy:
+2. Solution:
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.
@@ -132,7 +131,8 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   The following illustrates how to implement the above-mentioned strategy:
+   The following task lifecyle diagram illustrates how the above strategy
+   was impelemented:
    ```
    [Task starts]
      ↓
@@ -153,5 +153,5 @@ It usually means I'm doing something very worng...
 I think it is a natural assumption that MCP SDK is designed with consideration
 for parallel server initialization.
 I'm not sure what I'm missing...
-(FYI, with the TypeScript MCP SDK, parallel initialization was 
+(FYI, with the TypeScript MCP SDK, parallel initialization was
 [pretty straightforward](https://github.com/hideya/langchain-mcp-tools-ts/blob/main/src/langchain-mcp-tools.ts))

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0}/pyproject.toml

@@ -1,12 +1,11 @@
 [project]
 name = "langchain-mcp-tools"
-version = "0.0.16"
+version = "0.1.0"
 description = "Model Context Protocol (MCP) To LangChain Tools Conversion Utility"
 readme = "README.md"
 requires-python = ">=3.11"
 dependencies = [
     "jsonschema-pydantic>=0.6",
-    "langchain-core>=0.3.29",
     "langchain>=0.3.14",
     "langchain-anthropic>=0.3.1",
     "langchain-groq>=0.2.3",
@@ -20,15 +19,15 @@ dependencies = [
 
 [project.optional-dependencies]
 dev = [
-    "twine>=6.0.1",
+    "pytest>=8.3.4",
+    "pytest-asyncio>=0.25.2",
 ]
 
+[tool.setuptools]
+package-dir = {"" = "src"}
+
 [tool.setuptools.packages.find]
-exclude = [
-    "tests*",
-    "docs*",
-    "examples*",
-]
+where = ["src"]
 
 [tool.setuptools.package-data]
 langchain_mcp_tools = ["py.typed"]

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0/src}/langchain_mcp_tools/langchain_mcp_tools.py

@@ -36,7 +36,7 @@ This code implements a specific pattern for managing async resources that
 require context managers while enabling parallel initialization.
 The key aspects are:
 
-1. Core Challenge:
+1. Challenge:
 
    A key requirement for parallel initialization is that each server must be
    initialized in its own dedicated task - there's no way around this as far as
@@ -46,14 +46,13 @@ The key aspects are:
    - Resources management for `stdio_client` and `ClientSession` seems
      to require relying exclusively on `asynccontextmanager` for cleanup,
      with no manual cleanup options
-     (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
+     (based on the mcp python-sdk impl as of Jan 14, 2025)
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Need to keep sessions alive for later use by different tasks
-     after initialization
-   - Need to ensure proper cleanup later in the same task that created them
+   - Server cleanup can be initiated later by a task other than the one that
+     initialized the resources
 
-2. Solution Strategy:
+2. Solution:
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.
@@ -75,7 +74,8 @@ The key aspects are:
 
 3. Task Lifecycle:
 
-   The following illustrates how to implement the above-mentioned strategy:
+   The following task lifecyle diagram illustrates how the above strategy
+   was impelemented:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0/src}/langchain_mcp_tools.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: langchain-mcp-tools
-Version: 0.0.16
+Version: 0.1.0
 Summary: Model Context Protocol (MCP) To LangChain Tools Conversion Utility
 Project-URL: Bug Tracker, https://github.com/hideya/langchain-mcp-tools-py/issues
 Project-URL: Source Code, https://github.com/hideya/langchain-mcp-tools-py
@@ -8,7 +8,6 @@ Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: jsonschema-pydantic>=0.6
-Requires-Dist: langchain-core>=0.3.29
 Requires-Dist: langchain>=0.3.14
 Requires-Dist: langchain-anthropic>=0.3.1
 Requires-Dist: langchain-groq>=0.2.3
@@ -19,7 +18,8 @@ Requires-Dist: pyjson5>=1.6.8
 Requires-Dist: pympler>=1.1
 Requires-Dist: python-dotenv>=1.0.1
 Provides-Extra: dev
-Requires-Dist: twine>=6.0.1; extra == "dev"
+Requires-Dist: pytest>=8.3.4; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.25.2; extra == "dev"
 
 # MCP To LangChain Tools Conversion Utility [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/hideya/langchain-mcp-tools-py/blob/main/LICENSE) [![pypi version](https://img.shields.io/pypi/v/langchain-mcp-tools.svg)](https://pypi.org/project/langchain-mcp-tools/)
 
@@ -29,8 +29,7 @@ server tools with LangChain / Python.
 
 It contains a utility function `convert_mcp_to_langchain_tools()`.  
 This function handles parallel initialization of specified multiple MCP servers
-and converts their available tools into a list of
-[LangChain-compatible tools](https://js.langchain.com/docs/how_to/tool_calling/).
+and converts their available tools into a list of LangChain-compatible tools.
 
 A typescript equivalent of this utility library is available
 [here](https://www.npmjs.com/package/@h1deya/langchain-mcp-tools)
@@ -54,43 +53,44 @@ but only the contents of the `mcpServers` property,
 and is expressed as a `dict`, e.g.:
 
 ```python
-    mcp_configs = {
-        'filesystem': {
-            'command': 'npx',
-            'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
-        },
-        'fetch': {
-            'command': 'uvx',
-            'args': ['mcp-server-fetch']
-        }
+mcp_configs = {
+    'filesystem': {
+        'command': 'npx',
+        'args': ['-y', '@modelcontextprotocol/server-filesystem', '.']
+    },
+    'fetch': {
+        'command': 'uvx',
+        'args': ['mcp-server-fetch']
     }
+}
 
-    tools, cleanup = await convert_mcp_to_langchain_tools(
-        mcp_configs
-    )
+tools, cleanup = await convert_mcp_to_langchain_tools(
+    mcp_configs
+)
 ```
 
-The utility function initializes all specified MCP servers in parallel,
-and returns LangChain Tools (`List[BaseTool]`)
-by gathering all available MCP server tools,
-and by wrapping them into [LangChain Tools](https://js.langchain.com/docs/how_to/tool_calling/).
-It also returns a cleanup callback function (`McpServerCleanupFn`)
+This utility function initializes all specified MCP servers in parallel,
+and returns LangChain Tools
+([`tools: List[BaseTool]`](https://python.langchain.com/api_reference/core/tools/langchain_core.tools.base.BaseTool.html#langchain_core.tools.base.BaseTool))
+by gathering available MCP tools from the servers,
+and by wrapping them into LangChain tools.
+It also returns an async callback function (`cleanup: McpServerCleanupFn`)
 to be invoked to close all MCP server sessions when finished.
 
 The returned tools can be used with LangChain, e.g.:
 
 ```python
-    # from langchain.chat_models import init_chat_model
-    llm = init_chat_model(
-        model='claude-3-5-haiku-latest',
-        model_provider='anthropic'
-    )
-
-    # from langgraph.prebuilt import create_react_agent
-    agent = create_react_agent(
-        llm,
-        tools
-    )
+# from langchain.chat_models import init_chat_model
+llm = init_chat_model(
+    model='claude-3-5-haiku-latest',
+    model_provider='anthropic'
+)
+
+# from langgraph.prebuilt import create_react_agent
+agent = create_react_agent(
+    llm,
+    tools
+)
 ```
 A simple and experimentable usage example can be found
 [here](https://github.com/hideya/langchain-mcp-tools-py-usage/blob/main/src/example.py)
@@ -112,11 +112,11 @@ I'm new to Python, so it is very possible that my ignorance is playing
 a big role here...  
 I'll summarize the difficulties I faced below.
 The source code is available
-[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/langchain_mcp_tools/langchain_mcp_tools.py).  
+[here](https://github.com/hideya/langchain-mcp-tools-py/blob/main/src/langchain_mcp_tools/langchain_mcp_tools.py).  
 Any comments pointing out something I am missing would be greatly appreciated!
 [(comment here)](https://github.com/hideya/langchain-mcp-tools-ts/issues)
 
-1. Core Challenge:
+1. Challenge:
 
    A key requirement for parallel initialization is that each server must be
    initialized in its own dedicated task - there's no way around this as far as
@@ -129,11 +129,10 @@ Any comments pointing out something I am missing would be greatly appreciated!
      (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Need to keep sessions alive for later use by different tasks
-     after initialization
-   - Need to ensure proper cleanup later in the same task that created them
+   - Server cleanup can be initiated later by a task other than the one
+     that initialized the resources
 
-2. Solution Strategy:
+2. Solution:
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.
@@ -155,7 +154,8 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   The following illustrates how to implement the above-mentioned strategy:
+   The following task lifecyle diagram illustrates how the above strategy
+   was impelemented:
    ```
    [Task starts]
      ↓
@@ -176,5 +176,5 @@ It usually means I'm doing something very worng...
 I think it is a natural assumption that MCP SDK is designed with consideration
 for parallel server initialization.
 I'm not sure what I'm missing...
-(FYI, with the TypeScript MCP SDK, parallel initialization was 
+(FYI, with the TypeScript MCP SDK, parallel initialization was
 [pretty straightforward](https://github.com/hideya/langchain-mcp-tools-ts/blob/main/src/langchain-mcp-tools.ts))

langchain_mcp_tools-0.1.0/src/langchain_mcp_tools.egg-info/SOURCES.txt

@@ -0,0 +1,12 @@
+LICENSE
+README.md
+pyproject.toml
+src/langchain_mcp_tools/__init__.py
+src/langchain_mcp_tools/langchain_mcp_tools.py
+src/langchain_mcp_tools/py.typed
+src/langchain_mcp_tools.egg-info/PKG-INFO
+src/langchain_mcp_tools.egg-info/SOURCES.txt
+src/langchain_mcp_tools.egg-info/dependency_links.txt
+src/langchain_mcp_tools.egg-info/requires.txt
+src/langchain_mcp_tools.egg-info/top_level.txt
+tests/test_langchain_mcp_tools.py

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0/src}/langchain_mcp_tools.egg-info/requires.txt

@@ -1,5 +1,4 @@
 jsonschema-pydantic>=0.6
-langchain-core>=0.3.29
 langchain>=0.3.14
 langchain-anthropic>=0.3.1
 langchain-groq>=0.2.3
@@ -11,4 +10,5 @@ pympler>=1.1
 python-dotenv>=1.0.1
 
 [dev]
-twine>=6.0.1
+pytest>=8.3.4
+pytest-asyncio>=0.25.2

{langchain_mcp_tools-0.0.16 → langchain_mcp_tools-0.1.0/src}/langchain_mcp_tools.egg-info/top_level.txt

@@ -1,3 +1 @@
-build
-dist
 langchain_mcp_tools

langchain_mcp_tools-0.1.0/tests/test_langchain_mcp_tools.py

@@ -0,0 +1,164 @@
+import pytest
+from unittest.mock import AsyncMock, MagicMock, patch
+from langchain_core.tools import BaseTool
+from langchain_mcp_tools.langchain_mcp_tools import (
+    convert_mcp_to_langchain_tools,
+)
+
+# Fix the asyncio mark warning by installing pytest-asyncio
+pytest_plugins = ('pytest_asyncio',)
+
+
+@pytest.fixture
+def mock_stdio_client():
+    with patch('langchain_mcp_tools.langchain_mcp_tools.stdio_client') as mock:
+        mock.return_value.__aenter__.return_value = (AsyncMock(), AsyncMock())
+        yield mock
+
+
+@pytest.fixture
+def mock_client_session():
+    with patch('langchain_mcp_tools.langchain_mcp_tools.ClientSession') \
+            as mock:
+        session = AsyncMock()
+        # Mock the list_tools response
+        session.list_tools.return_value = MagicMock(
+            tools=[
+                MagicMock(
+                    name="tool1",
+                    description="Test tool",
+                    inputSchema={"type": "object", "properties": {}}
+                )
+            ]
+        )
+        mock.return_value.__aenter__.return_value = session
+        yield mock
+
+
+@pytest.mark.asyncio
+async def test_convert_mcp_to_langchain_tools_empty():
+    server_configs = {}
+    tools, cleanup = await convert_mcp_to_langchain_tools(server_configs)
+    assert isinstance(tools, list)
+    assert len(tools) == 0
+    await cleanup()
+
+
+"""
+@pytest.mark.asyncio
+async def test_convert_mcp_to_langchain_tools_invalid_config():
+    server_configs = {"invalid": {"command": "nonexistent"}}
+    with pytest.raises(Exception):
+        await convert_mcp_to_langchain_tools(server_configs)
+"""
+
+
+"""
+@pytest.mark.asyncio
+async def test_convert_single_mcp_success(
+    mock_stdio_client,
+    mock_client_session
+):
+    # Test data
+    server_name = "test_server"
+    server_config = {
+        "command": "test_command",
+        "args": ["--test"],
+        "env": {"TEST_ENV": "value"}
+    }
+    langchain_tools = []
+    ready_event = asyncio.Event()
+    cleanup_event = asyncio.Event()
+
+    # Create task
+    task = asyncio.create_task(
+        convert_single_mcp_to_langchain_tools(
+            server_name,
+            server_config,
+            langchain_tools,
+            ready_event,
+            cleanup_event
+        )
+    )
+
+    # Wait for ready event
+    await asyncio.wait_for(ready_event.wait(), timeout=1.0)
+
+    # Verify tools were created
+    assert len(langchain_tools) == 1
+    assert isinstance(langchain_tools[0], BaseTool)
+    assert langchain_tools[0].name == "tool1"
+
+    # Trigger cleanup
+    cleanup_event.set()
+    await task
+"""
+
+
+@pytest.mark.asyncio
+async def test_convert_mcp_to_langchain_tools_multiple_servers(
+    mock_stdio_client,
+    mock_client_session
+):
+    server_configs = {
+        "server1": {"command": "cmd1", "args": []},
+        "server2": {"command": "cmd2", "args": []}
+    }
+
+    tools, cleanup = await convert_mcp_to_langchain_tools(server_configs)
+
+    # Verify correct number of tools created
+    assert len(tools) == 2  # One tool per server
+    assert all(isinstance(tool, BaseTool) for tool in tools)
+
+    # Test cleanup
+    await cleanup()
+
+
+"""
+@pytest.mark.asyncio
+async def test_tool_execution(mock_stdio_client, mock_client_session):
+    server_configs = {
+        "test_server": {"command": "test", "args": []}
+    }
+
+    # Mock the tool execution response
+    session = mock_client_session.return_value.__aenter__.return_value
+    session.call_tool.return_value = MagicMock(
+        isError=False,
+        content={"result": "success"}
+    )
+
+    tools, cleanup = await convert_mcp_to_langchain_tools(server_configs)
+
+    # Test tool execution
+    result = await tools[0]._arun(test_param="value")
+    assert result == {"result": "success"}
+
+    # Verify tool was called with correct parameters
+    session.call_tool.assert_called_once_with("tool1", {"test_param": "value"})
+
+    await cleanup()
+"""
+
+
+@pytest.mark.asyncio
+async def test_tool_execution_error(mock_stdio_client, mock_client_session):
+    server_configs = {
+        "test_server": {"command": "test", "args": []}
+    }
+
+    # Mock error response
+    session = mock_client_session.return_value.__aenter__.return_value
+    session.call_tool.return_value = MagicMock(
+        isError=True,
+        content="Error message"
+    )
+
+    tools, cleanup = await convert_mcp_to_langchain_tools(server_configs)
+
+    # Test tool execution error
+    with pytest.raises(Exception):
+        await tools[0]._arun(test_param="value")
+
+    await cleanup()

langchain_mcp_tools-0.0.16/langchain_mcp_tools.egg-info/SOURCES.txt

@@ -1,11 +0,0 @@
-LICENSE
-README.md
-pyproject.toml
-langchain_mcp_tools/__init__.py
-langchain_mcp_tools/langchain_mcp_tools.py
-langchain_mcp_tools/py.typed
-langchain_mcp_tools.egg-info/PKG-INFO
-langchain_mcp_tools.egg-info/SOURCES.txt
-langchain_mcp_tools.egg-info/dependency_links.txt
-langchain_mcp_tools.egg-info/requires.txt
-langchain_mcp_tools.egg-info/top_level.txt