wmilvus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_model_schemaC | Validate a Pydantic model definition for WMilvus vector storage compatibility. |
| search_wmilvus_patternC | Search for production-ready WMilvus architectural patterns in the catalog. |
| deploy_wmilvus_scaffoldingC | Deploys a professional WMilvus vector application project structure. |
| get_wmilvus_architect_blueprintsB | Complete reference with runnable code examples for every WMilvus feature. |
| get_wmilvus_architect_manualC | Architectural manual explaining vector indexing, Milvus memory management, and forensic audit logs. |
| generate_wmilvus_crudC | Generate ready-to-run WMilvus CRUD code snippet. |
| generate_mcp_client_configC | Generate MCP Client JSON configuration snippet for Anthropic Claude, Antigravity, or Cursor. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.