A
licenseNot graded
qualityC
maintenanceLocal MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.
105
4
MIT
Vectr
by swapnanil
Related Servers
Alternatives to Vectr
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives AI coding assistants persistent project memory and semantic code search, running fully locally with no API keys required.MIT
- AlicenseNot gradedqualityDmaintenancePersistent memory for AI coding agents. Builds semantic memory from git history and codebase, searchable via MCP tools.122MIT
- AlicenseAqualityAmaintenanceA fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.169913MIT
- AlicenseNot gradedqualityDmaintenanceGives AI coding assistants cross-session persistent memory with semantic search and task management, fully local.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server with local vector search for your codebase. Smart indexing, semantic search, Git history — all offline.749MIT
TDQS
A4.2/5.0
Scored across 23 tools
Disambiguation4/5
The code navigation tools are strongly differentiated with explicit NOT-when guidance, and the search/locate/trace/fetch split is very clear. The main ambiguity risk sits in the note lifecycle cluster—forget, revoke, supersede, and reinstate have subtle boundaries that require reading the descriptions carefully.
Naming Consistency4/5
All tools share the vectr_ prefix and snake_case convention, making the family instantly recognizable. The style is not perfectly uniform—most are simple verbs (recall, locate, remember), but a few are noun-led or compound forms (map_save, snapshot_list, evict_hint).
Tool Count3/5
23 tools sits in the heavy range and would feel dense at first impression. Several note-lifecycle operations like pin, anchor, unanchor, promote, revoke, reinstate, and supersede are narrow enough that they could plausibly be consolidated, even though each has a distinct purpose.
Completeness5/5
The set covers its domain thoroughly: codebase discovery via map, search, locate, trace, fetch, and dynamic trace ingestion, plus a full persistent-note lifecycle with create, recall, delete, supersede, revoke, snapshot, pin, and anchoring. There are no obvious dead ends for the stated purpose, and edge cases like staleness detection are explicitly handled.
Maintenance
ActivityActive
ResponsivenessNo issues