OpenSearch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listIndexesC | List all available indexes in OpenSearch |
| searchLogsC | Search for logs in any OpenSearch index |
| getIndexMappingC | Get the field mappings for an index |
| exploreFieldValuesC | Explore possible values for a field in an index |
| monitorLogsC | Monitor logs in real-time (simulated) |
| searchAlertsC | Search for security alerts in Wazuh data |
| getAlertDetailsB | Get detailed information about a specific alert by ID |
| alertStatisticsC | Get statistics about security alerts |
| visualizeAlertTrendC | Visualize alert trends over time |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, but 'searchAlerts' and 'searchLogs' could be confused as both involve searching, though they target different data types (alerts vs. logs). The descriptions clarify this distinction, but the overlap in naming might cause initial ambiguity for an agent.
The naming is mixed with some tools using verb_noun patterns (e.g., 'listIndexes', 'searchAlerts') and others using noun_verb or descriptive phrases (e.g., 'alertStatistics', 'exploreFieldValues'). This inconsistency makes the set less predictable, though the names remain readable overall.
With 9 tools, the count is well-scoped for an OpenSearch server, covering key operations like listing, searching, monitoring, and visualizing data. Each tool appears to serve a specific function without redundancy, fitting the domain appropriately.
The tool set covers core OpenSearch and Wazuh security alert functionalities, including listing, searching, monitoring, and visualization. Minor gaps might exist, such as lack of CRUD operations for indexes or alerts (e.g., create/update/delete), but agents can likely work around this for common use cases.