langchain-mcp-tools 0.0.7__py3-none-any.whl → 0.0.9__py3-none-any.whl

langchain_mcp_tools/langchain_mcp_tools.py

@@ -43,16 +43,17 @@ The key aspects are:
    - 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 in the same task that created them
+   - Ensuring 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
-   initialized in its own dedicated task - there's no way around this if we
-   want true parallel initialization. However, this creates a challenge since
-   we also need to maintain long-lived sessions and handle cleanup properly.
+   initialized in its own dedicated task - there's no way around this as far
+   as I understand. However, this creates a challenge since we also need to
+   maintain long-lived sessions and handle cleanup properly.
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.
+
    By using `asyncio.Event`s for coordination, we can:
    - Allow parallel initialization while maintaining proper context management
    - Keep each initialization task running until explicit cleanup is requested
@@ -69,7 +70,9 @@ The key aspects are:
      called from the same task that created the context
 
 3. Task Lifecycle:
+
    To allow the initialization task to stay alive waiting for cleanup:
+   ```
    [Task starts]
      ↓
    Initialize server & convert tools
@@ -80,7 +83,7 @@ The key aspects are:
      ↓
    When cleanup_event is set:
    exit_stack.aclose() (cleanup in original task)
-
+   ```
 This approach indeed enables parallel initialization while maintaining proper
 async resource lifecycle management through context managers.
 However, I'm afraid I'm twisting things around too much.
@@ -89,8 +92,8 @@ 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 SDK, parallel server initializaion was quite
-straight forward)
+(FYI, with the TypeScript MCP SDK, parallel initialization was
+pretty straightforward.
 """
 
 

{langchain_mcp_tools-0.0.7.dist-info → langchain_mcp_tools-0.0.9.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
-Name: langchain_mcp_tools
-Version: 0.0.7
+Name: langchain-mcp-tools
+Version: 0.0.9
 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
@@ -19,7 +19,7 @@ Requires-Dist: pyjson5>=1.6.8
 Requires-Dist: pympler>=1.1
 Requires-Dist: python-dotenv>=1.0.1
 
-# MCP To LangChain Tools Conversion Utility [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/hideya/mcp-langchain-client-ts/blob/main/LICENSE) [![pypi version](https://img.shields.io/pypi/v/langchain-mcp-tools.svg)](https://pypi.org/project/langchain-mcp-tools/)
+# 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/)
 
 This package is intended to simplify the use of
 [Model Context Protocol (MCP)](https://modelcontextprotocol.io/)
@@ -27,7 +27,7 @@ server tools with LangChain / Python.
 
 It contains a utility function `convertMcpToLangchainTools()`.  
 This function handles parallel initialization of specified multiple MCP servers
-and converts their available tools into an array of
+and converts their available tools into a list of
 [LangChain-compatible tools](https://js.langchain.com/docs/how_to/tool_calling/).
 
 A typescript equivalent of this utility library is available
@@ -90,15 +90,13 @@ The returned tools can be used with LangChain, e.g.:
         tools
     )
 ```
-<!-- A simple and experimentable usage example can be found
-[here](https://github.com/hideya/langchain-mcp-tools-ts-usage/blob/main/src/index.ts) -->
+A simple and experimentable usage example can be found
+[here](https://github.com/hideya/langchain-mcp-tools-py-usage/blob/main/src/example.py)
 
-<!-- A more realistic usage example can be found
-[here](https://github.com/hideya/langchain-mcp-client-ts) -->
-
-An usage example can be found
+A more realistic usage example can be found
 [here](https://github.com/hideya/mcp-client-langchain-py)
 
+
 ## Limitations
 
 Currently, only text results of tool calls are supported.
@@ -110,7 +108,7 @@ to work successfully...
 
 I'm new to Python, so it is very possible that my ignorance is playing
 a big role here...  
-I'm summarizing why it was difficult for me below.  
+I'll summarize the difficulties I faced below.  
 Any comments pointing out something I am missing would be greatly appreciated!
 [(comment here)](https://github.com/hideya/langchain-mcp-tools-ts/issues)
 
@@ -124,10 +122,11 @@ Any comments pointing out something I am missing would be greatly appreciated!
    - Ensuring 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
-   initialized in its own dedicated task - there's no way around this if we
-   want true parallel initialization. However, this creates a challenge since
-   we also need to maintain long-lived sessions and handle cleanup properly.
+   initialized in its own dedicated task - there's no way around this as far
+   as I understand. However, this creates a challenge since we also need to
+   maintain long-lived sessions and handle cleanup properly.
 
    The key insight is to keep the initialization tasks alive throughout the
    session lifetime, rather than letting them complete after initialization.

langchain_mcp_tools-0.0.9.dist-info/RECORD

@@ -0,0 +1,8 @@
+langchain_mcp_tools/__init__.py,sha256=Xtv2VphhrWB_KlxTIofHZqtCIGtNEl0MxugnrNXTERA,94
+langchain_mcp_tools/langchain_mcp_tools.py,sha256=ysss7r51Adc5reyui2Zw2qB3RtUDRmc0IeEPTKvRHaM,10453
+langchain_mcp_tools/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+langchain_mcp_tools-0.0.9.dist-info/LICENSE,sha256=CRC91e8v116gCpnp7h49oIa6_zjhxqnHFTREeoZFJwA,1072
+langchain_mcp_tools-0.0.9.dist-info/METADATA,sha256=0K11Ip9o6CpwjewPP4iZyAjv5Y397yvQvNK5MFinm5A,6560
+langchain_mcp_tools-0.0.9.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
+langchain_mcp_tools-0.0.9.dist-info/top_level.txt,sha256=aR_9V2A1Yt-Bca60KmndmGLUWb2wiM5IOG-Gkaf1dxY,20
+langchain_mcp_tools-0.0.9.dist-info/RECORD,,

langchain_mcp_tools-0.0.7.dist-info/RECORD

@@ -1,7 +0,0 @@
-langchain_mcp_tools/__init__.py,sha256=Xtv2VphhrWB_KlxTIofHZqtCIGtNEl0MxugnrNXTERA,94
-langchain_mcp_tools/langchain_mcp_tools.py,sha256=0vIjVWyK5Ps7p3rxHVOEjbTywuLY3ON5G-hHJj-XkF0,10451
-langchain_mcp_tools-0.0.7.dist-info/LICENSE,sha256=CRC91e8v116gCpnp7h49oIa6_zjhxqnHFTREeoZFJwA,1072
-langchain_mcp_tools-0.0.7.dist-info/METADATA,sha256=7OiMRUSrJjEFlni0IODryRH0TknzoXazAtSy4XlTmzo,6687
-langchain_mcp_tools-0.0.7.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
-langchain_mcp_tools-0.0.7.dist-info/top_level.txt,sha256=aR_9V2A1Yt-Bca60KmndmGLUWb2wiM5IOG-Gkaf1dxY,20
-langchain_mcp_tools-0.0.7.dist-info/RECORD,,