langchain-mcp-tools 0.0.12__tar.gz → 0.0.14__tar.gz

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: langchain-mcp-tools
-Version: 0.0.12
+Version: 0.0.14
 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
@@ -120,13 +120,14 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 1. Core Challenge:
    - Async resources management for `stdio_client` and `ClientSession` seems
-     to require relying exclusively on `asynccontextmanager` for cleanup with
-     no manual cleanup options
+     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))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - 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
 
 2. Solution Strategy:
 
@@ -155,7 +156,7 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/README.md

@@ -95,13 +95,14 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 1. Core Challenge:
    - Async resources management for `stdio_client` and `ClientSession` seems
-     to require relying exclusively on `asynccontextmanager` for cleanup with
-     no manual cleanup options
+     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))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - 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
 
 2. Solution Strategy:
 
@@ -130,7 +131,7 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/langchain_mcp_tools/langchain_mcp_tools.py

@@ -38,13 +38,14 @@ The key aspects are:
 
 1. Core Challenge:
    - Async resources management for `stdio_client` and `ClientSession` seems
-     to require relying exclusively on `asynccontextmanager` for cleanup with
-     no manual cleanup options
+     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))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - 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
 
 2. Solution Strategy:
    A key requirement for parallel initialization is that each server must be
@@ -72,7 +73,7 @@ The key aspects are:
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/langchain_mcp_tools.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: langchain-mcp-tools
-Version: 0.0.12
+Version: 0.0.14
 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
@@ -120,13 +120,14 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 1. Core Challenge:
    - Async resources management for `stdio_client` and `ClientSession` seems
-     to require relying exclusively on `asynccontextmanager` for cleanup with
-     no manual cleanup options
+     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))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - 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
 
 2. Solution Strategy:
 
@@ -155,7 +156,7 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/langchain_mcp_tools.egg-info/top_level.txt

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

{langchain_mcp_tools-0.0.12 → langchain_mcp_tools-0.0.14}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "langchain-mcp-tools"
-version = "0.0.12"
+version = "0.0.14"
 description = "Model Context Protocol (MCP) To LangChain Tools Conversion Utility"
 readme = "README.md"
 requires-python = ">=3.11"