VecFS
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode | 3000 |
| VECFS_FILE | No | Path to the vector storage file | ./vecfs-data.jsonl |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search the vector space using a sparse or dense vector. |
| memorizeA | Store a new entry in the vector space. Updates the entry if the ID already exists. |
| feedbackC | Record feedback for a specific memory entry. |
| deleteB | Delete an entry from the vector space by its unique ID. |
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 4 tools
Each tool has a unique purpose: delete removes by ID, feedback records feedback, memorize stores/updates, and search queries by vector. There is no overlap in functionality.
All tool names are lowercase verbs (delete, feedback, memorize, search), following a consistent single-word verb naming pattern.
4 tools is perfectly scoped for a vector memory server, covering core operations (create/update, read by search, delete) plus feedback.
Covers main operations but lacks a direct retrieval tool for entries by ID; the search tool only works with vectors, so viewing a specific entry by ID is not possible.