Skip to main content
Glama
QkartBismuth

Bismut Vector MCP

by QkartBismuth

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BISMUT_API_KEYNoAPI key for a cloud (OpenAI-compatible) embedding endpoint
BISMUT_DB_PATHNoSQLite database file./.bismut/vectors.db
BISMUT_API_BASENoBase URL for an OpenAI-compatible embedding endpoint (Ollama, LM Studio, vLLM)https://api.openai.com/v1
BISMUT_CACHE_DIRNoModel download cache directory<db dir>/cache
BISMUT_LOG_LEVELNoLog level: silent, error, warn, info, debug, or traceinfo
BISMUT_BATCH_SIZENoEmbeddings per forward pass16
BISMUT_COLLECTIONNoDefault collection namedefault
BISMUT_EMBED_DTYPENoEmbedding dtype: q8, fp16, fp32, or quantizedq8
BISMUT_EMBED_MODELNoAny transformers.js modelXenova/paraphrase-multilingual-MiniLM-L12-v2
BISMUT_CHUNK_TOKENSNoTarget chunk size320
BISMUT_EMBED_DEVICENoEmbedding device: cpu, gpu, or autocpu
BISMUT_CHUNK_OVERLAPNoOverlap between chunks60
BISMUT_EMBED_PROVIDERNoEmbedding provider: local or openailocal
BISMUT_MAX_FILE_BYTESNoSkip files larger than this1048576

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
index_pathsA

Index files or directories into a vector collection for semantic search. Safe to re-run: files whose content hash is unchanged are skipped. Honors .gitignore, skips binaries/oversized files, and uses language-aware chunking (markdown sections, code symbols, prose paragraphs).

index_textA

Index arbitrary text (notes, snippets, memory entries, error logs, user-provided context) into a collection. Use a stable uri to replace previous content for the same uri, or pass replace:false to append a new version.

searchA

Run a semantic similarity query against indexed content. Returns ranked chunks with file path, line range, score (cosine similarity, 1 = identical), and text. Supports narrowing by path prefix, exact path, language, and content kind. Increase limit or use get_context when results look truncated.

get_contextA

Return contiguous chunks around a search hit (by chunk_id or document_id + ordinal) so you can read a whole function/section instead of an isolated fragment. Use after search when a result looks cut off.

list_sourcesA

List documents already indexed in a collection, with chunk counts and sizes. Use to check what is available before searching, or to confirm an index_paths run covered what you expected.

list_collectionsA

List all vector collections with their embedding model, dimensionality, document/chunk counts, and on-disk size.

delete_sourcesA

Remove documents from a collection by document id, exact uri, or path prefix. Vectors and chunks are deleted together. This is irreversible and requires at least one selector.

drop_collectionA

Permanently delete an entire collection and all its vectors, chunks, and documents. Irreversible. Prefer delete_sources when removing only some documents.

statsA

Show database path, embedding model/provider, collection count, and totals. Useful for verifying the server is healthy and which model is active before diagnosing empty search results.

get_chunkA

Return the full untruncated text of one chunk by its id, with its document metadata.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct roles (index_paths vs index_text differ by source type, and list_sources vs list_collections differ by resource). The only mild overlap is between get_context and get_chunk, which both retrieve fuller content, though their descriptions distinguish fragment-level vs surrounding-context use.

Naming Consistency4/5

Nearly all names follow a verb_noun pattern (list_collections, index_paths, delete_sources, drop_collection, get_chunk). Minor deviations are the bare single-word tools `search` and `stats`, but the overall convention is readable and predictable.

Tool Count5/5

Ten tools is well within the ideal range and each one maps to a distinct stage of the index/search/retrieve lifecycle. No tool feels redundant or superfluous.

Completeness4/5

The surface covers the full lifecycle: indexing (paths/text), discovery (collections/sources), search, context retrieval (get_context/get_chunk), and deletion (delete_sources/drop_collection) plus health via stats. The main gap is an explicit create_collection or metadata-update operation, but these are likely handled implicitly by indexing.

Maintenance

ActivityMaintained
ResponsivenessNo issues