Skip to main content
Glama
Knuckles-Team

vector-mcp

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHUNK_SIZEYesThe chunk size for document processing.
VECTOR_URLYesThe URL of the vector database.
VECTOR_API_KEYYesThe API key for the vector database.
EMBEDDING_MODEL_IDYesThe embedding model ID.

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vector_collection_managementC

Manage collection management operations.

Actions:

  • 'create_collection': Creates a new collection or retrieves an existing one in the vector database.

  • 'add_documents': Adds documents to an existing collection in the vector database.

  • 'delete_collection': Deletes a collection from the vector database.

  • 'list_collections': Lists all collections in the vector database.

vector_searchA

Manage search operations.

Actions:

  • 'semantic_search': Retrieves and gathers related knowledge from the vector database instance using the question variable.

  • 'lexical_search': This is a lexical or term based search that retrieves and gathers related knowledge from the database instance using the question variable via BM25.

  • 'search': Performs a hybrid search combining semantic (vector) and lexical (BM25) methods.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: collection management (CRUD operations on collections) and search (semantic, lexical, hybrid). There is no overlap, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent 'vector_' prefix pattern with descriptive suffixes ('collection_management', 'search'). Internal action names are uniformly snake_case, maintaining predictability.

Tool Count3/5

With only 2 tools, the server feels somewhat thin for a vector database MCP. While each tool bundles multiple actions, a few more tools (e.g., separate tools for document operations) would improve organization.

Completeness2/5

The server lacks essential operations such as updating or deleting documents, retrieving collection details, or managing metadata. These gaps would likely cause agent failures in typical workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources