Skip to main content
Glama
rbeg1

odigo-elastic-s2l-mcp

by rbeg1

odigo-elastic-s2l-mcp

MCP Elasticsearch Server with Semantic S2L Layer

License Python Elasticsearch MCP

Copyright 2025 Odigo SAS — Developed by Régis BEGUIN (regis.beguin@odigo.com)

A generic Model Context Protocol (MCP) server that connects LLMs to Elasticsearch, with a Semantic-to-Lexical (S2L) layer that translates technical field names into business knowledge — without hardcoding any domain logic in the server itself.


How it works

The S2L layer is a simple JSON file (field_descriptions.json) that provides:

  • Field descriptions: human-readable explanations of each Elasticsearch field

  • Business rules: mandatory filters, billing criteria, error codes, timezone handling, index patterns — anything the LLM needs to build correct queries autonomously

The LLM reads this semantic layer via get_field_descriptions() and builds Query DSL or ES|QL queries on its own. No business logic is hardcoded in the server.

LLM ──► get_field_descriptions() ──► reads business rules from JSON
LLM ──► get_mappings()           ──► reads enriched schema
LLM ──► search() / esql()        ──► executes autonomous queries

Related MCP server: Elasticsearch MCP Server

Available Tools

Tool

Description

cluster_info

Cluster info and available features (version, ES|QL support)

list_indices

List available indices

get_mappings

Index schema enriched with S2L field descriptions

get_field_descriptions

Field descriptions + business rules from field_descriptions.json

search

Query DSL search

esql

ES|QL query (Elasticsearch >= 8.11.0 only)

get_shards

Shard information


Requirements

  • Python 3.11+

  • Elasticsearch >= 8.10.4

  • Docker or Podman


Quick Start

1. Configure your S2L layer

Edit src/field_descriptions.json to describe your Elasticsearch fields and business rules:

{
  "_business_rules": {
    "_mandatory_filter": "All queries must include: { 'term': { 'status': 'active' } }",
    "_index_pattern": "Target index pattern: my_data_index_*",
    "_timezone": "Timestamps are stored in UTC."
  },
  "my_field": "Description of what this field means in your domain.",
  "my_status_field": "Status: '0' = success, '1' = failure."
}

2. Build the Docker image

chmod +x build.sh
./build.sh

Or with Podman:

CONTAINER_TOOL=podman ./build.sh

3. Configure Claude Desktop

Edit %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "elastic-s2l-mcp": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm", "--network", "host",
        "-e", "ES_URL=http://your-elasticsearch-host:9200",
        "-e", "ES_API_KEY=YOUR_API_KEY",
        "elastic-s2l-mcp:latest"
      ]
    }
  }
}

4. Or run directly with Python

pip install -r requirements.txt
ES_URL=http://localhost:9200 ES_API_KEY=YOUR_KEY python src/server.py

Environment Variables

Variable

Description

Default

ES_URL

Elasticsearch URL

http://localhost:9200

ES_API_KEY

Elasticsearch API key

(empty — no auth)

FIELD_DESCRIPTIONS_PATH

Path to the S2L JSON config file

src/field_descriptions.json


Project Structure

odigo-elastic-s2l-mcp/
├── src/
│   ├── server.py                # MCP server (generic, no business logic)
│   └── field_descriptions.json  # S2L semantic layer (your domain knowledge)
├── Dockerfile
├── requirements.txt
├── build.sh
├── lance_mcp.sh
├── export_image.sh
├── LICENSE
└── README.md

About

This project was developed as part of an R&D initiative at Odigo, a leading European cloud contact center software company.

Author: Régis BEGUIN — Revenue Assurance Engineer, Odigo
Contact: regis.beguin@odigo.com


License

Copyright 2025 Odigo SAS Developed by Régis BEGUIN (regis.beguin@odigo.com)

Licensed under the Apache License, Version 2.0.

F
license - not found
-
quality - not tested
D
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Connects Claude and other MCP clients to Elasticsearch data, allowing users to interact with their Elasticsearch indices through natural language conversations.
    3
    2,176
    702
    Apache 2.0
  • A
    license
    B
    quality
    C
    maintenance
    Connects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through MCP Clients like Claude Desktop and Cursor.
    11
    49
    22
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    Connects to Elasticsearch databases using the Model Context Protocol, allowing users to query and interact with their Elasticsearch indices through natural language conversations.
    4
    10
    Apache 2.0
  • A
    license
    -
    quality
    D
    maintenance
    Connects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through tools for listing indices, getting field mappings, performing searches, and viewing shard information.
    2,176
    Apache 2.0

View all related MCP servers

Related MCP Connectors

  • The grounded data layer for any LLM: governed SQL, metrics, lineage and catalog over your data.

  • Multi-LLM entity enrichment: schemas, single/batch enrichment, fusion, model benchmarks.

  • Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rbeg1/odigo-elastic-s2l-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server