universal-mcp 0.1.15rc5__tar.gz → 0.1.16__tar.gz

{universal_mcp-0.1.15rc5 → universal_mcp-0.1.16}/.gitignore

@@ -47,4 +47,5 @@ src/universal_mcp/applications/test_with_docs/
 src/universal_mcp/applications/test_without_docs/
 
 # Temporary files
-tmp/
+tmp/
+examples

universal_mcp-0.1.16/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Agentr
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

universal_mcp-0.1.16/PKG-INFO

@@ -0,0 +1,282 @@
+Metadata-Version: 2.4
+Name: universal-mcp
+Version: 0.1.16
+Summary: Universal MCP acts as a middle ware for your API applications. It can store your credentials, authorize, enable disable apps on the fly and much more.
+Author-email: Manoj Bajaj <manojbajaj95@gmail.com>
+License: MIT
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: cookiecutter>=2.6.0
+Requires-Dist: gql[all]>=3.5.2
+Requires-Dist: jinja2>=3.1.3
+Requires-Dist: jsonref>=1.1.0
+Requires-Dist: keyring>=25.6.0
+Requires-Dist: langchain-mcp-adapters>=0.0.3
+Requires-Dist: litellm>=1.30.7
+Requires-Dist: loguru>=0.7.3
+Requires-Dist: mcp>=1.7.1
+Requires-Dist: posthog>=3.24.0
+Requires-Dist: pydantic-settings>=2.8.1
+Requires-Dist: pydantic>=2.11.1
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: rich>=14.0.0
+Requires-Dist: typer>=0.15.2
+Provides-Extra: dev
+Requires-Dist: litellm>=1.30.7; extra == 'dev'
+Requires-Dist: pre-commit>=4.2.0; extra == 'dev'
+Requires-Dist: pyright>=1.1.398; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.26.0; extra == 'dev'
+Requires-Dist: pytest>=8.3.5; extra == 'dev'
+Requires-Dist: ruff>=0.11.4; extra == 'dev'
+Provides-Extra: playground
+Requires-Dist: langchain-openai>=0.3.12; extra == 'playground'
+Requires-Dist: langgraph-checkpoint-sqlite>=2.0.6; extra == 'playground'
+Requires-Dist: langgraph>=0.3.24; extra == 'playground'
+Requires-Dist: litellm>=1.30.7; extra == 'playground'
+Requires-Dist: python-dotenv>=1.0.1; extra == 'playground'
+Requires-Dist: streamlit>=1.44.1; extra == 'playground'
+Requires-Dist: watchdog>=6.0.0; extra == 'playground'
+Description-Content-Type: text/markdown
+
+# Universal MCP
+
+Universal MCP acts as a middleware layer for your API applications, enabling seamless integration with various services through the Model Control Protocol (MCP). It simplifies credential management, authorization, dynamic app enablement, and provides a robust framework for building and managing AI-powered tools.
+
+## 🌟 Features
+
+- **MCP (Model Control Protocol) Integration**: Seamlessly works with MCP server architecture for standardized agent-tool communication.
+- **Simplified API Integration**: Connect to services like GitHub, Google Calendar, Gmail, Reddit, Tavily, and more with minimal code. See [AgentR](https://agentr.dev) for a list of available applications.
+- **Managed Authentication**: Built-in support for API keys and OAuth-based authentication flows, often managed via the AgentR platform.
+- **Extensible Architecture**: Easily build and add new app integrations with minimal boilerplate using provided base classes and generation tools.
+- **Credential Management**: Flexible and secure storage options for API credentials (memory, environment variables, system keyring).
+- **Comprehensive Tool Management**: Robust tool registration, Pydantic-based validation, automatic docstring parsing, and execution capabilities. Supports conversion between MCP, LangChain, and OpenAI tool formats.
+- **Multiple Server Types**: Configurations for local development, AgentR-connected dynamic app loading, and single-application servers.
+- **Playground Environment**: Includes an interactive Streamlit-based playground for testing agents and tools.
+
+## 🔧 Installation
+
+Install Universal MCP using pip:
+
+```bash
+pip install universal-mcp
+```
+
+## 🚀 Quick Start
+
+**Important Prerequisite: AgentR API Key (If Using AgentR Integration)**
+
+If you plan to use integrations with `type: "agentr"` (for services like GitHub, Gmail, Notion via the AgentR platform), or if you run the MCP server itself with `type: "agentr"`, you first need an AgentR API key:
+
+1.  Visit [https://agentr.dev](https://agentr.dev) to create an account and generate an API key from your dashboard.
+2.  Set it as an environment variable _before_ running the MCP server:
+    ```bash
+    export AGENTR_API_KEY="your_api_key_here"
+    ```
+
+**1. Create a Configuration File (e.g., `config.json`)**
+
+This file defines the server settings, credential stores, and the applications to load with their respective integrations.
+
+```json
+{
+  "name": "My Local MCP Server",
+  "description": "A server for testing applications locally",
+  "type": "local", // "local" or "agentr"
+  "transport": "sse", // "sse", "stdio", or "http"
+  "port": 8005, // Relevant for "sse" or "http"
+  "store": {
+    // Default store for integrations
+    "name": "my_mcp_store",
+    "type": "keyring" // "keyring", "environment", or "memory"
+  },
+  "apps": [
+    {
+      "name": "zenquotes", // App slug (e.g., from agentr.dev)
+      "integration": null // No authentication needed for this app
+    },
+    {
+      "name": "tavily",
+      "integration": {
+        "name": "TAVILY_API_KEY", // Unique name for this credential if type is "api_key"
+        "type": "api_key",
+        "store": {
+          // Override default store for this specific app
+          "type": "environment" // Looks for TAVILY_API_KEY env var
+        }
+      }
+    },
+    {
+      "name": "github",
+      "integration": {
+        "name": "github", // Matches the service name in AgentR
+        "type": "agentr" // Uses AgentR platform for auth/creds
+      }
+    }
+  ]
+}
+```
+
+_Notes on `config.json`:_
+
+- `type: "local"`: Runs applications defined directly in the config's `apps` list.
+- `type: "agentr"`: Connects to the AgentR platform to dynamically load user-enabled apps (ignores the `apps` list in the config) and handle credentials. Requires `AGENTR_API_KEY` environment variable.
+- `store`: Defines credential storage.
+  - `environment`: Looks for an environment variable named `<INTEGRATION_NAME_UPPERCASE>` (e.g., `TAVILY_API_KEY` for the example above).
+  - `keyring`: Uses the system's secure credential storage.
+  - `memory`: Transient storage, lost when the server stops.
+- `integration`: Configures authentication for each app.
+  - `type: "agentr"`: Uses the AgentR platform for OAuth/credential management.
+  - `type: "api_key"`: Uses the specified `store` to retrieve the key.
+
+**2. Run the Server via CLI**
+
+Ensure any required environment variables (like `TAVILY_API_KEY` for the Tavily example, or `AGENTR_API_KEY` if using `"agentr"` type server/integrations) are set.
+
+```bash
+universal_mcp run -c config.json
+```
+
+The server will start, load the configured applications (or connect to AgentR if `type: "agentr"`), and listen for connections based on the `transport` type.
+
+## 🛠️ Using the Playground
+
+The `playground` directory provides a runnable Streamlit application for interacting with agents that can use tools from an MCP server.
+
+**Prerequisites:**
+
+- **`local_config.json`**: This file must exist in the **project root directory** (the same directory as this `README.md`). It configures the _local_ MCP server that the playground's agent can connect to if you choose to run one. For an example, see the `local_config.json` structure in the [Playground README](playground/README.md).
+- **Dependencies**: Install playground-specific dependencies. If you have the project cloned, you might install them via:
+  ```bash
+  pip install -e .[playground]
+  # or manually install fastapi, streamlit, uvicorn, langchain-openai, etc.
+  ```
+
+**Running the Playground:**
+
+The easiest way is to use the automated startup script from the **project root directory**:
+
+```bash
+python playground
+```
+
+This script will:
+
+1. Optionally start a local MCP server (based on your `local_config.json`) if you confirm.
+2. Launch the Streamlit application.
+
+For more detailed setup, manual startup instructions, and an explanation of the `local_config.json` for the playground, please refer to the [Playground README](playground/README.md).
+
+## 🧩 Available Applications
+
+Universal MCP can integrate with a wide variety of applications. For a list of publicly available applications and their slugs (e.g., "github", "google-calendar"), please visit [AgentR Applications](https://agentr.dev).
+Applications are typically installed dynamically by Universal MCP from their respective repositories when first referenced by slug.
+
+_Authentication Type Notes:_
+
+- _OAuth (via AgentR)_: Usually requires configuring the app's integration with `type: "agentr"` in your `ServerConfig`. This leverages the AgentR platform for the OAuth flow and requires the `AGENTR_API_KEY` to be set.
+- _API Key (via Integration)_: Requires configuring `type: "api_key"` for the app's integration in your `ServerConfig`, along with a `store` (like `environment` or `keyring`) to specify where the API key is located.
+
+## 🔐 Integration Types
+
+Universal MCP supports different ways to handle authentication for applications:
+
+### 1. API Key Integration (`type: "api_key"`)
+
+For services that authenticate via simple API keys.
+
+```json
+// In your ServerConfig apps array:
+{
+  "name": "tavily",
+  "integration": {
+    "name": "TAVILY_API_KEY", // Used by the store (e.g., as env var name)
+    "type": "api_key",
+    "store": {
+      "type": "environment" // Or "keyring", "memory"
+    }
+  }
+}
+```
+
+### 2. AgentR Integration (`type: "agentr"`)
+
+Recommended for services integrated with the AgentR platform, which typically handles OAuth flows or centrally managed credentials. Requires the `AGENTR_API_KEY` environment variable to be set for the MCP server process.
+
+```json
+// In your ServerConfig apps array:
+{
+  "name": "github",
+  "integration": {
+    "name": "github", // Matches the service name configured in AgentR
+    "type": "agentr"
+  }
+}
+```
+
+When an action requiring authorization is called, the `AgentRIntegration` will prompt the user (via the MCP client) to visit a URL to complete the OAuth flow managed by AgentR. This is also the default integration type for apps if the main server config is `type: "agentr"`.
+
+### 3. Direct OAuth Integration (`type: "oauth"`)
+
+While `AgentRIntegration` is generally preferred for OAuth, a direct `OAuthIntegration` class exists. However, it requires manual configuration of client IDs, secrets, and callback handling, which is more complex to set up outside the AgentR platform.
+
+## 🤖 CLI Usage
+
+Universal MCP includes a powerful command-line interface:
+
+```bash
+# Run the MCP server using a configuration file
+universal_mcp run -c config.json
+
+# Initialize a new MCP application project structure
+universal_mcp init --app-name my-cool-app --o ./my-apps --integration-type api_key
+
+# Generate API client code and application structure from an OpenAPI schema
+universal_mcp generate -s <path_to_schema.json_or_yaml> -o <path/to/app_output_directory> --c CustomAppClassName
+# Example: universal_mcp generate -s notion_api.yaml -o ./custom_apps/notion --c MyNotionApp
+
+# Preprocess an OpenAPI schema using an LLM to fill/enhance descriptions
+universal_mcp preprocess -s <path_to_input_schema.json_or_yaml> -o <path_to_processed_schema.json_or_yaml>
+
+# Generate Google-style docstrings for functions in a Python file using an LLM
+universal_mcp docgen <path/to/app_file.py>
+
+# Generate a README.md for a generated application file
+universal_mcp readme <path/to/app_file.py>
+
+# Install MCP configuration for supported desktop apps (e.g., Claude, Cursor)
+# Requires an AgentR API key for configuration.
+universal_mcp install claude
+universal_mcp install cursor
+
+# Check installed version (standard typer command)
+universal_mcp --version
+```
+
+## 📋 Requirements
+
+- Python 3.10+
+- Key Dependencies (installed automatically via pip, see `pyproject.toml` for full list):
+  - `mcp-server`
+  - `loguru`
+  - `typer`
+  - `httpx`
+  - `pydantic`
+  - `pyyaml`
+  - `keyring` (for `KeyringStore`)
+  - `litellm` (for `docgen` and `preprocess` commands)
+  - `uv` (used internally for dynamic package installation)
+
+## 📚 Documentation
+
+For more detailed information about specific components:
+
+- [Applications Framework](src/universal_mcp/applications/README.md)
+- [Tool Management](src/universal_mcp/tools/README.md)
+- [Server Implementations](src/universal_mcp/servers/README.md)
+- [Credential Stores](src/universal_mcp/stores/README.md)
+- [Integration & Authentication](src/universal_mcp/integrations/README.md)
+- [Playground Usage](playground/README.md)
+
+## 📝 License
+
+This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.

universal_mcp-0.1.16/README.md

@@ -0,0 +1,242 @@
+# Universal MCP
+
+Universal MCP acts as a middleware layer for your API applications, enabling seamless integration with various services through the Model Control Protocol (MCP). It simplifies credential management, authorization, dynamic app enablement, and provides a robust framework for building and managing AI-powered tools.
+
+## 🌟 Features
+
+- **MCP (Model Control Protocol) Integration**: Seamlessly works with MCP server architecture for standardized agent-tool communication.
+- **Simplified API Integration**: Connect to services like GitHub, Google Calendar, Gmail, Reddit, Tavily, and more with minimal code. See [AgentR](https://agentr.dev) for a list of available applications.
+- **Managed Authentication**: Built-in support for API keys and OAuth-based authentication flows, often managed via the AgentR platform.
+- **Extensible Architecture**: Easily build and add new app integrations with minimal boilerplate using provided base classes and generation tools.
+- **Credential Management**: Flexible and secure storage options for API credentials (memory, environment variables, system keyring).
+- **Comprehensive Tool Management**: Robust tool registration, Pydantic-based validation, automatic docstring parsing, and execution capabilities. Supports conversion between MCP, LangChain, and OpenAI tool formats.
+- **Multiple Server Types**: Configurations for local development, AgentR-connected dynamic app loading, and single-application servers.
+- **Playground Environment**: Includes an interactive Streamlit-based playground for testing agents and tools.
+
+## 🔧 Installation
+
+Install Universal MCP using pip:
+
+```bash
+pip install universal-mcp
+```
+
+## 🚀 Quick Start
+
+**Important Prerequisite: AgentR API Key (If Using AgentR Integration)**
+
+If you plan to use integrations with `type: "agentr"` (for services like GitHub, Gmail, Notion via the AgentR platform), or if you run the MCP server itself with `type: "agentr"`, you first need an AgentR API key:
+
+1.  Visit [https://agentr.dev](https://agentr.dev) to create an account and generate an API key from your dashboard.
+2.  Set it as an environment variable _before_ running the MCP server:
+    ```bash
+    export AGENTR_API_KEY="your_api_key_here"
+    ```
+
+**1. Create a Configuration File (e.g., `config.json`)**
+
+This file defines the server settings, credential stores, and the applications to load with their respective integrations.
+
+```json
+{
+  "name": "My Local MCP Server",
+  "description": "A server for testing applications locally",
+  "type": "local", // "local" or "agentr"
+  "transport": "sse", // "sse", "stdio", or "http"
+  "port": 8005, // Relevant for "sse" or "http"
+  "store": {
+    // Default store for integrations
+    "name": "my_mcp_store",
+    "type": "keyring" // "keyring", "environment", or "memory"
+  },
+  "apps": [
+    {
+      "name": "zenquotes", // App slug (e.g., from agentr.dev)
+      "integration": null // No authentication needed for this app
+    },
+    {
+      "name": "tavily",
+      "integration": {
+        "name": "TAVILY_API_KEY", // Unique name for this credential if type is "api_key"
+        "type": "api_key",
+        "store": {
+          // Override default store for this specific app
+          "type": "environment" // Looks for TAVILY_API_KEY env var
+        }
+      }
+    },
+    {
+      "name": "github",
+      "integration": {
+        "name": "github", // Matches the service name in AgentR
+        "type": "agentr" // Uses AgentR platform for auth/creds
+      }
+    }
+  ]
+}
+```
+
+_Notes on `config.json`:_
+
+- `type: "local"`: Runs applications defined directly in the config's `apps` list.
+- `type: "agentr"`: Connects to the AgentR platform to dynamically load user-enabled apps (ignores the `apps` list in the config) and handle credentials. Requires `AGENTR_API_KEY` environment variable.
+- `store`: Defines credential storage.
+  - `environment`: Looks for an environment variable named `<INTEGRATION_NAME_UPPERCASE>` (e.g., `TAVILY_API_KEY` for the example above).
+  - `keyring`: Uses the system's secure credential storage.
+  - `memory`: Transient storage, lost when the server stops.
+- `integration`: Configures authentication for each app.
+  - `type: "agentr"`: Uses the AgentR platform for OAuth/credential management.
+  - `type: "api_key"`: Uses the specified `store` to retrieve the key.
+
+**2. Run the Server via CLI**
+
+Ensure any required environment variables (like `TAVILY_API_KEY` for the Tavily example, or `AGENTR_API_KEY` if using `"agentr"` type server/integrations) are set.
+
+```bash
+universal_mcp run -c config.json
+```
+
+The server will start, load the configured applications (or connect to AgentR if `type: "agentr"`), and listen for connections based on the `transport` type.
+
+## 🛠️ Using the Playground
+
+The `playground` directory provides a runnable Streamlit application for interacting with agents that can use tools from an MCP server.
+
+**Prerequisites:**
+
+- **`local_config.json`**: This file must exist in the **project root directory** (the same directory as this `README.md`). It configures the _local_ MCP server that the playground's agent can connect to if you choose to run one. For an example, see the `local_config.json` structure in the [Playground README](playground/README.md).
+- **Dependencies**: Install playground-specific dependencies. If you have the project cloned, you might install them via:
+  ```bash
+  pip install -e .[playground]
+  # or manually install fastapi, streamlit, uvicorn, langchain-openai, etc.
+  ```
+
+**Running the Playground:**
+
+The easiest way is to use the automated startup script from the **project root directory**:
+
+```bash
+python playground
+```
+
+This script will:
+
+1. Optionally start a local MCP server (based on your `local_config.json`) if you confirm.
+2. Launch the Streamlit application.
+
+For more detailed setup, manual startup instructions, and an explanation of the `local_config.json` for the playground, please refer to the [Playground README](playground/README.md).
+
+## 🧩 Available Applications
+
+Universal MCP can integrate with a wide variety of applications. For a list of publicly available applications and their slugs (e.g., "github", "google-calendar"), please visit [AgentR Applications](https://agentr.dev).
+Applications are typically installed dynamically by Universal MCP from their respective repositories when first referenced by slug.
+
+_Authentication Type Notes:_
+
+- _OAuth (via AgentR)_: Usually requires configuring the app's integration with `type: "agentr"` in your `ServerConfig`. This leverages the AgentR platform for the OAuth flow and requires the `AGENTR_API_KEY` to be set.
+- _API Key (via Integration)_: Requires configuring `type: "api_key"` for the app's integration in your `ServerConfig`, along with a `store` (like `environment` or `keyring`) to specify where the API key is located.
+
+## 🔐 Integration Types
+
+Universal MCP supports different ways to handle authentication for applications:
+
+### 1. API Key Integration (`type: "api_key"`)
+
+For services that authenticate via simple API keys.
+
+```json
+// In your ServerConfig apps array:
+{
+  "name": "tavily",
+  "integration": {
+    "name": "TAVILY_API_KEY", // Used by the store (e.g., as env var name)
+    "type": "api_key",
+    "store": {
+      "type": "environment" // Or "keyring", "memory"
+    }
+  }
+}
+```
+
+### 2. AgentR Integration (`type: "agentr"`)
+
+Recommended for services integrated with the AgentR platform, which typically handles OAuth flows or centrally managed credentials. Requires the `AGENTR_API_KEY` environment variable to be set for the MCP server process.
+
+```json
+// In your ServerConfig apps array:
+{
+  "name": "github",
+  "integration": {
+    "name": "github", // Matches the service name configured in AgentR
+    "type": "agentr"
+  }
+}
+```
+
+When an action requiring authorization is called, the `AgentRIntegration` will prompt the user (via the MCP client) to visit a URL to complete the OAuth flow managed by AgentR. This is also the default integration type for apps if the main server config is `type: "agentr"`.
+
+### 3. Direct OAuth Integration (`type: "oauth"`)
+
+While `AgentRIntegration` is generally preferred for OAuth, a direct `OAuthIntegration` class exists. However, it requires manual configuration of client IDs, secrets, and callback handling, which is more complex to set up outside the AgentR platform.
+
+## 🤖 CLI Usage
+
+Universal MCP includes a powerful command-line interface:
+
+```bash
+# Run the MCP server using a configuration file
+universal_mcp run -c config.json
+
+# Initialize a new MCP application project structure
+universal_mcp init --app-name my-cool-app --o ./my-apps --integration-type api_key
+
+# Generate API client code and application structure from an OpenAPI schema
+universal_mcp generate -s <path_to_schema.json_or_yaml> -o <path/to/app_output_directory> --c CustomAppClassName
+# Example: universal_mcp generate -s notion_api.yaml -o ./custom_apps/notion --c MyNotionApp
+
+# Preprocess an OpenAPI schema using an LLM to fill/enhance descriptions
+universal_mcp preprocess -s <path_to_input_schema.json_or_yaml> -o <path_to_processed_schema.json_or_yaml>
+
+# Generate Google-style docstrings for functions in a Python file using an LLM
+universal_mcp docgen <path/to/app_file.py>
+
+# Generate a README.md for a generated application file
+universal_mcp readme <path/to/app_file.py>
+
+# Install MCP configuration for supported desktop apps (e.g., Claude, Cursor)
+# Requires an AgentR API key for configuration.
+universal_mcp install claude
+universal_mcp install cursor
+
+# Check installed version (standard typer command)
+universal_mcp --version
+```
+
+## 📋 Requirements
+
+- Python 3.10+
+- Key Dependencies (installed automatically via pip, see `pyproject.toml` for full list):
+  - `mcp-server`
+  - `loguru`
+  - `typer`
+  - `httpx`
+  - `pydantic`
+  - `pyyaml`
+  - `keyring` (for `KeyringStore`)
+  - `litellm` (for `docgen` and `preprocess` commands)
+  - `uv` (used internally for dynamic package installation)
+
+## 📚 Documentation
+
+For more detailed information about specific components:
+
+- [Applications Framework](src/universal_mcp/applications/README.md)
+- [Tool Management](src/universal_mcp/tools/README.md)
+- [Server Implementations](src/universal_mcp/servers/README.md)
+- [Credential Stores](src/universal_mcp/stores/README.md)
+- [Integration & Authentication](src/universal_mcp/integrations/README.md)
+- [Playground Usage](playground/README.md)
+
+## 📝 License
+
+This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.

{universal_mcp-0.1.15rc5 → universal_mcp-0.1.16}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "universal-mcp"
-version = "0.1.15-rc5"
+version = "0.1.16"
 description = "Universal MCP acts as a middle ware for your API applications. It can store your credentials, authorize, enable disable apps on the fly and much more."
 readme = "README.md"
 authors = [
@@ -18,9 +18,10 @@ dependencies = [
     "gql[all]>=3.5.2",
     "jsonref>=1.1.0",
     "keyring>=25.6.0",
+    "langchain-mcp-adapters>=0.0.3",
     "litellm>=1.30.7",
     "loguru>=0.7.3",
-    "mcp>=1.6.0",
+    "mcp>=1.7.1",
     "posthog>=3.24.0",
     "pydantic>=2.11.1",
     "pydantic-settings>=2.8.1",
@@ -39,13 +40,13 @@ dev = [
     "ruff>=0.11.4",
 ]
 playground = [
-    "langchain-mcp-adapters>=0.0.3",
     "langchain-openai>=0.3.12",
     "langgraph>=0.3.24",
     "langgraph-checkpoint-sqlite>=2.0.6",
     "python-dotenv>=1.0.1",
     "streamlit>=1.44.1",
     "watchdog>=6.0.0",
+    "litellm>=1.30.7",
 ]
 
 [project.scripts]
@@ -57,7 +58,6 @@ universal_mcp = "universal_mcp.cli:app"
 [tool.hatch.build.targets.sdist]
 include = [
     "/src",
-    "/templates", # Important: Include the templates directory!
 ]
 
 [tool.hatch.build.targets.wheel]
@@ -98,7 +98,7 @@ exclude = [
     "site-packages",
     "venv",
 ]
-line-length = 88
+line-length = 120
 indent-width = 4
 target-version = "py312"
 

{universal_mcp-0.1.15rc5 → universal_mcp-0.1.16}/src/tests/test_api_generator.py

@@ -3,7 +3,7 @@ from pathlib import Path
 
 import pytest
 
-from universal_mcp.utils.api_generator import generate_api_from_schema
+from universal_mcp.utils.openapi.api_generator import generate_api_from_schema
 
 
 @pytest.fixture
@@ -70,9 +70,7 @@ async def test_generate_api_with_output(sample_schema, temp_dir):
     """Test API generation with output file."""
     output_path = temp_dir / "test.py"
 
-    app_file = generate_api_from_schema(
-        schema_path=sample_schema, output_path=output_path
-    )
+    app_file = generate_api_from_schema(schema_path=sample_schema, output_path=output_path)
 
     assert "app_file" != None
     assert "readme_file" != None
@@ -100,9 +98,7 @@ async def test_generate_api_invalid_schema(temp_dir):
 async def test_generate_api_nonexistent_schema():
     """Test API generation with nonexistent schema file."""
     with pytest.raises(FileNotFoundError):
-        await generate_api_from_schema(
-            schema_path=Path("nonexistent.json"), output_path=None
-        )
+        await generate_api_from_schema(schema_path=Path("nonexistent.json"), output_path=None)
 
 
 @pytest.mark.asyncio
@@ -110,9 +106,7 @@ async def test_generate_api_without_docstrings(sample_schema, temp_dir):
     """Test API generation without docstring generation."""
     output_path = temp_dir / "test_without_docs.py"
 
-    app_file = generate_api_from_schema(
-        schema_path=sample_schema, output_path=output_path
-    )
+    app_file = generate_api_from_schema(schema_path=sample_schema, output_path=output_path)
 
     assert app_file is not None
     assert app_file.exists()
@@ -169,9 +163,7 @@ async def test_generate_api_with_complex_schema(temp_dir):
         json.dump(schema, f)
 
     output_path = temp_dir / "complex.py"
-    app_file = generate_api_from_schema(
-        schema_path=schema_file, output_path=output_path
-    )
+    app_file = generate_api_from_schema(schema_path=schema_file, output_path=output_path)
 
     assert app_file is not None
     assert app_file.exists()