Summary
Retrieval only: the corpus has to exist in Supavec before either call has anything to return.
There is no upload path in the tool surface — list-user-files reports what is already there and fetch-embeddings queries one file at a time by file_id — so ingestion stays inside Supavec itself. That makes this a tightly scoped reader over a corpus someone else maintains, and it means a session that cannot find the file it wants has no way from here to add it.
What it is
A server over a Supavec account, exposing the uploaded file list and embedding retrieval against one file at a time.
What you get
- fetch-embeddings retrieves embeddings for a single file, addressed by file_id, against a query.
- list-user-files returns the files uploaded to Supavec for the current user, paged with limit, offset and order_dir.
Requirements
A Supavec account with an API key, supplied as SUPAVEC_API_KEY.
Setup effort
One command plus a key — npx @supavec/mcp-server --api-key your_api_key, then supply credentials