Skip to main content
Glama
README.md
# wmilvus-mcp

<p align="center">
    <a href="https://pypi.org/project/wmilvus-mcp/">
        <img src="https://img.shields.io/pypi/v/wmilvus-mcp.svg" alt="PyPI version">
    </a>
    <a href="https://pypi.org/project/wmilvus-mcp/">
        <img src="https://img.shields.io/pypi/pyversions/wmilvus-mcp.svg" alt="Python versions">
    </a>
    <a href="https://github.com/wisrovi/wmilvus-mcp/blob/main/LICENSE">
        <img src="https://img.shields.io/pypi/l/wmilvus-mcp.svg" alt="License">
    </a>
</p>

**wmilvus-mcp** is the Model Context Protocol (MCP) server for architecting, validating, scaffolding, and generating code for **WMilvus** vector database applications.

## Technical Stack

| Component | Technology |
|-----------|------------|
| Language | Python 3.10+ |
| Protocol Core | Model Context Protocol (MCP) |
| Server Framework | FastMCP (mcp.server.fastmcp) |
| Validation Engine | AST & Pydantic 2.x |
| Testing Framework | pytest, pytest-cov |
| Code Formatting | ruff |

## Features & Exposed MCP Tools

1. `validate_model_schema` — Validate Pydantic models for WMilvus compatibility.
2. `search_wmilvus_pattern` — Search production-ready WMilvus design patterns.
3. `deploy_wmilvus_scaffolding` — Deploy a complete WMilvus vector application structure.
4. `get_wmilvus_architect_blueprints` — Runnable code reference for CRUD, vector search, range search, batch ingestion, async client, and ghost audit log.
5. `get_wmilvus_architect_manual` — Comprehensive architectural manual for Milvus memory and vector indexing.
6. `generate_wmilvus_crud` — Generate ready-to-run CRUD code for WMilvus models.
7. `generate_mcp_client_config` — Generate JSON configuration snippet for Anthropic Claude, Antigravity, or Cursor.

## Quick Start

Run the server via stdio:

```bash
pip install -e .
wmilvus-mcp --start
```

## Running Tests

Execute tests inside an isolated Docker container:

```bash
./run_tests_docker.sh
```

Calculate code coverage:

```bash
./run_coverage.sh
```

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but the reference-oriented tools (get_wmilvus_architect_blueprints, get_wmilvus_architect_manual, search_wmilvus_pattern) have some conceptual overlap. Descriptions help distinguish code examples, conceptual manual, and searchable patterns, so an agent can mostly select correctly.

Naming Consistency5/5

All tool names use consistent snake_case and follow a verb_noun pattern (validate_, search_, deploy_, get_, generate_). The inclusion of 'wmilvus' varies slightly but does not break predictability.

Tool Count5/5

Seven tools is well-scoped for a specialized WMilvus development-assistant server. Each tool appears to earn its place without excessive redundancy or missing obvious operations.

Completeness4/5

The surface covers validation, search, scaffolding, reference documentation, code generation, and MCP client configuration for WMilvus development. Minor gaps may exist, such as runtime vector operations, but the stated development-assistant purpose is largely covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues