zvec-mcp-server 0.1.0__tar.gz

zvec_mcp_server-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,52 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          version: "latest"
+
+      - name: Install dependencies
+        run: |
+          uv venv
+          uv pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: |
+          uv run ruff check src/ tests/
+          uv run ruff format --check src/ tests/
+
+      - name: Run tests
+        run: |
+          uv run pytest tests/ -v --tb=short
+
+      - name: Upload coverage to Codecov
+        if: matrix.os == 'ubuntu-latest' && matrix.python-version == '3.11'
+        uses: codecov/codecov-action@v4
+        with:
+          fail_ci_if_error: false
+          verbose: true
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

zvec_mcp_server-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,49 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          version: "latest"
+
+      - name: Install build dependencies
+        run: |
+          uv venv
+          uv pip install build twine
+
+      - name: Build package
+        run: |
+          uv run python -m build
+
+      - name: Check package
+        run: |
+          uv run twine check dist/*
+
+      - name: Upload to PyPI
+        if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+
+      - name: Create GitHub Release
+        if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+        uses: softprops/action-gh-release@v1
+        with:
+          generate_release_notes: true
+          draft: false
+          prerelease: false

zvec_mcp_server-0.1.0/.gitignore

@@ -0,0 +1,64 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Virtual environments
+venv/
+env/
+ENV/
+.venv/
+
+# UV
+.uv/
+uv.lock
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# Qoder / Agents
+.agents/
+.qoder/
+skills-lock.json
+
+# Temporary directories
+tmp/
+
+# Zvec data directories
+*.zvec/
+my_vectors/
+test_vectors/
+./embeddings/
+./my_collection/
+example_collection/
+test_collection/
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+
+# OS
+.DS_Store
+Thumbs.db

zvec_mcp_server-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.6.9
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

zvec_mcp_server-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+the issue tracker.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

zvec_mcp_server-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,212 @@
+# Contributing to Zvec MCP Server
+
+Thank you for your interest in contributing to Zvec MCP Server! This document provides guidelines and instructions for contributing.
+
+## Development Setup
+
+### Prerequisites
+
+- Python 3.10 - 3.12
+- [uv](https://github.com/astral-sh/uv) (recommended) or pip
+
+### Setup Steps
+
+1. Fork the repository and clone your fork:
+```bash
+git clone https://github.com/yourusername/zvec-mcp-server.git
+cd zvec-mcp-server
+```
+
+2. Create a virtual environment and install dependencies:
+```bash
+# Using uv (recommended)
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+uv pip install -e ".[dev]"
+
+# Or using pip
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+3. Verify the setup by running tests:
+```bash
+pytest tests/ -v
+```
+
+## Development Workflow
+
+### Code Style
+
+We use [Ruff](https://docs.astral.sh/ruff/) for linting and formatting:
+
+```bash
+# Check code style
+ruff check src/ tests/
+
+# Format code
+ruff format src/ tests/
+
+# Fix auto-fixable issues
+ruff check --fix src/ tests/
+```
+
+### Running Tests
+
+```bash
+# Run all tests
+pytest tests/ -v
+
+# Run specific test file
+pytest tests/test_server.py -v
+
+# Run with coverage
+pytest tests/ --cov=zvec_mcp --cov-report=html
+
+# Run specific test class
+pytest tests/test_server.py::TestMultiVectorQuery -v
+```
+
+### Testing with MCP Inspector
+
+```bash
+# Start the MCP Inspector
+npx @modelcontextprotocol/inspector python -m zvec_mcp
+```
+
+## Submitting Changes
+
+### Pull Request Process
+
+1. **Create a branch** for your changes:
+   ```bash
+   git checkout -b feature/your-feature-name
+   # or
+   git checkout -b fix/issue-description
+   ```
+
+2. **Make your changes** following our coding standards
+
+3. **Add tests** for new functionality
+
+4. **Ensure all tests pass**:
+   ```bash
+   pytest tests/ -v
+   ```
+
+5. **Update documentation** if needed (README.md, docstrings, etc.)
+
+6. **Commit your changes** with a clear commit message:
+   ```bash
+   git commit -m "feat: add new embedding search tool"
+   ```
+
+7. **Push to your fork**:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+8. **Open a Pull Request** against the main repository
+
+### Commit Message Convention
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `docs:` - Documentation changes
+- `style:` - Code style changes (formatting, no logic change)
+- `refactor:` - Code refactoring
+- `test:` - Test changes
+- `chore:` - Build process or auxiliary tool changes
+
+Examples:
+```
+feat: add support for sparse vector queries
+fix: handle missing collection error in search
+docs: update README with new examples
+```
+
+## Code Guidelines
+
+### Python Style
+
+- Follow PEP 8 guidelines
+- Maximum line length: 100 characters
+- Use type hints where appropriate
+- Write docstrings for all public functions and classes
+
+### Testing Guidelines
+
+- Write tests for all new functionality
+- Use pytest fixtures for setup/teardown
+- Use `pytest-asyncio` for async tests
+- Ensure tests are isolated and don't depend on external state
+
+### MCP Tool Design
+
+When adding new MCP tools:
+
+1. Define input schema in `schemas.py` using Pydantic models
+2. Implement the tool in `server.py` with proper annotations
+3. Add comprehensive tests in `tests/test_server.py`
+4. Update README.md with usage examples
+
+Example tool structure:
+```python
+@mcp.tool(
+    name="tool_name",
+    annotations={
+        "title": "Human Readable Title",
+        "readOnlyHint": True/False,
+        "destructiveHint": True/False,
+        "idempotentHint": True/False,
+        "openWorldHint": True/False,
+    }
+)
+async def tool_name(params: ToolInput) -> str:
+    """
+    Clear description of what the tool does.
+    
+    Args:
+        params (ToolInput): Description of parameters
+    
+    Returns:
+        str: Description of return value
+    """
+    try:
+        # Implementation
+        return result
+    except Exception as e:
+        return handle_error(e)
+```
+
+## Reporting Issues
+
+### Bug Reports
+
+When reporting bugs, please include:
+
+- Python version
+- Operating system
+- Steps to reproduce
+- Expected behavior
+- Actual behavior
+- Error messages and stack traces
+
+### Feature Requests
+
+For feature requests, please describe:
+
+- The use case
+- Proposed solution
+- Alternatives considered
+
+## Questions?
+
+Feel free to open an issue for questions or join discussions in existing issues.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the Apache 2.0 License.