Server facts
VectorCode MCP Server
Project
- Author
- Davidyz
- Repository
- github.com/Davidyz/VectorCode
- License
- MIT
- Category
- Developer Tools
Tech
- Runtime / language
- pythonPython
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 875
- Last commit
- Data as of
Tags
- Code Indexing
- Embeddings
- Neovim
- Retrieval Augmented Generation
Overview
VectorCode indexes source repositories so coding assistants can receive context relevant to the project and task at hand. The README frames this around code that models may not already understand well, such as private repositories, less familiar projects, or recent changes. Retrieved project material can be injected into prompts programmatically instead of expecting a model to infer details from its training alone. The repository contains both a command-line tool and a Neovim plugin. The plugin offers APIs for building or extending AI integrations, alongside integrations with existing editor plugins. MCP interfacing is acknowledged, although the supplied README does not enumerate MCP tool names or show a server launch command.
Completed features listed in the README include file metadata, configurable chunk sizes, syntax-aware chunking using tree-sitter, respect for gitignore rules, and project-root detection through .vectorcode or .git anchors. Collection management includes viewing and deleting indexed files, while asynchronous caching and persistent-client support are also marked implemented. Authenticated remote ChromaDB support and query rewriting remain unfinished items. The project is explicitly beta and changes quickly. Its pre-1.0 versioning scheme uses minor releases for breaking changes and patch releases for compatible updates or deprecation warnings. Setup instructions are linked in separate CLI and Neovim documentation, and users are told to consult documentation matching their installed version.
Install & configure
Not stated in the README: a runnable installation or MCP launch command. Setup is delegated to separate CLI and Neovim documentation; no environment variables or MCP tool names are supplied.
Use cases
- Inject relevant repository material into coding-model prompts
- Build Neovim AI integrations using plugin APIs
- Index code with configurable syntax-aware chunks
- Inspect or remove indexed files from collections
Strengths
- Combines repository indexing with editor integration APIs
- Respects gitignore and recognizes project-root anchors
- Supports configurable syntax-aware chunking
Limitations
- Beta interfaces may change across minor releases
- Authenticated remote ChromaDB support is unfinished
- No runnable MCP launch command or named tools are stated in the README
VectorCode setup notes
- VectorCode records stdio only; confirm a network transport upstream before planning remote access.