universal-mcp-applications 0.1.17__py3-none-any.whl → 0.1.33__py3-none-any.whl

universal_mcp/applications/hubspot/app.py

@@ -4,21 +4,8 @@ from typing import Any
 from universal_mcp.applications.application import APIApplication
 from universal_mcp.integrations import Integration
 
-
-class CrmApi:
-    def __init__(self, api_client):
-        pass
-
-    def list_tools(self):
-        return []
-
-
-class MarketingApi:
-    def __init__(self, api_client):
-        pass
-
-    def list_tools(self):
-        return []
+from universal_mcp.applications.hubspot.api_segments.crm_api import CrmApi
+from universal_mcp.applications.hubspot.api_segments.marketing_api import MarketingApi
 
 
 class HubspotApp(APIApplication):

universal_mcp/applications/jira/app.py

@@ -1,7 +1,6 @@
 from typing import Any
 
 import httpx
-
 from universal_mcp.applications.application import APIApplication
 from universal_mcp.integrations import Integration
 

universal_mcp/applications/klaviyo/README.md

@@ -275,39 +275,3 @@ This is automatically generated from OpenAPI schema for the KlaviyoApp API.
 | `update_webhook` | Updates the webhook resource identified by {id} using partial modifications, requiring a revision header and returning appropriate status codes for success (200), client errors (400), or server errors (500). |
 | `get_webhook_topics` | Retrieves webhook topics with an optional revision header parameter, returning 200, 400, or 500 status codes. |
 | `get_webhook_topic` | Retrieves a webhook topic by its ID using the GET method, supporting revision information via a header parameter, and returns responses for successful retrieval (200), bad requests (400), and internal server errors (500). |
-
-
-## 📁 Project Structure
-
-The generated project has a standard layout:
-```
-.
-├── src/                  # Source code directory
-│   └── universal_mcp_klaviyoapp/
-│       ├── __init__.py
-│       └── mcp.py        # Server is launched here
-│       └── app.py        # Application tools are defined here
-├── tests/                # Directory for project tests
-├── .env                  # Environment variables (for local development)
-├── pyproject.toml        # Project dependencies managed by uv
-├── README.md             # This file
-```
-
-## 📝 License
-
-This project is licensed under the MIT License.
-
----
-
-_This project was generated using **MCP CLI** — Happy coding! 🚀_
-
-## Usage
-
-- Login to AgentR
-- Follow the quickstart guide to setup MCP Server for your client
-- Visit Apps Store and enable the KlaviyoApp app
-- Restart the MCP Server
-
-### Local Development
-
-- Follow the README to test with the local MCP Server 

universal_mcp/applications/linkedin/README.md

@@ -9,7 +9,21 @@ This is automatically generated from OpenAPI schema for the LinkedinApp API.
 
 | Tool | Description |
 |------|-------------|
-| `create_post` | Create a post on LinkedIn. |
-| `get_your_info` | Get your LinkedIn profile information. |
-| `delete_post` | Delete a post on LinkedIn. |
-| `update_post` | Update a post on LinkedIn. |
+| `list_all_chats` | Retrieves a paginated list of all chat conversations across linked accounts. Supports filtering by unread status, date range, and account provider, distinguishing it from functions listing messages within a single chat. |
+| `list_chat_messages` | Retrieves messages from a specific chat identified by `chat_id`. Supports pagination and filtering by date or sender. Unlike `list_all_messages`, which fetches from all chats, this function targets the contents of a single conversation. |
+| `send_chat_message` | Sends a text message to a specific chat conversation using its `chat_id`. This function creates a new message via a POST request, distinguishing it from read-only functions like `list_chat_messages`. It returns the API's response, which typically confirms the successful creation of the message. |
+| `retrieve_chat` | Retrieves a single chat's details using its Unipile or provider-specific ID. This function is distinct from `list_all_chats`, which returns a collection, by targeting one specific conversation. |
+| `list_all_messages` | Retrieves a paginated list of messages from all chats associated with the account. Unlike `list_chat_messages` which targets a specific conversation, this function provides a global message view, filterable by sender and date range. |
+| `list_profile_posts` | Retrieves a paginated list of posts from a specific user or company profile using their provider ID. An authorizing `account_id` is required, and the `is_company` flag must specify the entity type, distinguishing this from `retrieve_post` which fetches a single post by its own ID. |
+| `retrieve_own_profile` | Retrieves the profile details for the user associated with the Unipile account. This function targets the API's 'me' endpoint to fetch the authenticated user's profile, distinct from `retrieve_user_profile` which fetches profiles of other users by their public identifier. |
+| `retrieve_user_profile` | Retrieves a specific LinkedIn user's profile using their public or internal ID. Unlike `retrieve_own_profile`, which fetches the authenticated user's details, this function targets and returns data for any specified third-party user profile on the platform. |
+| `retrieve_post` | Fetches a specific post's details by its unique ID. Unlike `list_profile_posts`, which retrieves a collection of posts from a user or company profile, this function targets one specific post and returns its full object. |
+| `list_post_comments` | Fetches comments for a specific post. Providing an optional `comment_id` retrieves threaded replies instead of top-level comments. This read-only operation contrasts with `create_post_comment`, which publishes new comments, and `list_content_reactions`, which retrieves 'likes'. |
+| `create_post` | Publishes a new top-level post from the account, including text, user mentions, and an external link. This function creates original content, distinguishing it from `create_post_comment` which adds replies to existing posts. |
+| `list_content_reactions` | Retrieves a paginated list of reactions for a given post or, optionally, a specific comment. This read-only operation uses the account for the request, distinguishing it from the `create_reaction` function which adds new reactions. |
+| `create_post_comment` | Publishes a comment on a specified post. By providing an optional `comment_id`, it creates a threaded reply to an existing comment instead of a new top-level one. This function's dual capability distinguishes it from `list_post_comments`, which only retrieves comments and their replies. |
+| `create_reaction` | Adds a specified reaction (e.g., 'like', 'love') to a LinkedIn post or, optionally, to a specific comment. This function performs a POST request to create the reaction, differentiating it from `list_content_reactions` which only retrieves existing ones. |
+| `search_companies` | Performs a paginated search for companies on LinkedIn using keywords, with optional location and industry filters. Its specific 'companies' search category distinguishes it from other methods like `search_people` or `search_posts`, ensuring that only company profiles are returned. |
+| `search_jobs` | Performs a LinkedIn search for jobs, filtering results by keywords, region, industry, and minimum salary. Unlike other search functions (`search_people`, `search_companies`), this method is specifically configured to query the 'jobs' category, providing a paginated list of relevant employment opportunities. |
+| `search_people` | Searches for LinkedIn user profiles using keywords, with optional filters for location, industry, and company. This function specifically targets the 'people' category, distinguishing it from other search methods like `search_companies` or `search_jobs` that query different entity types through the same API endpoint. |
+| `search_posts` | Performs a keyword-based search for LinkedIn posts, allowing filters for date and sorting by relevance. This function executes a general, platform-wide content search, distinguishing it from other search functions that target people, companies, or jobs, and from `list_profile_posts` which retrieves from a specific profile. |