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.

LiveContext

All integrations

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.

28 toolsBasic authAPI docs

Connect Elasticsearch How integrations work

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

POSTclose_index
Close an index to remove its overhead from the cluster. Closed indices do not allow read or write operations
PUTcreate_index
Create a new index with optional settings, mappings, and aliases. Index names must be lowercase and cannot start with a hyphen or underscore
DELETEdelete_index
Delete one or more indices. This operation is irreversible and deletes all documents, mappings, and settings for the specified index
GETget_index
Retrieve information about one or more indices including settings, mappings, and aliases

Document, 3 operations

DELETEdelete_document
Delete a specific document from an index by its ID
GETget_document
Retrieve a specific document from an index by its ID
POSTupdate_document
Update a document using a partial document or a script. Supports partial updates without replacing the entire document

Operation, 3 operations

POSTdelete_by_query
Delete all documents that match a given query in one or more indices
POSTsearch
Search 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
POSTupdate_by_query
Update all documents that match a given query using a script, without modifying the source data

Mapping, 2 operations

GETget_mapping
Retrieve the field mapping definitions for one or more indices
PUTput_mapping
Update the mapping definition for an existing index. New fields can be added but existing field types cannot be changed

Alias, 1 operation

GETget_aliases
Retrieve all aliases for one or more indices

Analyze text, 1 operation

POSTanalyze_text
Analyze text using the analyzer configured for an index or a custom analyzer. Returns the tokens produced by the analysis process

Bulk, 1 operation

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

Cat indice, 1 operation

GETcat_indices
List 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

GETcluster_health
Get the health status of the cluster including number of nodes, shards, and overall status (green, yellow, red)

Cluster stat, 1 operation

GETcluster_stats
Get comprehensive statistics about the cluster including node counts, index counts, memory usage, and disk usage

Count, 1 operation

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

Index document, 1 operation

POSTindex_document
Add a JSON document to an index with an auto-generated document ID

Index document with id, 1 operation

PUTindex_document_with_id
Add or replace a JSON document in an index with a specific document ID

Manage alias, 1 operation

POSTmanage_aliases
Add, remove, or update index aliases atomically. Aliases provide alternative names for indices and can point to multiple indices

Multi get, 1 operation

POSTmulti_get
Retrieve multiple documents by ID in a single request. Allows fetching documents from one or more indices efficiently

Multi search, 1 operation

POSTmulti_search
Execute 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

POSTopen_index
Open a previously closed index, making it available for search and indexing operations again

Refresh index, 1 operation

POSTrefresh_index
Refresh one or more indices to make all recent operations available for search. By default Elasticsearch refreshes every second

Reindex, 1 operation

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

Setting, 1 operation

GETget_settings
Retrieve 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

Create your workspace
Sign up free. Nothing to install.
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.
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.