Lucene MCP Server

What does “Lucene” MCP Server do?

The MCP Lucene Server is a Java-based implementation of the Model Context Protocol (MCP) designed to provide efficient search and retrieval capabilities using Apache Lucene. Acting as an MCP-compliant server, it enables AI assistants and agents to interact with large document repositories for tasks such as full-text search, indexing, and metadata filtering. Through its RESTful API, the Lucene MCP Server allows clients to upsert (add/update), delete, list, and query documents using Lucene’s powerful query syntax. Built on Spring Boot, it is easy to deploy and can be containerized with Docker. This server is ideal for integrating advanced document search and management features into AI-driven workflows or software development pipelines.

List of Prompts

No information about prompt templates is provided in the repository.

List of Resources

No explicit MCP resources are described in the repository.

List of Tools

• Upsert Tool

  • Allows clients to add or update documents in the Lucene index through the /mcp/v1/upsert endpoint.

• Delete Tool

  • Enables deletion of documents from the Lucene index using the /mcp/v1/delete endpoint.

• List Tool

  • Retrieves a list of documents from the index via the /mcp/v1/list endpoint.

• Query Tool

  • Supports complex search queries with Lucene query syntax using the /mcp/v1/query endpoint.

• Status Tool

  • Checks the server status with the /mcp/v1/status endpoint.

Use Cases of this MCP Server

• Enterprise Document Search
  Developers can integrate the Lucene MCP Server to provide robust, scalable search capabilities over large sets of business documents, making it easy to find relevant files and records.

• Knowledge Base Augmentation
  Enhance AI assistants by allowing them to query and retrieve information from indexed company manuals, FAQs, or support tickets.

• Automated Data Ingestion and Indexing
  Streamline workflows by programmatically upserting and updating documents in the Lucene index, ensuring the search engine is always current.

• Metadata-based Filtering
  Take advantage of Lucene’s ability to filter queries based on document metadata, supporting advanced data retrieval scenarios.

• API-driven Search Integration
  Facilitate seamless access to document search and management features for other applications or agents via RESTful endpoints.

How to set it up

Windsurf

1. Ensure Java 11+ and Maven 3.6+ are installed.
2. Build the project:

   mvn clean install
   

3. Add the MCP Lucene Server to your configuration:

   {
     "mcpServers": {
       "lucene-mcp": {
         "command": "java",
         "args": ["-jar", "target/mcp-lucene-server-0.0.1-SNAPSHOT.jar"]
       }
     }
   }
   

4. Save your configuration and start Windsurf.
5. Verify the server is running at http://localhost:8080/mcp/v1/status.

Claude

1. Install Java 11+ and Maven 3.6+.
2. Build the project:

   mvn clean install
   

3. Edit your Claude configuration to include:

   {
     "mcpServers": {
       "lucene-mcp": {
         "command": "java",
         "args": ["-jar", "target/mcp-lucene-server-0.0.1-SNAPSHOT.jar"]
       }
     }
   }
   

4. Restart Claude and ensure the MCP Lucene Server is reachable.

Cursor

1. Confirm Java 11+ and Maven 3.6+ are installed.
2. Build the Lucene MCP Server:

   mvn clean install
   

3. Add to your Cursor config:

   {
     "mcpServers": {
       "lucene-mcp": {
         "command": "java",
         "args": ["-jar", "target/mcp-lucene-server-0.0.1-SNAPSHOT.jar"]
       }
     }
   }
   

4. Save and restart Cursor.
5. Test the endpoint at http://localhost:8080/mcp/v1/status.

Cline

1. Make sure Java 11+ and Maven 3.6+ are installed.
2. Build:

   mvn clean install
   

3. In your Cline configuration:

   {
     "mcpServers": {
       "lucene-mcp": {
         "command": "java",
         "args": ["-jar", "target/mcp-lucene-server-0.0.1-SNAPSHOT.jar"]
       }
     }
   }
   

4. Restart Cline and confirm the MCP server is active.

Note about securing API keys

If your setup requires securing API keys or sensitive information, use environment variables:

{
  "mcpServers": {
    "lucene-mcp": {
      "command": "java",
      "args": ["-jar", "target/mcp-lucene-server-0.0.1-SNAPSHOT.jar"],
      "env": {
        "LUCENE_API_KEY": "${LUCENE_API_KEY}"
      },
      "inputs": {
        "apiKey": "${LUCENE_API_KEY}"
      }
    }
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "lucene-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “lucene-mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Based on the available information, the MCP Lucene Server provides a strong foundation for document search and management but lacks explicit support for prompt templates, resources, roots, or sampling. It is well-documented for setup and usage as an MCP server.

Our opinion

The MCP Lucene Server is a robust, practical MCP implementation for enterprise-grade search and document management. However, the lack of prompt templates, resource definitions, and advanced MCP features like roots or sampling limits its flexibility for more complex, agentic workflows. Overall, it is a solid starting point for integrating Lucene-powered search into AI systems. MCP Score: 6/10

MCP Score