1. Conduid
  2. Developer Tools
  3. Cursor Local Indexing
MCP server · Developer Tools

Cursor Local Indexing

ChromaDB-powered local indexing support for Cursor, exposed as an MCP server

Unclaimed last commit a year ago devtools
46Fair

Scored 5 months ago · breakdown

About Cursor Local Indexing

Cursor Local Indexing is an MCP server published by LuotoCompany in the Developer Tools category: chromaDB-powered local indexing support for Cursor, exposed as an MCP server.

The repository has 33 stars and 11 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/LuotoCompany/cursor-local-indexing

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Cursor Local Indexing

Powered by Claude · Grounded in docs

I know everything about Cursor Local Indexing. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

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!

README fetched from the repository 5 days ago. The original is authoritative.

Questions

About Cursor Local Indexing

How do I install Cursor Local Indexing?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Cursor Local Indexing safe to use with an AI agent?

Its trust score is 46 out of 100 (fair). It passes 2 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Cursor Local Indexing still maintained?

The last commit was a year ago and 7 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.