Skip to main content
Glama
Rbedoyag

Elasticsearch/OpenSearch MCP Server

by Rbedoyag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENSEARCH_HOSTSNoThe hosts for the OpenSearch cluster, e.g., https://localhost:9200
ELASTICSEARCH_HOSTSNoThe hosts for the Elasticsearch cluster, e.g., https://localhost:9200
OPENSEARCH_PASSWORDNoThe password for OpenSearch authentication
OPENSEARCH_USERNAMENoThe username for OpenSearch authentication
ELASTICSEARCH_PASSWORDNoThe password for Elasticsearch authentication
ELASTICSEARCH_USERNAMENoThe username for Elasticsearch authentication
OPENSEARCH_VERIFY_CERTSNoWhether to verify certificates for OpenSearch connections (e.g., 'false')

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_indicesB

List all indices.

get_indexC
        Returns information (mappings, settings, aliases) about one or more indices.
        
        Args:
            index: Name of the index
create_indexC
        Create a new index.
        
        Args:
            index: Name of the index
            body: Optional index configuration including mappings and settings
delete_indexC
        Delete an index.
        
        Args:
            index: Name of the index
search_documentsD
        Search for documents.
        
        Args:
            index: Name of the index
            body: Search query
index_documentC
        Creates or updates a document in the index.
        
        Args:
            index: Name of the index
            document: Document data
            id: Optional document ID
get_documentC
        Get a document by ID.
        
        Args:
            index: Name of the index
            id: Document ID
delete_documentC
        Delete a document by ID.
        
        Args:
            index: Name of the index
            id: Document ID
delete_by_queryC
        Deletes documents matching the provided query.
        
        Args:
            index: Name of the index
            body: Query to match documents for deletion
get_cluster_healthB

Returns basic information about the health of the cluster.

get_cluster_statsB

Returns high-level overview of cluster statistics.

list_aliasesB

List all aliases.

get_aliasC
        Get alias information for a specific index.

        Args:
            index: Name of the index
put_aliasC
        Create or update an alias for a specific index.

        Args:
            index: Name of the index
            name: Name of the alias
            body: Alias configuration
delete_aliasC
        Delete an alias for a specific index.

        Args:
            index: Name of the index
            name: Name of the alias
general_api_requestB

Perform a general HTTP API request. Use this tool for any Elasticsearch/OpenSearch API that does not have a dedicated tool.

        Args:
            method: HTTP method (GET, POST, PUT, DELETE, etc.)
            path: API endpoint path
            params: Query parameters
            body: Request body

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 16 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific resources and actions in Elasticsearch/OpenSearch. The tools cover index management, document operations, alias handling, cluster monitoring, and search with no overlapping functionality. Even the general_api_request tool is clearly distinguished as a fallback for unsupported APIs.

Naming Consistency5/5

The tools follow a highly consistent verb_noun naming pattern throughout (e.g., create_index, delete_document, get_cluster_health, search_documents). All tools use snake_case with clear action verbs followed by resource nouns, making the API surface predictable and readable.

Tool Count5/5

With 16 tools, this server is well-scoped for the Elasticsearch/OpenSearch domain. It provides comprehensive coverage of core operations without being overwhelming. Each tool serves a specific, necessary function in the database management workflow, and the count aligns well with the complexity of the domain.

Completeness4/5

The toolset provides excellent coverage of core Elasticsearch/OpenSearch operations including CRUD for indices and documents, alias management, cluster monitoring, and search. The general_api_request tool elegantly handles edge cases. Minor gaps might include bulk operations or specific monitoring endpoints, but agents can work around these using the general tool.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources