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
- 876
- 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
No install command stated in the README — see repo.
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.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
No individual tool names were confirmed in the source material. Check the repository for its current tool list.
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
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
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
