OpenSearch Logs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
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