Integration

Elasticsearch integration

Elasticsearch distributed search and analytics engine REST API. Index, search, and analyze large volumes of data in near real-time. Manage indices, documents, mappings, and perform powerful full-text search queries with aggregations.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Elasticsearch.Built from the 28 Elasticsearch tools below, on the connection you add once.

Common Elasticsearch use cases

  • automate index management
  • automate document management
  • automate operation management
  • automate mapping management
  • get alias programmatically
  • get index programmatically
  • close index programmatically
  • get mapping programmatically
  • get setting programmatically
  • put mapping programmatically

What you can do with Elasticsearch

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Index, 4 operations

  • close_indexClose indexPOSTClose an index to remove its overhead from the cluster. Closed indices do not allow read or write operations
  • create_indexCreate indexPUTCreate a new index with optional settings, mappings, and aliases. Index names must be lowercase and cannot start with a hyphen or underscore
  • delete_indexDelete indexDELETEDelete one or more indices. This operation is irreversible and deletes all documents, mappings, and settings for the specified index
  • get_indexGet indexGETRetrieve information about one or more indices including settings, mappings, and aliases

Document, 3 operations

  • delete_documentDelete documentDELETEDelete a specific document from an index by its ID
  • get_documentGet documentGETRetrieve a specific document from an index by its ID
  • update_documentUpdate documentPOSTUpdate a document using a partial document or a script. Supports partial updates without replacing the entire document

Operation, 3 operations

  • delete_by_queryDelete by queryPOSTDelete all documents that match a given query in one or more indices
  • searchSearchPOSTSearch for documents in one or more indices using the Elasticsearch Query DSL. Supports full-text search, term queries, range queries, bool queries, aggregations, highlighting, and sorting
  • update_by_queryUpdate by queryPOSTUpdate all documents that match a given query using a script, without modifying the source data

Mapping, 2 operations

  • get_mappingGet mappingGETRetrieve the field mapping definitions for one or more indices
  • put_mappingPut mappingPUTUpdate the mapping definition for an existing index. New fields can be added but existing field types cannot be changed

Alias, 1 operation

  • get_aliasesGet aliasesGETRetrieve all aliases for one or more indices

Analyze text, 1 operation

  • analyze_textAnalyze textPOSTAnalyze text using the analyzer configured for an index or a custom analyzer. Returns the tokens produced by the analysis process

Bulk, 1 operation

  • bulkBulkPOSTPerform multiple index, create, update, and delete operations in a single API call using NDJSON format for high throughput

Cat indice, 1 operation

  • cat_indicesCat indicesGETList all indices with high-level information including health, status, document count, storage size, and shard details in a compact tabular format

Cluster health, 1 operation

  • cluster_healthCluster healthGETGet the health status of the cluster including number of nodes, shards, and overall status (green, yellow, red)

Cluster stat, 1 operation

  • cluster_statsCluster statsGETGet comprehensive statistics about the cluster including node counts, index counts, memory usage, and disk usage

Count, 1 operation

  • countCountGETGet the number of documents matching a query. If no query is provided, returns the total document count for the index

Index document, 1 operation

  • index_documentIndex documentPOSTAdd a JSON document to an index with an auto-generated document ID

Index document with id, 1 operation

  • index_document_with_idIndex document with idPUTAdd or replace a JSON document in an index with a specific document ID

Manage alias, 1 operation

  • manage_aliasesManage aliasesPOSTAdd, remove, or update index aliases atomically. Aliases provide alternative names for indices and can point to multiple indices

Multi get, 1 operation

  • multi_getMulti getPOSTRetrieve multiple documents by ID in a single request. Allows fetching documents from one or more indices efficiently

Multi search, 1 operation

  • multi_searchMulti searchPOSTExecute multiple search requests in a single API call using newline-delimited JSON (NDJSON) format. Each pair of lines contains a header and a body

Open index, 1 operation

  • open_indexOpen indexPOSTOpen a previously closed index, making it available for search and indexing operations again

Refresh index, 1 operation

  • refresh_indexRefresh indexPOSTRefresh one or more indices to make all recent operations available for search. By default Elasticsearch refreshes every second

Reindex, 1 operation

  • reindexReindexPOSTCopy documents from one index to another. Useful for changing mappings, splitting indices, or migrating data between clusters

Setting, 1 operation

  • get_settingsGet settingsGETRetrieve the settings for one or more indices, including number of shards, replicas, analyzers, and other configuration

Use Elasticsearch from Claude Code, Cursor or Codex

Connect Elasticsearch in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Elasticsearch operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Elasticsearch

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Elasticsearch once

    Add your Elasticsearch connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Elasticsearch integration FAQ

What can you do with the Elasticsearch integration?

LiveContext exposes 28 operations on Elasticsearch, covering index, document, operation and mapping. Common uses include automate index management, automate document management and automate operation management.

Popular integrations

Browse the whole catalog