$ loading_
Retrieve error stack traces from OpenSearch logs by transaction ID.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "OpenSearch MCP Server" yet — see the docs or source repo.
Query OpenSearch for logs with transaction ID txn-48291, extract the related error stack traces, and summarize the likely cause in chronological order.
Returns the transaction’s error stack trace, key log excerpts, and a brief analysis of the probable cause.
Use the current configuration to connect to OpenSearch, verify index accessibility, and report whether transaction ID log retrieval works correctly.
Returns the connection status, accessible index information, and whether transaction-based retrieval is functioning properly.
Explain how to deploy this MCP server with Docker and provide an example workflow for querying an error stack trace by transaction ID after startup.
Returns Docker deployment steps, required configuration items, and an executable example query workflow.
Search, aggregate, and explore OpenSearch logs and index metadata read-only.
Interact with Elasticsearch for health checks, index management, CRUD, and search.
Connect to Elasticsearch for querying, search analysis, and workflow automation.
Connect to Elasticsearch clusters to inspect indices, search data, and fetch mappings.
Query and analyze telemetry data in natural language to find performance issues.
Use natural language to search, analyze, and manage Elasticsearch data.