1. Conduid
  2. Search
  3. Lucene Net
MCP server · Search

Lucene Net

An MCP server for full-text search using Lucene.NET

Unclaimed search
34Low

Scored 7 months ago · breakdown

About Lucene Net

Lucene Net is an MCP server in the Search category: an MCP server for full-text search using Lucene.NET.

Install

From source
git clone https://github.com/breitreiter/mcp-lucene-net

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 Lucene Net

Powered by Claude · Grounded in docs

I know everything about Lucene Net. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

MCP Lucene.NET

A Model Context Protocol (MCP) server for full-text search using Lucene.NET with document chunking support.

Overview

This project consists of two components:

  • /server - MCP server that provides search functionality over a Lucene.NET index
  • /idx - CLI tool for indexing documents (text files, PDFs) into Lucene.NET

Quick Start

1. Index Documents

cd idx
dotnet run -- init -i ./lucene-index
dotnet run -- add -d "manual" -t "User Manual" -f "./manual.pdf"
dotnet run -- add -d "policy" -t "Privacy Policy" -c "Our privacy policy..."

2. Start MCP Server

cd server
dotnet run ./lucene-index

3. Search Documents

The server exposes a Search tool that returns JSON with relevant document chunks.

MCP Configuration

To configure the server in Claude Desktop or other MCP clients, add this to your MCP configuration:

{
  "mcpServers": {
    "lucene-search": {
      "command": "/path/to/mcp-lucene-net/server/bin/Release/net8.0/server",
      "args": [
        "/path/to/your/lucene-index"
      ],
      "env": {}
    }
  }
}

Replace /path/to/mcp-lucene-net/server/bin/Release/net8.0/server with the actual path to your compiled server binary and /path/to/your/lucene-index with the path to your Lucene index directory.

Document Chunking

Documents are automatically split into ~250 word chunks with 40 word overlap to optimize search relevance and LLM context usage. Each chunk includes:

  • id: Unique chunk identifier (e.g., "manual-chunk-001")
  • title: Descriptive title with part number
  • content: ~250 words of text
  • source_document: Original document ID
  • chunk_index: Sequential chunk number

CLI Commands

# Initialize new index
idx init -i ./lucene-index

# Add single document
idx add -d "doc1" -t "Title" -c "Text content"
idx add -d "doc2" -t "Title" -f "./document.pdf"

# Bulk add from JSON
idx bulk -i ./lucene-index -j "./documents.json"

JSON Format

[
  {
    "Id": "doc1",
    "Title": "Document Title",
    "Content": "Document content..."
  }
]

Requirements

  • .NET 8.0
  • Lucene.NET 4.8.0-beta
  • iText for PDF extraction

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Lucene Net

How do I install Lucene Net?

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

Is Lucene Net safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Lucene Net still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.