Supavec MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-embeddingsC | Fetch embeddings for a file by ID and query |
| list-user-filesB | List all files uploaded to Supavec for the current user |
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 2 tools
The two tools have completely distinct purposes: one fetches embeddings for a specific file, while the other lists all user files. There is no overlap or ambiguity between these operations, making it clear when to use each tool.
Both tools use a verb_noun pattern (fetch-embeddings, list-user-files), which is consistent and readable. The minor deviation is the use of hyphens instead of underscores, but this is a consistent stylistic choice across both tools.
With only 2 tools, the server feels thin for a Supavec MCP Server, which likely involves file and embedding management. Key operations like uploading files, deleting files, or managing embeddings beyond fetching are missing, making the scope incomplete.
The toolset is severely incomplete for file and embedding management. There are no tools for uploading files, deleting files, updating embeddings, or other CRUD operations, leaving significant gaps that will hinder agent workflows in this domain.