MCP ExplorerExplorer

Cursor Local Indexing

@LuotoCompanyon 9 months ago
17 MIT
FreeCommunity
AI Systems
ChromaDB-powered local indexing support for Cursor, exposed as an MCP server

Overview

What is Cursor Local Indexing

Cursor-local-indexing is an experimental server that utilizes ChromaDB to locally index codebases, enabling semantic search capabilities through an MCP server for tools like Cursor.

Use cases

Use cases for cursor-local-indexing include searching through large codebases, improving code navigation in development environments, and enhancing productivity by providing semantic context for code queries.

How to use

To use cursor-local-indexing, clone the repository, set up the environment variables in a .env file, start the indexing server using Docker, and configure Cursor to connect to the local search server. Finally, create a .cursorrules file to guide the search behavior.

Key features

Key features include local code indexing using ChromaDB, semantic search capabilities, easy setup with Docker, and integration with Cursor for enhanced code exploration.

Where to use

undefined

Content

Local Code Indexing for Cursor

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.

Setup

  1. Clone and enter the repository:

    git clone <repository-url>
    cd cursor-local-indexing
    
  2. Create a .env file by copying .env.example:

    cp .env.example .env
    
  3. 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
    
  4. Start the indexing server:

    docker-compose up -d
    
  5. Configure Cursor to use the local search server:
    Create or edit ~/.cursor/mcp.json:

    {
      "mcpServers": {
        "workspace-code-search": {
          "url": "http://localhost:8978/sse"
        }
      }
    }
  6. 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.

  1. Open a project that you configured as indexed.

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>
  1. Start using the Cursor Agent mode and see it doing local vector searches!

Tools

No tools

Comments

Recommend MCP Servers

View All MCP Servers