universal-mcp-applications 0.1.18__py3-none-any.whl → 0.1.19__py3-none-any.whl

universal_mcp/applications/ahrefs/README.md

@@ -1,10 +1,10 @@
-# Ahrefs MCP Server
+# AhrefsApp MCP Server
 
-An MCP Server for the Ahrefs API.
+An MCP Server for the AhrefsApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Ahrefs API.
+This is automatically generated from OpenAPI schema for the AhrefsApp API.
 
 
 | Tool | Description |

universal_mcp/applications/airtable/README.md

@@ -1,10 +1,10 @@
-# Airtable MCP Server
+# AirtableApp MCP Server
 
-An MCP Server for the Airtable API.
+An MCP Server for the AirtableApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Airtable API.
+This is automatically generated from OpenAPI schema for the AirtableApp API.
 
 
 | Tool | Description |

universal_mcp/applications/asana/README.md

@@ -1,10 +1,10 @@
-# Asana MCP Server
+# AsanaApp MCP Server
 
-An MCP Server for the Asana API.
+An MCP Server for the AsanaApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Asana API.
+This is automatically generated from OpenAPI schema for the AsanaApp API.
 
 
 | Tool | Description |

universal_mcp/applications/aws_s3/README.md

@@ -0,0 +1,29 @@
+# AwsS3App MCP Server
+
+An MCP Server for the AwsS3App API.
+
+## 🛠️ Tool List
+
+This is automatically generated from OpenAPI schema for the AwsS3App API.
+
+
+| Tool | Description |
+|------|-------------|
+| `create_bucket` | Creates a new Amazon S3 bucket with a specified name and optional region. Returns `True` upon successful creation, or `False` if an AWS client error, such as a naming conflict or permission issue, occurs. |
+| `delete_bucket` | Deletes a specified S3 bucket. The operation requires the bucket to be empty to succeed. It returns `True` if the bucket is successfully deleted and `False` if an error occurs, such as the bucket not being found or containing objects. |
+| `get_bucket_policy` | Retrieves the IAM resource policy for a specified S3 bucket, parsing the JSON string into a dictionary. If the operation fails due to permissions or a non-existent policy, it returns an error dictionary. This complements `put_bucket_policy`, which applies a new policy. |
+| `set_bucket_policy` | Applies or replaces the access policy for a specified S3 bucket. The function accepts the policy as a dictionary, converts it to JSON, and assigns it to the bucket. This write operation is the counterpart to `get_bucket_policy` and returns `True` on success. |
+| `list_subdirectories` | Lists immediate subdirectories (common prefixes) within an S3 bucket. If a prefix is provided, it returns subdirectories under that path; otherwise, it lists top-level directories. This function specifically lists folders, distinguishing it from `list_objects`, which lists files. |
+| `create_prefix` | Creates a prefix (folder) in an S3 bucket, optionally nested under a parent prefix. It simulates a directory by creating a zero-byte object with a key ending in a slash ('/'), distinguishing it from put_object, which uploads content. |
+| `list_objects` | Paginates through and lists all objects within a specified S3 bucket prefix. It returns a curated list of metadata for each object (key, name, size, last modified), excluding folder placeholders. This function specifically lists files, distinguishing it from `list_prefixes` which lists folders. |
+| `put_text_object` | Uploads string content to create an object in a specified S3 bucket and prefix. The content is UTF-8 encoded before being written. This method is for text, distinguishing it from `put_object_from_base64` which handles binary data. |
+| `put_object_from_base64` | Decodes a base64 string into binary data and uploads it as an object to a specified S3 location. This method is designed for binary files, differentiating it from `put_object` which handles plain text content. Returns true on success. |
+| `get_object_with_content` | Retrieves an S3 object's content. It decodes text files as UTF-8 or encodes binary files as base64 based on the object's key. This function downloads the full object body, unlike `get_object_metadata` which only fetches metadata without content, returning the content, name, size, and type. |
+| `get_object_metadata` | Efficiently retrieves metadata for a specified S3 object, such as size and last modified date, without downloading its content. This function uses a HEAD request, making it faster than `get_object_content` for accessing object properties. Returns a dictionary of metadata or an error message on failure. |
+| `copy_object` | Copies an S3 object from a specified source location to a destination, which can be in the same or a different bucket. Unlike `move_object`, the original object remains at the source after the copy operation. It returns `True` for a successful operation. |
+| `move_object` | Moves an S3 object from a source to a destination. This is achieved by first copying the object to the new location and subsequently deleting the original. The move can occur within the same bucket or between different ones, returning `True` on success. |
+| `delete_single_object` | Deletes a single, specified object from an S3 bucket using its key. Returns `True` if successful, otherwise `False`. For bulk deletions in a single request, the `delete_objects` function should be used instead. |
+| `delete_objects` | Performs a bulk deletion of objects from a specified S3 bucket in a single request. Given a list of keys, it returns a dictionary detailing successful deletions and any errors. This method is the batch-processing counterpart to the singular `delete_object` function, designed for efficiency. |
+| `generate_presigned_url` | Generates a temporary, secure URL for a specific S3 object. This URL grants time-limited permissions for actions like GET, PUT, or DELETE, expiring after a defined period. It allows object access without sharing permanent AWS credentials. |
+| `search_objects` | Filters objects within an S3 bucket and prefix based on a name pattern and size range. It retrieves all objects via `list_objects` and then applies the specified criteria client-side, returning a refined list of matching objects and their metadata. |
+| `get_storage_summary` | Calculates and returns statistics for an S3 bucket or prefix. The result includes the total number of objects, their combined size in bytes, and a human-readable string representation of the size (e.g., '15.2 MB'). |

universal_mcp/applications/bill/README.md

@@ -0,0 +1,249 @@
+# BillApp MCP Server
+
+An MCP Server for the BillApp API.
+
+## 🛠️ Tool List
+
+This is automatically generated from OpenAPI schema for the BillApp API.
+
+
+| Tool | Description |
+|------|-------------|
+| `list_customer_attachments` | Get list of customer attachments |
+| `create_customer_attachment` | Upload customer attachment |
+| `list_invoice_attachments` | Get list of invoice attachments |
+| `create_invoice_attachment` | Upload invoice attachment |
+| `list_vendor_attachments` | Get list of vendor attachments |
+| `create_vendor_attachment` | Upload vendor attachment |
+| `get_attachment` | Get attachment details |
+| `list_bills` | Get list of bills |
+| `create_bill` | Create a bill |
+| `create_bulk_bills` | Create multiple bills |
+| `get_bill` | Get bill details |
+| `replace_bill` | Replace a bill |
+| `update_bill` | Update a bill |
+| `archive_bill` | Archive a bill |
+| `restore_bill` | Restore an archived bill |
+| `list_classification_accounting_classes` | Get list of accounting classes |
+| `create_classification_accounting_class` | Create an accounting class |
+| `bulk_create_classification_accounting_class` | Create multiple accounting classes |
+| `bulk_update_classification_accounting_class` | Update multiple accounting classes |
+| `bulk_archive_classification_accounting_class` | Archive multiple accounting classes |
+| `bulk_restore_classification_accounting_class` | Restore multiple accounting classes |
+| `get_classification_accounting_class` | Get accounting class details |
+| `update_classification_accounting_class` | Update an accounting class |
+| `archive_classification_accounting_class` | Archive an accounting class |
+| `restore_classification_accounting_class` | Restore an archived accounting class |
+| `list_classification_chart_of_accounts` | Get list of chart of accounts |
+| `create_classification_chart_of_accounts` | Create a chart of accounts |
+| `bulk_create_classification_chart_of_accounts` | Create multiple chart of accounts |
+| `bulk_update_classification_chart_of_accounts` | Update multiple chart of accounts |
+| `bulk_archive_classification_chart_of_accounts` | Archive mutliple chart of accounts |
+| `bulk_restore_classification_chart_of_accounts` | Restore multiple chart of accounts |
+| `get_classification_chart_of_accounts` | Get chart of accounts details |
+| `update_classification_chart_of_accounts` | Update a chart of accounts |
+| `archive_classification_chart_of_accounts` | Archive a chart of accounts |
+| `restore_classification_chart_of_accounts` | Restore an archived chart of accounts |
+| `list_classification_departments` | Get list of departments |
+| `create_classification_department` | Create a department |
+| `bulk_create_classification_department` | Create multiple departments |
+| `bulk_update_classification_department` | Update multiple departments |
+| `bulk_archive_classification_department` | Archive multiple departments |
+| `bulk_restore_classification_department` | Restore multiple departments |
+| `get_classification_department` | Get department details |
+| `update_classification_department` | Update a department |
+| `archive_classification_department` | Archive a department |
+| `restore_classification_department` | Restore an archived department |
+| `list_classification_employees` | Get list of employees |
+| `create_classification_employee` | Create an employee |
+| `bulk_create_classification_employee` | Create multiple employees |
+| `bulk_update_classification_employee` | Update multiple employees |
+| `bulk_archive_classification_employee` | Archive multiple employees |
+| `bulk_restore_classification_employee` | Restore multiple employees |
+| `get_classification_employee` | Get employee details |
+| `update_classification_employee` | Update an employee |
+| `archive_classification_employee` | Archive an employee |
+| `restore_classification_employee` | Restore an archived employee |
+| `list_classification_items` | Get list of items |
+| `create_classification_item` | Create an item |
+| `bulk_create_classification_item` | Create multiple items |
+| `bulk_update_classification_item` | Update multiple items |
+| `bulk_archive_classification_item` | Archive multiple items |
+| `bulk_restore_classification_item` | Restore multiple items |
+| `get_classification_item` | Get item details |
+| `update_classification_item` | Update an item |
+| `archive_classification_item` | Archive an item |
+| `restore_classification_item` | Restore an archived item |
+| `list_classification_jobs` | Get list of jobs |
+| `create_classification_job` | Create a job |
+| `bulk_create_classification_job` | Create multiple jobs |
+| `bulk_update_classification_job` | Update multiple jobs |
+| `bulk_archive_classification_job` | Archive multiple jobs |
+| `bulk_restore_classification_job` | Restore multiple jobs |
+| `get_classification_job` | Get job details |
+| `update_classification_job` | Update a job |
+| `archive_classification_job` | Archive a job |
+| `restore_classification_job` | Restore an archived job |
+| `list_classification_locations` | Get list of locations |
+| `create_classification_location` | Create a location |
+| `bulk_create_classification_location` | Create multiple locations |
+| `bulk_update_classification_location` | Update multiple locations |
+| `bulk_archive_classification_location` | Archive multiple locations |
+| `bulk_restore_classification_location` | Restore multiple locations |
+| `get_classification_location` | Get location details |
+| `update_classification_location` | Update a location |
+| `archive_classification_location` | Archive a location |
+| `restore_classification_location` | Restore an archived location |
+| `list_customers` | Get list of customers |
+| `create_customer` | Create a customer |
+| `get_customer` | Get customer details |
+| `update_customer` | Update a customer |
+| `archive_customer` | Archive a customer |
+| `restore_customer` | Restore an archived customer |
+| `list_documents` | Get list of documents |
+| `create_bill_document` | Upload bill document |
+| `upload_status` | Get document upload status |
+| `get_document` | Get document details |
+| `list_payable_apcards` | Get list of AP Cards |
+| `list_bank_accounts` | Get list of bank accounts |
+| `create_bank_account` | Create a bank account |
+| `list_bank_account_users` | Get list of bank account users |
+| `nominate_bank_account_user` | Nominate a bank account user |
+| `archive_bank_account_user` | Archive a bank account user |
+| `get_bank_account` | Get bank account details |
+| `update_bank_account` | Update a bank account |
+| `archive_bank_account` | Archive a bank account |
+| `verify_bank_account` | Verify a bank account |
+| `list_payable_card_accounts` | Get list of card accounts |
+| `list_card_funding_purposes` | Get card funding purpose |
+| `list_card_account_users` | Get list of card account users |
+| `get_card_account` | Get card account details |
+| `get_funding_account_permission` | Get funding account permissions |
+| `get_health_check` | Check app health |
+| `list_invoices` | Get list of invoices |
+| `create_invoice` | Create an invoice |
+| `record_invoice` | Record AR payment |
+| `get_invoice` | Get invoice details |
+| `replace_invoice` | Replace an invoice |
+| `update_invoice` | Update an invoice |
+| `archive_invoice` | Archive an invoice |
+| `send_invoice` | Send an invoice |
+| `restore_invoice` | Restore an archived invoice |
+| `login` | API login |
+| `get_session_info` | Get API session details |
+| `logout` | API logout |
+| `generate_challenge` | Generate MFA challenge |
+| `validate_challenge` | Validate MFA challenge |
+| `list_mfa_phones` | Get list of MFA phone numbers |
+| `setup` | Add phone for MFA setup |
+| `validate` | Validate phone for MFA setup |
+| `step_up_session` | MFA step-up for API session |
+| `search` | Search for an organization in the BILL networks |
+| `accept_invitation` | Accept network invitation |
+| `get_customer_invitation` | Get customer invitation status |
+| `create_customer_invitation` | Invite a customer in the BILL network |
+| `delete_customer_invitation` | Delete customer connection |
+| `get_vendor_invitation` | Get vendor invitation status |
+| `create_vendor_invitation` | Invite a vendor in the BILL network |
+| `delete_vendor_invitation` | Delete vendor connection |
+| `list_industries` | Get list of organization industries |
+| `get_organization` | Get organization details |
+| `update_organization` | Update an organization |
+| `get_price_plan` | Get organization price plan details |
+| `partner_login` | API partner login |
+| `login_as_user` | API login as user |
+| `list_partner_organizations` | Get list of organizations |
+| `create_organization` | Create an organization |
+| `create_phone` | Add phone for risk verification |
+| `list_partner_user_roles` | Get list of user roles |
+| `get_partner_user_role` | Get user role details |
+| `list_partner_users` | Get list of users |
+| `create_partner_user` | Create a user |
+| `get_partner_user` | Get user details |
+| `update_partner_user` | Update a user |
+| `archive_partner_user` | Archive a user |
+| `restore_partner_user` | Restore an archived user |
+| `list_payments` | Get list of payments |
+| `create_payment` | Create a payment |
+| `create_bulk_payment` | Create a bulk payment |
+| `list_payment_options` | Get list of vendor payment options |
+| `get_payment` | Get payment details |
+| `cancel_payment` | Cancel a payment |
+| `get_check_image_data` | Get check image data |
+| `void_payment` | Void a payment |
+| `list_recurring_bills` | Get list of recurring bills |
+| `create_recurring_bill` | Create a recurring bill |
+| `get_recurring_bill` | Get recurring bill details |
+| `replace_recurring_bill` | Replace a recurring bill |
+| `update_recurring_bill` | Update a recurring bill |
+| `archive_recurring_bill` | Archive a recurring bill |
+| `restore_recurring_bill` | Restore an archived recurring bill |
+| `get_vendor_audit_trail` | Get audit trail details for a vendor |
+| `get_risk_verifications` | Get risk verification details |
+| `initiate_risk_verifications` | Initiate risk verification for an organization |
+| `get_risk_verification_phone` | Get phone status for risk verification |
+| `create_risk_verification_phone` | Add phone for risk verification |
+| `list_organization_user_roles` | Get list of user roles |
+| `get_organization_user_role` | Get user role details |
+| `list_budgets` | Get list of budgets |
+| `create_budget` | Create a budget |
+| `get_budget` | Get budget details |
+| `delete_budget` | Delete a budget |
+| `update_budget` | Update a budget |
+| `list_budget_members` | Get list of members for a budget |
+| `upsert_bulk_budget_users` | Update a list of budget members in a budget |
+| `get_budget_member` | Get a single member for a budget |
+| `upsert_budget_member` | Add a member to a budget or update an existing member of the budget |
+| `delete_budget_member` | Delete a member from a budget |
+| `list_cards` | Get list of cards |
+| `create_budget_card` | Create a vendor card |
+| `get_card` | Get card details |
+| `delete_card` | Delete a card |
+| `update_card` | Update a vendor card |
+| `get_pan_jwt` | Get PAN JWT |
+| `list_custom_fields` | Get list of custom fields |
+| `create_custom_field` | Create custom field |
+| `get_custom_field` | Get custom field details |
+| `delete_custom_field` | Delete a custom field |
+| `update_custom_field` | Update custom field details |
+| `list_custom_field_values` | Get list of values for custom field |
+| `create_custom_field_values` | Create custom field values |
+| `delete_custom_field_value` | Delete custom field values |
+| `get_custom_field_values` | Get custom field value |
+| `list_reimbursements` | Get list of reimbursements |
+| `create_reimbursement` | Create a reimbursement |
+| `create_image_upload_url` | Create an image upload URL for a reimbursement. |
+| `get_reimbursement` | Get reimbursement details |
+| `delete_reimbursement` | Delete a reimbursement |
+| `update_reimbursement` | Update a reimbursement |
+| `approve_or_deny_reimbursement` | Approve or deny a reimbursement |
+| `list_transactions` | Get list of transactions |
+| `get_transaction` | Get transaction details |
+| `update_transaction` | Update transaction |
+| `list_transaction_custom_fields` | Get transaction custom field details |
+| `update_transaction_custom_fields` | Update a custom field and values on a transaction |
+| `list_transaction_custom_field_values` | Get transaction custom field value details |
+| `list_users` | Get list of users |
+| `create_user` | Create a user |
+| `get_current_user` | Get current user details |
+| `get_user` | Get user details |
+| `delete_user` | Delete a user |
+| `update_user` | Update a user |
+| `list_organization_users` | Get list of users |
+| `create_organization_user` | Create a user |
+| `get_organization_user` | Get user details |
+| `update_organization_user` | Update a user |
+| `archive_organization_user` | Archive a user |
+| `restore_organization_user` | Restore an archived user |
+| `list_vendors` | Get list of vendors |
+| `create_vendor` | Create a vendor |
+| `create_bulk_vendor` | Create multiple vendors |
+| `get_intl_config` | Get international payments configuration |
+| `get_vendor` | Get vendor details |
+| `update_vendor` | Update a vendor |
+| `archive_vendor` | Archive a vendor |
+| `get_vendor_bank_account` | Get vendor bank account details |
+| `create_vendor_bank_account` | Create a vendor bank account |
+| `delete_vendor_bank_account` | Delete a vendor bank account |
+| `get_configuration_by_vendor_id` | Get vendor configuration |
+| `restore_vendor` | Restore an archived vendor |

universal_mcp/applications/calendly/README.md

@@ -1,53 +1,53 @@
-# Calendly MCP Server
+# CalendlyApp MCP Server
 
-An MCP Server for the Calendly API.
+An MCP Server for the CalendlyApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Calendly API.
+This is automatically generated from OpenAPI schema for the CalendlyApp API.
 
 
 | Tool | Description |
 |------|-------------|
-| `list_event_invitees` | Retrieves a paginated list of invitees for a specific scheduled event with optional filtering by status, email, and sorting parameters. |
-| `get_event` | Retrieves details about a scheduled event identified by the provided UUID using the GET method. |
-| `get_event_invitee` | Retrieves detailed information about a specific invitee for a scheduled event using their unique identifiers. |
-| `list_events` | Retrieves a list of scheduled events filtered by user, organization, invitee, status, time range, and other parameters, supporting pagination and sorting. |
-| `get_event_type` | Retrieves the details of a specific event type identified by its UUID using the path "/event_types/{uuid}" and the GET method. |
-| `list_user_sevent_types` | Retrieves a list of event types based on active status, organization, user, availability schedule, sorting, and pagination. |
-| `get_user` | Retrieves a user's details by their unique identifier (UUID) and returns the user data. |
-| `get_current_user` | Retrieves information about the current user using the API. |
-| `list_organization_invitations` | Retrieves a list of invitations for an organization identified by its UUID, allowing filtering by count, page token, sort order, email, and invitation status. |
-| `invite_user_to_organization` | Creates an invitation for a user to join an organization, identified by the provided UUID, and sends it to the specified recipient. |
-| `get_organization_invitation` | Retrieves information about an organization invitation identified by its UUID, returning details about the invitation using the specified organization UUID and invitation UUID. |
-| `revoke_user_sorganization_invitation` | Deletes one or more organization invitations and returns success or error codes indicating invalid tokens, missing invitations, or authorization issues. |
-| `get_organization_membership` | Retrieves details of a specific organization membership using its unique identifier. |
-| `remove_user_from_organization` | Removes a user from an organization using the specified UUID and returns a success status if the operation is completed without errors. |
-| `list_organization_memberships` | Retrieves and lists organization memberships for specified users or organizations, supporting filtering by user, organization, and other criteria, using the "GET" method at the "/organization_memberships" path. |
-| `get_webhook_subscription` | Retrieves the details of a webhook subscription identified by the specified `webhook_uuid`, returning relevant subscription information in response. |
-| `delete_webhook_subscription` | Deletes a webhook subscription identified by its unique UUID and returns a success response upon completion. |
-| `list_webhook_subscriptions` | Retrieves a paginated list of webhook subscriptions filtered by organization, user, and scope, with options for sorting and count. |
-| `create_webhook_subscription` | Creates a new webhook subscription to receive notifications for specified events from a Squarespace website. |
-| `create_single_use_scheduling_link` | Creates a new scheduling link using the "POST" method at the "/scheduling_links" path, allowing users to generate customized links for scheduling events. |
-| `delete_invitee_data` | Initiates data deletion requests for invitees in compliance with data privacy regulations. |
-| `delete_scheduled_event_data` | Submits data deletion requests for compliance events and returns asynchronous processing confirmation. |
-| `get_invitee_no_show` | Retrieves information about an invitee who did not show up, identified by a specific UUID, using the GET method via the API endpoint "/invitee_no_shows/{uuid}". |
-| `delete_invitee_no_show` | Removes an invitee's "no-show" status using their unique identifier (uuid) and returns an empty response upon successful deletion. |
-| `create_invitee_no_show` | Triggers an action related to invitee no-shows using the POST method at the "/invitee_no_shows" endpoint, returning a status message based on the response codes provided. |
-| `get_group` | Retrieves information about a group specified by its UUID from the API. |
-| `list_groups` | Retrieves a list of groups for a specified organization using the GitHub API, with optional pagination controls. |
-| `get_group_relationship` | Retrieves information about group relationships identified by the specified UUID using the GET method. |
-| `list_group_relationships` | Retrieves a list of group relationships filtered by organization, owner, or group, using pagination parameters for controlled results. |
-| `get_routing_form` | Retrieves a routing form by its unique identifier (UUID) using the GET method via the "/routing_forms/{uuid}" path. |
-| `list_routing_forms` | Retrieves a list of routing forms for a specified organization with pagination, sorting, and count parameters. |
-| `get_routing_form_submission` | Retrieves a specific routing form submission by its unique identifier (UUID) using the Calendly API. |
-| `list_routing_form_submissions` | Retrieves routing form submissions using the GET method at "/routing_form_submissions", allowing filtering by form, count, page token, and sort order. |
-| `list_event_type_available_times` | Retrieves a list of available times for a specified event type within a given date range, using the event type, start time, and end time as query parameters. |
-| `list_activity_log_entries` | Retrieves filtered activity log entries based on parameters like organization, actor, timestamps, and action, supporting sorting and pagination. |
-| `create_share` | Creates a new share resource and returns a status message. |
-| `list_user_busy_times` | Retrieves an ascending list of a user's internal and external scheduled events within a specified date range using the "/user_busy_times" endpoint, allowing for efficient management of busy times. |
-| `get_user_availability_schedule` | Retrieves the availability schedule of a user based on the provided UUID using the GET method. |
-| `list_user_availability_schedules` | Retrieves the availability schedule for a specified user, including time intervals when booking is permitted. |
-| `list_event_type_hosts` | Retrieves paginated event type memberships filtered by event type, count, and page token. |
-| `create_one_off_event_type` | Creates a one-off event type using the "POST" method, allowing for the setup of a single, unique event configuration. |
-| `get_sample_webhook_data` | Retrieves sample webhook data filtered by event type, organization, user, and scope parameters. |
+| `list_event_invitees` | Retrieves a paginated list of invitees for a specific scheduled event, identified by its UUID. The results can be filtered by invitee status or email, sorted by creation date, and the list size can be controlled using pagination parameters. |
+| `get_scheduled_event` | Retrieves the details for a specific scheduled event using its unique identifier (UUID). This targets a single event instance, differentiating it from `list_events` which fetches a collection of events and `get_event_type` which retrieves an event template. |
+| `get_event_invitee` | Fetches detailed information for a single invitee associated with a specific scheduled event. It uses both the event's UUID and the invitee's UUID to uniquely identify and retrieve the correct record, distinguishing it from `list_event_invitees` which returns a collection. |
+| `list_scheduled_events` | Fetches a list of scheduled events, offering extensive filtering by user, organization, invitee email, status, and time range. Supports pagination and sorting, providing a flexible method to query specific event data from the Calendly API. |
+| `get_event_type` | Retrieves the full details of a specific event type, such as its name, duration, and scheduling rules, by providing its unique identifier (UUID). It fetches a single resource, unlike list_user_sevent_types which retrieves a collection. |
+| `list_event_types` | Retrieves a collection of event types from the `/event_types` endpoint. Results can be filtered by user, organization, or status, and the list supports sorting and pagination for controlled data retrieval. |
+| `get_user` | Retrieves the details of a specific user identified by their unique identifier (UUID). This differs from `get_current_user`, which fetches the profile of the currently authenticated user. |
+| `get_current_user` | Retrieves profile information for the currently authenticated user by querying the `/users/me` endpoint. This function requires no parameters, unlike `get_user` which fetches a specific user by their UUID. |
+| `list_organization_invitations` | Retrieves a paginated list of invitations for a specific organization, identified by its UUID. It allows optional filtering by email and status (e.g., pending, accepted) and sorting. This function fetches a collection of invitations, unlike `get_organization_invitation` which retrieves a single one. |
+| `create_organization_invitation` | Invites a user via email to join a specific organization, identified by the organization's UUID. This function creates a new pending invitation, distinguishing it from functions that list, retrieve, or revoke existing invitations. |
+| `get_organization_invitation` | Retrieves the details of a single, specific invitation within an organization. It requires both the organization's unique identifier (`org_uuid`) and the invitation's unique identifier (`uuid`) for the lookup. |
+| `revoke_user_organization_invitation` | Revokes a specific user's invitation to an organization, identified by the organization and invitation UUIDs. This action permanently deletes the pending invitation, preventing it from being accepted. |
+| `get_organization_membership` | Fetches the details of a specific organization membership using its unique identifier (UUID). Unlike `list_organization_memberships`, this function retrieves a single membership record rather than a collection. |
+| `delete_organization_membership` | Deletes an organization membership by its unique UUID, effectively removing the associated user from the organization. This function is the destructive counterpart to `get_organization_membership` and acts on active members, not pending invitations. |
+| `list_organization_memberships` | Retrieves a paginated list of organization memberships. The results can be filtered by user, organization, or email address to narrow down the search for specific members within one or more organizations. |
+| `get_webhook_subscription` | Fetches detailed information for a single webhook subscription using its unique identifier (UUID). Unlike `list_webhook_subscriptions`, which returns a collection, this function retrieves one specific subscription's configuration and status. |
+| `delete_webhook_subscription` | Deletes a specific webhook subscription using its unique `webhook_uuid`. This function sends a DELETE request to the Calendly API to permanently remove the subscription, stopping all future event notifications. It raises an error if the deletion fails. |
+| `list_webhook_subscriptions` | Retrieves a collection of webhook subscriptions for a given scope (organization or user). Supports filtering, sorting, and pagination to browse multiple subscriptions, unlike functions like `get_webhook_subscription` which fetches a single subscription by its unique ID. |
+| `create_webhook_subscription` | Creates a Calendly webhook subscription for specified events. It requires a callback URL, the scope (e.g., organization, user), and the list of events to monitor, registering the webhook via a POST request to the API. |
+| `create_limited_use_scheduling_link` | Generates a unique, limited-use scheduling link for a specific owner, such as an event type. The link is valid for a specified maximum number of bookings, after which it expires. |
+| `request_invitee_data_deletion` | Submits an asynchronous data deletion request for one or more invitees, identified by their email addresses, to comply with privacy regulations. This action permanently removes invitee information from the system. |
+| `request_scheduled_event_data_deletion` | For data compliance, submits an asynchronous request to delete scheduled event data within a specified `start_time` and `end_time`. This targets events by time range, unlike `delete_invitee_data` which targets specific individuals. |
+| `get_invitee_no_show` | Retrieves the details for a specific 'no-show' record associated with an invitee, identified by its unique ID (UUID). This function fetches a single record, unlike create_invitee_no_show which creates one. |
+| `revoke_invitee_no_show` | Deletes an invitee's 'no-show' record using its unique UUID. This operation revokes the no-show status previously assigned to an invitee, effectively undoing the action of `create_invitee_no_show`. |
+| `mark_invitee_as_no_show` | Marks a specific invitee as a 'no-show' by creating a no-show record. It requires the invitee's URI and sends a POST request to the `/invitee_no_shows` endpoint, returning the details of the newly created entry. |
+| `get_group_by_id` | Retrieves the details of a specific group by its unique identifier (UUID). Unlike `list_groups`, which returns multiple group records, this function fetches information for a single group. |
+| `list_groups` | Retrieves a paginated list of groups associated with a specific organization. The result set can be controlled using pagination parameters for the page token and the number of items to return per page. |
+| `get_group_relationship` | Retrieves the details of a specific group relationship, which connects an owner (like a user or invitation) to a group, by its unique identifier (UUID). This differs from `list_group_relationships` which fetches a list. |
+| `list_group_relationships` | Fetches a paginated list of group relationships. The results can be filtered by organization, owner, or a specific group to refine the search and control the returned data set. |
+| `get_routing_form` | Retrieves the details of a specific routing form using its unique identifier (UUID). This is distinct from `list_routing_forms`, which fetches a collection, and from functions that retrieve form submissions. |
+| `list_routing_forms` | Retrieves a list of routing forms for a specified organization. This function supports pagination using a page token, sorting by creation date, and limiting the number of results returned per request, distinguishing it from `get_routing_form` which fetches a single item. |
+| `get_routing_form_submission` | Fetches details for a single routing form submission using its unique identifier (UUID). It queries the `/routing_form_submissions/{uuid}` endpoint, distinct from `list_routing_form_submissions` which retrieves multiple submissions. |
+| `get_routing_form_submissions` | Retrieves a paginated list of submissions associated with a specific routing form. The results can be sorted by creation date and navigated using count and page_token parameters. |
+| `list_event_type_available_times` | Retrieves a list of concrete, bookable time slots for a specific event type within a defined start and end time. It provides specific availability, distinct from functions that list a user's general busy times or configured schedules. |
+| `list_activity_log_entries` | Fetches a paginated list of activity log entries for an organization. Allows advanced filtering by actor, time range, search term, namespace, and action, with support for custom sorting and pagination to refine the results. |
+| `create_shareable_link` | Creates a custom, shareable scheduling link by defining properties like availability rules, event duration, and location. This generates a unique booking link tailored to specific settings, differing from standard event types or single-use links. |
+| `list_user_busy_times` | Fetches a user's busy time intervals within a specified date range, including all scheduled events. This helps determine actual unavailability, differing from `list_user_availability_schedules` which retrieves a user's general working hours. |
+| `get_user_availability_schedule` | Retrieves a specific user availability schedule by its unique identifier (UUID). It fetches a single schedule resource, unlike `list_user_availability_schedules`, which returns all schedules associated with a user. |
+| `list_schedules_for_user` | Retrieves all availability schedules for a specified user via their URI. Unlike `get_user_availability_schedule`, which fetches a single schedule by its UUID, this function returns a collection of all schedules defining a user's availability intervals. |
+| `list_event_type_memberships` | Retrieves a paginated list of all user memberships (hosts) for a specific event type. It requires the event type's URI and allows for navigating through results using `count` and `page_token` parameters, returning the membership objects. |
+| `create_one_off_event_type` | Creates a unique, non-reusable event type for a single, ad-hoc meeting. It defines event details like host, co-hosts, duration, and location, distinguishing it from standard, reusable event types. |
+| `get_sample_webhook_data` | Fetches a sample webhook data payload for a specified event, organization, and scope. This helps developers preview the JSON structure for a webhook notification, facilitating testing and integration without needing to trigger a live event. |

universal_mcp/applications/canva/README.md

@@ -1,43 +1,43 @@
-# Canva MCP Server
+# CanvaApp MCP Server
 
-An MCP Server for the Canva API.
+An MCP Server for the CanvaApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Canva API.
+This is automatically generated from OpenAPI schema for the CanvaApp API.
 
 
 | Tool | Description |
 |------|-------------|
-| `v1_apps_appid_jwks` | Retrieves the JSON Web Key Set (JWKS) containing public keys for verifying JWTs associated with the specified application. |
-| `v1_assets_assetid1` | Retrieves the details of a specific asset using the provided assetId and returns the asset data. |
-| `v1_assets_assetid3` | Updates an asset using the "POST" method at the "/v1/assets/{assetId}" endpoint and returns a status message. |
-| `v1_assets_assetid` | Deletes an asset by its unique identifier and returns a success status upon completion. |
-| `v1_assets_assetid2` | Updates specific properties of an asset identified by its ID and returns the operation status. |
-| `v1_assets_upload` | Uploads an asset with provided metadata to the server and returns a success or error status. |
-| `v1_asset_uploads` | Initiates an asset upload using the "POST" method at the "/v1/asset-uploads" path, accepting asset metadata in the header and handling responses for successful and failed uploads. |
-| `v1_asset_uploads_jobid` | Retrieves the status and results of an asset upload job identified by the job ID. |
-| `v1_autofills` | Triggers an autofill operation using the API at the "/v1/autofills" path, sending data via the POST method, and returns a response indicating success or failure. |
-| `v1_autofills_jobid` | Retrieves autofill data for a job identified by the specified jobId using the GET method at the "/v1/autofills/{jobId}" endpoint. |
-| `v1_brand_templates` | Retrieves a list of brand templates based on query parameters such as ownership and sorting options using the "GET" method at the "/v1/brand-templates" path. |
-| `v1_brand_templates_brandtemplateid` | Retrieves metadata for a specific brand template using its unique identifier. |
-| `v1_brand_templates_brandtemplateid_dataset` | Retrieves the dataset definition of a brand template, including data field names and types, allowing for the identification of autofillable fields. |
-| `v1_comments` | Creates a new comment and returns a status message. |
-| `v1_comments_commentid_replies` | Creates a new reply to a comment using the "POST" method. |
-| `v1_designs_designid_comments_commentid` | Retrieves a specific comment from a design using the provided design ID and comment ID. |
-| `v1_connect_keys` | Retrieves a list of connection keys associated with the current user or application. |
-| `v1_designs` | Retrieves a list of designs based on query parameters, including query, continuation, ownership, and sort order, using the GET method at the "/v1/designs" endpoint. |
-| `v1_designs1` | Creates a new design resource and returns the result of the operation. |
-| `v1_designs_designid` | Retrieves a specific design by its ID using the GET method at the "/v1/designs/{designId}" endpoint. |
-| `v1_imports` | Initiates a data import process with the provided metadata in the request header and returns an appropriate response. |
-| `v1_imports_jobid` | Retrieves the status and details of a specific import job identified by its job ID. |
-| `v1_exports` | Initiates an export process through the API and returns status codes for success or failure. |
-| `v1_exports_exportid` | Retrieves export details by ID using the "GET" method at the path "/v1/exports/{exportId}" and returns a response. |
-| `v1_folders_folderid1` | Retrieves information about a folder with the specified ID using the "GET" method at the "/v1/folders/{folderId}" endpoint. |
-| `v1_folders_folderid` | Deletes a folder with the specified ID, including all of its contents, using the DELETE method and returns a status code indicating success or failure. |
-| `v1_folders_folderid2` | Updates an existing folder using the specified `folderId` and returns a status message upon successful modification. |
-| `v1_folders_folderid_items` | Retrieves a paginated list of items within a specified folder, filtered by type, using continuation tokens for pagination. |
-| `v1_folders_move` | Moves folders to a new location using the "POST" method at the "/v1/folders/move" endpoint and returns status messages based on the operation's success or failure. |
-| `v1_folders` | Creates a new folder in the system and returns a success or error status. |
-| `v1_users_me` | Retrieves information about the currently authenticated user using the GET method at the "/v1/users/me" endpoint. |
-| `v1_users_me_profile` | Retrieves the authenticated user's profile information. |
+| `get_app_jwks` | Retrieves the JSON Web Key Set (JWKS) for a given application ID. The JWKS contains public keys essential for verifying the authenticity of JSON Web Tokens (JWTs) issued by the application, ensuring secure communication. |
+| `get_asset` | Fetches the details of a specific asset using its unique identifier. This function performs a GET request to retrieve asset data, distinguishing it from other functions that update (`v1_assets_assetid2`, `v1_assets_assetid3`) or delete (`v1_assets_assetid`) assets at the same endpoint. |
+| `post_update_asset` | Updates an asset's name and tags by its ID using an HTTP POST request. This method is distinct from the PATCH-based update function (`v1_assets_assetid2`), which performs a similar action on the same `/v1/assets/{assetId}` endpoint. |
+| `delete_asset` | Deletes a specific Canva asset identified by its unique ID. This function sends an HTTP DELETE request to the `/v1/assets/{assetId}` endpoint to permanently remove the resource, returning the API's confirmation response upon successful completion. |
+| `patch_asset` | Partially updates an asset by its ID using an HTTP PATCH request to modify specific fields like name or tags. Unlike `v1_assets_assetid3` which uses POST, this method applies incremental changes, returning the updated asset data upon completion. |
+| `upload_asset` | Uploads an asset by sending its data to the `/v1/assets/upload` endpoint. This function performs a direct, synchronous upload, returning a confirmation. It differs from `v1_asset_uploads`, which initiates an asynchronous upload job tracked by an ID. |
+| `create_asset_upload_job` | Initiates an asynchronous asset upload by creating an upload job. This method returns details, like a job ID, for subsequent steps. It differs from `v1_assets_upload`, which targets a direct, synchronous upload endpoint. |
+| `get_asset_upload_job_status` | Retrieves the status and results of an asynchronous asset upload job using its unique job ID. This allows for checking the outcome of an upload initiated by `v1_asset_uploads`, returning details on its completion and any resulting asset information. |
+| `create_autofill_job` | Initiates an autofill job to create a new design by populating a brand template with provided data. It sends a POST request with the template ID, data, and title, returning the details of the newly created job. |
+| `get_autofill_job_status` | Retrieves the status and results of an asynchronous autofill job by its unique `jobId`. This function is used to check the outcome of a template population operation initiated by the `v1_autofills` method. |
+| `list_brand_templates` | Searches for and retrieves a paginated list of brand templates. Results can be filtered by ownership and sorted by relevance, modification date, or title. A continuation token can be used to fetch subsequent pages of templates. |
+| `get_brand_template_by_id` | Retrieves the complete metadata for a specific brand template using its unique identifier. This is distinct from `v1_brand_templates`, which lists multiple templates, and `v1_brand_templates_brandtemplateid_dataset`, which gets only a template's dataset. |
+| `get_brand_template_dataset` | Retrieves the dataset for a specific brand template by its ID. The dataset defines the names and types of autofillable fields, which is essential for programmatically populating the template with data. |
+| `create_comment` | Creates a new top-level comment attached to a specific resource, such as a design. It allows for an optional assignee and a message body, sending a POST request to the `/v1/comments` endpoint and returning the details of the newly created comment. |
+| `create_comment_reply` | Creates a reply to a specific comment, identified by `commentId`. It sends a POST request with the reply's message and attachment details to the `/v1/comments/{commentId}/replies` endpoint, adding a threaded response to an existing comment. |
+| `get_design_comment` | Fetches a specific comment from a design using both the design and comment IDs. Unlike other functions that create comments or replies, this method exclusively retrieves the data for a single, existing comment by making a GET request to the API. |
+| `get_connection_keys` | Fetches a list of connection keys for the authenticated user or application from the `/v1/connect/keys` endpoint. These keys are used for establishing secure connections or integrations with the Canva API. |
+| `list_designs` | Retrieves a list of designs available to the user. Results can be filtered by a search query, ownership status, and sort order. It supports pagination for large datasets using a continuation token to fetch multiple designs. |
+| `create_design` | Creates a new design from an asset. This function sends a POST request to the `/v1/designs` endpoint with the asset ID, design type, and title, returning the data for the newly created design resource. |
+| `get_design` | Fetches the details for a single, specific design using its unique identifier. This function retrieves one design, distinguishing it from `v1_designs` which lists multiple designs and `v1_designs1` which creates a new design. |
+| `create_design_import_job` | Initiates a job to import a file (e.g., PDF, PPTX) for creating a new Canva design. This function sends a POST request to the `/v1/imports` endpoint and returns details of the created import job, including a job ID for status tracking. |
+| `get_design_import_status` | Retrieves the status and results of a specific design import job using its unique `jobId`. This function checks the outcome of an import process initiated by the `v1_imports` method, returning details about the job's progress and final state. |
+| `create_design_export` | Initiates an export job for a specified design based on its ID and format details (e.g., file type, quality). It returns the export job's details, including an ID used to track its status with `v1_exports_exportid`. |
+| `get_export_job_status` | Retrieves the status and results of a specific design export job using its unique ID. This is used to check on an export initiated by the `v1_exports` function and to obtain download links for the completed file. |
+| `get_folder_by_id` | Retrieves detailed information for a specific folder using its unique ID. This GET operation fetches folder metadata, distinguishing it from functions that delete (`v1_folders_folderid`) or update (`v1_folders_folderid2`) the same folder resource. |
+| `delete_folder` | Deletes a folder and all its contents using the folder's unique identifier. This function sends an HTTP DELETE request to the `/v1/folders/{folderId}` endpoint and returns a confirmation status upon successful deletion. |
+| `update_folder` | Updates a specific folder's properties, such as its name, using its unique ID. This function sends a PATCH request to the `/v1/folders/{folderId}` endpoint to apply partial modifications and returns the updated folder information upon success. |
+| `list_folder_items` | Lists items within a specific folder. Supports optional filtering by item type (asset, design, folder, template) and pagination using a continuation token to navigate through large result sets. |
+| `move_folder_item` | Moves an item, such as a design or another folder, from a source folder to a destination folder. It requires the unique IDs for the item, the source folder, and the target folder to perform the relocation, returning a status confirmation upon completion. |
+| `create_folder` | Creates a new folder, optionally assigning it a name and placing it within a specified parent folder. This function is distinct from others as it uses a POST request to the base `/v1/folders` endpoint, specifically for creation. |
+| `get_current_user` | Retrieves core information for the currently authenticated user, such as ID and team details. This function is distinct from `v1_users_me_profile`, which fetches more specific profile data like the user's display name and profile picture. |
+| `get_current_user_profile` | Fetches detailed profile information for the currently authenticated user. This method is distinct from `v1_users_me`, which retrieves general user account information rather than specific profile details like display name or avatar. |

universal_mcp/applications/clickup/README.md

@@ -1,10 +1,10 @@
-# Clickup MCP Server
+# ClickupApp MCP Server
 
-An MCP Server for the Clickup API.
+An MCP Server for the ClickupApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Clickup API.
+This is automatically generated from OpenAPI schema for the ClickupApp API.
 
 
 | Tool | Description |
@@ -60,7 +60,7 @@ This is automatically generated from OpenAPI schema for the Clickup API.
 | `lists_get_folderless` | Retrieves all lists within the specified space that are not associated with a folder. |
 | `lists_create_folderless_list` | Creates a new list within a specified space without associating it with a folder. |
 | `lists_get_list_details` | Retrieves the details of a specific list by its unique identifier. |
-| `lists_update_list_info_due_date_priority_assignee_color` | Updates the information of a list, including name, content, due date, priority, assignee, status, and color attributes. |
+| `lists_update_list` | Updates the information of a list, including name, content, due date, priority, assignee, status, and color attributes. |
 | `lists_remove_list` | Removes a list with the specified list ID via an HTTP DELETE request and returns the API response as a dictionary. |
 | `lists_add_task_to_list` | Adds a task to a specified list. |
 | `lists_remove_task_from_list` | Removes a specific task from a list by sending a DELETE request to the appropriate API endpoint. |

universal_mcp/applications/contentful/README.md

@@ -13,5 +13,4 @@ This is automatically generated from OpenAPI schema for the ContentfulApp API.
 | `get_entries_collection` | Fetches a collection of entries of a specified content type. |
 | `get_asset` | Fetches a single asset by its ID. |
 | `get_assets_collection` | Fetches a collection of assets. |
-| `execute_graphql_query` | Executes an arbitrary GraphQL query. |
-| `execute_graphql_mutation` | Executes an arbitrary GraphQL mutation. |
+| `execute_graphql_query` | Executes an arbitrary GraphQL query against the configured Contentful space/environment. |