ChromaDB-powered local indexing support for Cursor, exposed as an MCP server
{
"mcpServers": {
"cursor-local-indexing": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
ChromaDB-powered local indexing support for Cursor, exposed as an MCP server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 384 days ago. 36 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Manage Supabase projects — databases, auth, storage, and edge functions
Query and manage PostgreSQL databases directly from AI assistants
An official Qdrant Model Context Protocol (MCP) server implementation
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
MCP Security Weekly
Get CVE alerts and security updates for Cursor Local Indexing and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An experimental Python-based server that locally indexes codebases using ChromaDB and provides a semantic search tool via an MCP (Model Context Protocol) server for tools like Cursor.
Clone and enter the repository:
git clone <repository-url>
cd cursor-local-indexing
Create a .env file by copying .env.example:
cp .env.example .env
Configure your .env file:
PROJECTS_ROOT=~/your/projects/root # Path to your projects directory
FOLDERS_TO_INDEX=project1,project2 # Comma-separated list of folders to index
Example:
PROJECTS_ROOT=~/projects
FOLDERS_TO_INDEX=project1,project2
Start the indexing server:
docker-compose up -d
Configure Cursor to use the local search server:
Create or edit ~/.cursor/mcp.json:
{
"mcpServers": {
"workspace-code-search": {
"url": "http://localhost:8978/sse"
}
}
}
Restart Cursor IDE to apply the changes.
The server will start indexing your specified projects, and you'll be able to use semantic code search within Cursor when those projects are active.
Create a .cursorrules file and add the following:
<instructions>
For any request, use the @search_code tool to check what the code does.
Prefer that first before resorting to command line grepping etc.
</instructions>