semvec/pypi-packages huggingface dataset:
cz-mono 0.1.0
A Mono version scheme plugin for Commitizen
Requires Python: >=3.10

# [Commitizen](https://github.com/commitizen-tools/commitizen) Mono Versioning Plugin

## Overview

This is a dead simple [Commitizen](https://github.com/commitizen-tools/commitizen) plugin that provides
mono versioning scheme.

If you're just using a single number as your version (e.g., `1`, `2`, `3`), this plugin will help you manage version
bumps and create changelogs accordingly.

## Installation

Using uv (recommended):

```shell
uv add cz-mono
```

or

Using pip:

```shell
pip install cz-mono
```

## Usage

In your `pyproject.toml`, set the `version_scheme` field to `mono` under the `[tool.commitizen]` section:

```toml
[tool.commitizen]
version_scheme = "mono"
```

Now, when you run `cz bump` or `cz ch`, it will use the mono versioning scheme to determine the next version.
iflow-mcp_dataring-engineering_mcp_server_trino 0.1.1
A Model Context Protocol (MCP) server that enables secure interaction with Trino. This server allows AI assistants to list tables, read data, and execute SQL queries through a controlled interface, making data exploration and analysis safer and more structured.
Requires Python: >=3.11

# Trino MCP Server

This repository provides an MCP (Model-Control-Protocol) server that allows you to list and query tables via Trino using Python.

## Overview

- MCP: MCP is a protocol for bridging AI models, data, and tools. This example MCP server provides:
    - A list of Trino tables as MCP resources
    - Ability to read table contents through MCP
    - A tool for executing arbitrary SQL queries against Trino
- Trino: A fast, distributed SQL query engine for big data analytics. This server makes use of Trino’s Python client (trino.dbapi) to connect to a Trino host, catalog, and schema.

## Requirements

- Python 3.9+ (or a version compatible with mcp, trino, and asyncio)
- trino (the Python driver for Trino)
- mcp (the Model-Control-Protocol Python library)

## Configuration

The server reads Trino connection details from environment variables:

| Variable         | Description                                                          | Default     |
|------------------|----------------------------------------------------------------------|------------|
| `TRINO_HOST`     | Trino server hostname or IP                                          | `localhost`|
| `TRINO_PORT`     | Trino server port                                                    | `8080`     |
| `TRINO_USER`     | Trino user name                                                      | *required* |
| `TRINO_PASSWORD` | Trino password (optional, depends on your authentication setup)      | (empty)    |
| `TRINO_CATALOG`  | Default catalog to use (e.g., `hive`, `tpch`, `postgresql`, etc.)    | *required* |
| `TRINO_SCHEMA`   | Default schema to use (e.g., `default`, `public`, etc.)             | *required* |

## Usage

``` json
{
  "mcpServers": {
    "trino": {
      "command": "uv",
      "args": [
        "--directory", 
        "<path_to_mcp_server_trino>",
        "run",
        "mcp_server_trino"
      ],
      "env": {
        "TRINO_HOST": "<host>",
        "TRINO_PORT": "<port>",
        "TRINO_USER": "<user>",
        "TRINO_PASSWORD": "<password>",
        "TRINO_CATALOG": "<catalog>",
        "TRINO_SCHEMA": "<schema>"
      }
    }
  }
}

```