Knuckles-Team/vector-mcp

Action-routed MCP and agent interfaces for governed vector collection management and retrieval.
The native default is medulla. Secure opt-in providers cover PostgreSQL/pgvector,
Qdrant, and MongoDB Atlas.
## Governed capability
MCP tools: vectorcollectionmanagement and vectorsearch
Skill provider: the consolidated vector-mcp-operations workflow
Ontology provider: the packaged vector retrieval ontology
Source connector provider: a read-only vector collection inventory preset
Runtime configuration: AgentConfig, environment variables, and secret references
Privacy posture: no checked-in endpoints, credentials, personal identity, or host paths
## Install
Use the smallest extra set required by the deployment:
bash
uvx --from 'vector-mcp[mcp]' vector-mcp
The runtime requires scion-sdk>=0.2.0 and its self-contained full
medulla engine contract. A bare numeric-only or partial engine profile is not a
supported deployment.
For a selected storage provider:
bash
uv add 'vector-mcp[postgres]'
uv add 'vector-mcp[qdrant]'
uv add 'vector-mcp[mongodb]'
The all extra enables every supported optional provider plus the agent, Langfuse, and
Logfire runtimes. Production images should install only the providers they operate.
## MCP configuration
The package includes a neutral agent-start configuration containing only the command,
condensed tool mode, and tool toggles. Runtime values are inherited from AgentConfig or
injected by the operator. Detailed instructions on how to use the underlying API wrappers,
extended schema bindings, and developer SDK references are maintained in
docs/index.md.
## MCP
This server use dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.
### Available MCP Tools
Auto-generated from the live MCP server — do not edit by hand.
#### Condensed action-routed tools (MCPTOOLMODE=condensed)
| MCP Tool | Toggle Env Var | Description |
| vectorcollectionmanagement | COLLECTIONMANAGEMENTTOOL | Manage collection management operations. |
| vectorsearch | SEARCHTOOL | Manage search operations. |
2 action-routed tool(s) · 0 verbose 1:1 tool(s). Each is enabled unless its TOOL toggle is set false; MCPTOOLMODE selects the surface (intent default — the six verb-tools, granular set loaded on demand · condensed action-routed · verbose 1:1 · both). Auto-generated — do not edit.
Detailed tool schemas, parameter shapes, and validation constraints are preserved in the usage guide.
### Dynamic Tool Selection & Visibility
This MCP server supports dynamic toolset selection and visibility filtering at runtime. This allows the operator to restrict the set of exposed tools to prevent blowing up the LLM's context window.
The operator can configure tool filtering via multiple input channels:
CLI Arguments: Pass --tools or --toolsets (or their disabled counterparts --disabled-tools and --disabled-toolsets) during startup.
Environment Variables: Define standard environment variables:
MCPENABLEDTOOLS / MCPDISABLEDTOOLS
MCPENABLEDTAGS / MCPDISABLEDTAGS
HTTP SSE Request Headers: Pass custom headers during transport initialization:
x-mcp-enabled-tools / x-mcp-disabled-tools
x-mcp-enabled-tags / x-mcp-disabled-tags