Retrieve Elasticsearch index aliases with optional name filtering, enabling precise alias management and querying. Integrates with the octodet-elasticsearch-mcp server for streamlined operations.
Probe vector database endpoints for unauthenticated exposure, fingerprinting Weaviate, Qdrant, Chroma, Elasticsearch, Redis, and Postgres/pgvector and listing exposed schemas or data read-only.
Run a deep health probe across databases, Elasticsearch, embedding and LLM providers, and schedulers, returning status, components, queue, and scheduler details for production diagnostics.
MCP server for Kibana / Elasticsearch — log search, aggregations, index discovery, and dashboard browsing. Hits Elasticsearch REST API directly for log queries; falls back to Kibana
Console proxy when no direct ES URL is configured. Supports ApiKey auth (best for agents), Basic auth, and anonymous access. All 5 tools are read-only (readOnlyHint: true). Returns
structured JSON (outputSchema).
Find and inspect Virtual Observatory TAP services when no preset catalog fits. Search registry metadata, then review the selected service before querying it.
Search and aggregate measurement data using Elasticsearch Query DSL. Filter results with server-side aggregations and exact text matching for precise analysis.
Retrieve account profile, limits and permissions, API key scope and expiry, plus es-python setup progress with the next step. Read-only check for MCP clients.
Lists supported Linux distributions, architectures, and Python versions for es-python installations, optionally filtered by an OS target such as ubuntu_24_04_x86_64.
Query Elasticsearch indices using query DSL with enabled highlights. Connect and interact with Elasticsearch data via the Elasticsearch MCP Server for precise search results.
Convert an Elasticsearch SQL SELECT into the equivalent Query DSL using _sql/translate without running it. Learn the query structure, then pass the DSL to run_query for control.
Discover available Elasticsearch indices along with health, status, document count, and storage size. Use this to find index names before searching or aggregating logs.
Add new fields to an existing index mapping in Elasticsearch. Requires confirmation and enables only additive changes, helping extend schemas without data loss.