Lucidworks MCP

​

Benefits

• Self-service integration: Configure Claude to access Lucidworks Search data without custom API development.
• Enterprise security: Leverages Lucidworks Search’s existing security controls, including field-level security, role-based access, and audit logging.
• Multi-tenant architecture: Support multiple use cases with different data access patterns using query profiles and collection isolation.
• Query pipeline integration: Claude benefits from your custom query pipelines, ML models, and relevance tuning.
• Extensible tool framework: Add custom tools programmatically that automatically become available to Claude.

​

Supported AI clients

• Claude Code - Command-line AI agent with built-in MCP support (recommended for easiest setup).
• Claude Desktop - Desktop application for conversational AI.

​

MCP server setup

​

Before you begin

• Lucidworks Search 5.17 or later with the MCP Server service running
• A Lucidworks Search app configured with indexed content
• A query profile created for MCP access
• Claude Code (recommended) or Claude Desktop

​

Set up authentication

POST,GET:/mcp

GET:/query-profiles/search-experiences
GET:/collections/*/schema/fields
GET:/collections/*/schema/dynamicfields
GET:/apps/*/query-profiles/**
GET:/apps/*/query/**

GET:/query-profiles/search-experiences
GET:/collections/<collection-name>/schema/fields
GET:/collections/<collection-name>/schema/dynamicfields
GET:/apps/<app-name>/query-profiles/<query-profile-id>
GET:/apps/<app-name>/query/<query-profile-id>

​

Configure the MCP server

1

Open the query profile

In Lucidworks Search, navigate to Querying > Query Profiles and select the query profile you want to make available as an MCP search experience.

2

Enable the search experience

Scroll to the MCP Search Experience section and select the Enable for MCP Processing checkbox:

3

Configure search experience metadata

Fill in the required fields:

• Name: Display name for this search experience (required)
• Description: Description that helps Claude understand when to use this search experience (required)
• Content Field: Optional field name to use as the document description source

The form validates that required fields are populated before allowing you to save.

How document descriptions are determined:When Content Field is specified:

• If the field contains a value in the Query Profile response, that value is used.
• If the field is empty, the MCP server falls back to checking default fields like body_t.

When Content Field is empty:

• The MCP server checks default fields like body_t to generate document descriptions.

4

Save the query profile

Click Save to apply your changes. The search experience is immediately available to MCP clients.

​

Connect an AI agent

claude mcp add --transport http fusion https://FUSION_HOST/mcp --header "x-api-key: FUSION_API_KEY"

claude mcp list

​

Test the connection

​

Search with MCP

​

List search experiences

• You need to see what search experiences are available.
• You need to determine which search experience to use for a specific query.
• You need to help users who don’t know what they can search for.

​

Search documents

​

Get a document

​

Get the field schema

• You need to discover what fields exist within a particular search experience.
• You need to determine which fields can be used for sorting.
• You need to determine which fields can be used for filtering.
• You need to display field information to users with human-readable names.

​

How the tools work together

1. When a user asks a question without specifying a search experience, Claude calls list_search_experiences to discover available options.
2. Claude analyzes the search experiences and matches them to the user’s query intent.
3. Claude calls search_documents with the appropriate search experience.
4. Claude returns results to the user.

1. Calls list_search_experiences and receives the following data:
   {
     "searchExperiences": [
       {"name": "Product Catalog", "description": "Outdoor gear and sporting equipment"},
       {"name": "Support Articles", "description": "Product guides, warranties, and care instructions"}
     ]
   }
   
2. Identifies the “Product Catalog” search experience as the one that best matches the prompt.
3. Calls search_documents with searchExperience: "Product Catalog" and the user’s query.
4. Returns the product results.

​

Example use cases

Find all technical documentation about JWT authentication from the past six months

{
  "method": "tools/call",
  "params": {
    "name": "search_documents",
    "arguments": {
      "searchExperience": "technical_docs",
      "query": "JWT authentication",
      "filters": [
        {"field": "doc_type", "operator": "equals", "value": "technical"},
        {"field": "date", "operator": "relative_date_range", "timeUnit": "MONTHS", "timeValue": 6}
      ],
      "rows": 10
    }
  }
}

I found eight technical documents about JWT authentication from the past six months:

1. **JWT Authentication Best Practices 2026** (Jan 15, 2026)
   This guide covers modern JWT authentication patterns including...
   [View Document](https://docs.company.com/security/jwt-guide)

2. **Implementing JWT in Node.js** (Feb 2, 2026)
   Step-by-step tutorial for implementing JWT tokens...
   [View Document](...)

認証に関する最新のドキュメントを教えてください

{
  "jsonrpc": "2.0",
  "id": 10,
  "result": {
    "content": [],
    "isError": false,
    "structuredContent": {
      "summary": "Found 3 documents for query: search",
      "documents": [
        {
          "id": "doc-123",
          "title": "Introduction to Search Analytics",
          "url": "https://docs.example.com/search-analytics",
          "moreLikeThis": [
            {
              "id": "doc-456",
              "title": "Query Performance Optimization"
            },
            {
              "id": "doc-789",
              "title": "Relevance Tuning Best Practices"
            },
            {
              "id": "doc-321",
              "title": "Understanding Search Metrics"
            }
          ],
          "highlighting": {
            "title_t": ["Introduction to <em>Search</em> Analytics"],
            "description_t": ["Learn how to analyze and improve your <em>search</em> performance"]
          }
        }
      ],
      "searchExperiences": [],
      "querySpellcheckSuggestions": []
    }
  }
}

​

Example multi-tenant configurations

claude mcp add --transport http fusion-employee \
    https://FUSION_HOST/mcp \
    --header "x-api-key: EMPLOYEE_KEY"

claude mcp add --transport http fusion-contractor \
    https://FUSION_HOST/mcp \
    --header "x-api-key: CONTRACTOR_KEY"

{
  "mcpServers": {
    "fusion-public": {
      "type": "http",
      "url": "https://FUSION_HOST/mcp",
      "headers": {
        "x-api-key": "PUBLIC_READONLY_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "fusion-internal": {
      "type": "http",
      "url": "https://FUSION_HOST/mcp",
      "headers": {
        "x-api-key": "EMPLOYEE_KEY"
      }
    }
  }
}

​

Troubleshooting

2. Confirm that the Lucidworks Search version is 5.17 or later:
 ```bash wrap
 curl https://FUSION_HOST:FUSION_PORT/api/admin/version

claude mcp add --transport http fusion https://FUSION_HOST/mcp --header "x-api-key: API_KEY"

claude mcp list

fusion - https://FUSION_HOST/mcp (http)

{
  "summary": "Search experience is not configured",
  "documents": [],
  "searchExperiences": [...]
}

{
  "content": [{"type": "text", "text": "Error: Unable to process request"}],
  "isError": true
}

{
  "summary": "Found 0 documents",
  "documents": [],
  "searchExperiences": []
}

​

Monitoring MCP usage