Schema | OpenSearch Logs MCP Server

OpenSearch Logs MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`OPENSEARCH_DEV_PASSWORD`	Yes	Password for the development OpenSearch environment
`OPENSEARCH_DEV_USERNAME`	Yes	Username for the development OpenSearch environment
`OPENSEARCH_PROD_PASSWORD`	Yes	Password for the production OpenSearch environment
`OPENSEARCH_PROD_USERNAME`	Yes	Username for the production OpenSearch environment

Features and capabilities supported by this server

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
search_logsA	Search OpenSearch logs with a free-text query. Supports Lucene query syntax. Examples: 'error AND authentication', 'status:500', 'message:timeout'
search_by_traceA	Search logs by OpenTelemetry trace ID to see all logs related to a specific request/transaction.
search_by_serviceC	Search logs filtered by service name, optionally with additional filters.
search_errorsC	Search for error logs, optionally filtered by service or additional query.
get_field_valuesB	Get the most common values for a specific field. Useful for discovering available services, log levels, or other field values.
search_by_fieldC	Search logs by a specific field and value.
get_mappingA	Get the field mapping for the index. Useful for discovering available fields and their types.
get_sample_logB	Get a single sample log entry to see the structure and available fields.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/luis-dominguez-stori/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server